Product Migration Communication Agent

Standard migration instructions often miss prerequisites that apply to a specific customer's setup. When a customer is scheduled for migration, this agent reads their configuration export and identifies which prerequisites apply, such as version, add-ons, integrations and data size. It checks for missing evidence, like an unconfirmed backup. If the customer runs an unsupported version, it creates a separate exception path. It drafts tailored instructions based only on the actual configuration and checks every step against it. Product operations approves delivery to the customer, and the agent never runs a migration. Edge case: the export shows an older version that needs an intermediate upgrade, so the guide adds that step.