As a prerequisite to the host migration, we'll need to create a dedicated connector for migration purposes along with the outbox connector. These connectors will be deployed with initial snapshots disabled and in STOPPED state.

This will prevent the connector from processing any hosts before our desired migration date. We should understand what happens if a host is added to either the hosts table or the outbox before migration but after the connectors are created to ensure there isn't a potential for data consistency issues. If a host is deleted/updated before the migration, and that event is captured by the connector, there is a potential for a deleted/updated host to replicate to Inventory and have inaccurate permissions/settings/history.

Example scenario:

• Connectors are created, in STOPPED state
• If a new hosts is added to outbox/hbi, do those hosts get replicated while the connector is stopped?
• If not, when the connector is started, are those changes captured in WAL and replicated immediately after starting the connector?
• What process must we take for the migration to setup the required infra, and avoid any out-of-order message processing