Migration guide
Plan the move before moving the data.
Use the public demo to evaluate workflows with synthetic records. A real dealership migration is a separate, authorized project with its own review and validation.
Define the scope and the owner
List the rooftops, teams, source systems and records that belong in the migration. Agree who can approve access, field mapping, duplicate handling and the final cutover.
Review identities before volume
Check inventory VIN and stock identity, customer matching, lead attribution and record references with a small approved sample. Resolve conflicting identities instead of treating every row as a new record.
Keep consent and history intact
Do not infer consent from a contact field or a historical export. Review suppression, revocation evidence, channel purpose and audit requirements alongside the operational records.
Validate, then decide
Compare dry-run or rehearsal results, permission checks and expected counts before approving real writes. Current vendor migration adapters use synthetic fixtures; they are not a promise of a live connector or an automatic production migration.