CRM Migration stages supported source data for review. Import management permission, the applicable file or connector feature and current capacity are required. Rollout pauses can also restrict these actions. See CRM access and capacity.
Related video lesson
Review supported migration scope, source identities and reconciliation before a pilot.
Preview before importing
Upload supported Zoho exports or a Zoho backup package, or use Reimport Nviti CSV for supported native exports. Keep stable source IDs and use the same source organization or migration name for later reimports. Review mappings, timezone, currency, relationships and duplicate decisions; a changed mapping needs a new preview.
The dry-run preview shows row outcomes, exceptions and capacity. Inspect the full outcomes, not only samples. Map reviewed duplicates to the intended existing contact. Approve and import requires the current preview and explicit acceptance of exceptions where offered. Review resulting rows and files for failures or omissions. An upload or approval is not a completed import receipt, and source presence is not marketing consent.
Use the guarded rollback preview before applying rollback. Only unchanged imported changes can be reversed safely; later work needs manual reconciliation. Restore Nviti archive accepts an original Nviti ZIP, retains its original workspace identity and previews supported records, files, retained history and exclusions before approval. Full workspace restoration is unavailable. Automation enrollment and worker state, campaign enrollment bindings and external provider credentials are not reconstructed merely by restoring supported records; inspect the archive's exclusions.
Evidence expires
Keep your original exports and backups. Check the job's displayed expiry time before reviewing duplicates or preparing rollback: those actions require unexpired evidence. The source-retention default is 30 days and is configurable; the displayed expiry is the deadline for that job, not a promise of permanent rollback availability.
When evidence is expired and purged, source payloads, before-change values and approval source evidence are cleared. Temporary source files are removed only when their removal is confirmed. Imported records and outcome metadata remain; these retained outcomes cannot reconstruct the missing review or rollback evidence. Expired rollback requires manual reconciliation. Check the job's current status rather than assuming expiry maintenance has already run.
Read-only Zoho source
When available and configured, Connect Zoho selects the account region and requested modules. Verify the returned organization and environment before Read Zoho data. Read only the selected records and supported delta window. Files, deleted records, audit history and custom modules need separate reviewed exports where supported. This read-only migration-source workflow does not provide two-way Zoho synchronization; it stages data for review. Ongoing record exchange is a separate integration: see Zoho CRM and Zoho record updates.
Inspect extraction progress and row outcomes before resuming or approving. Disconnect Zoho removes credentials and stops further reads while retaining staged and imported records. Connecting requires the relevant purchased feature, staff authority, rollout access and configured provider credentials; the button alone is not proof of a usable provider connection.
Your sales connections
For connected email and calendar, start at account and purpose selection (01:09). This is separate from bulk data migration.
Your sales connections manages your own Google sales email and calendar connections in the selected workspace. Synced messages and meetings remain private to their authorized staff scope. Review linked and unmatched results; an ambiguous match must not be treated as an identified customer. Restart synchronization or request the next page only after reviewing the current status.
Disconnecting retains linked records. Calendar export, customer email and meeting actions retain their own permissions and eligibility checks. Review the local record and actual provider outcome; for an unknown delivery, check the mailbox or calendar before trying a new send or invitation. Provider configuration and operational availability must be checked before relying on synchronization.
Duplicate review and a migration pilot
Within-package email/phone collisions use the same mapped identity normalization as the import. Potential later duplicate creates are held for review and excluded from contact-growth forecasts. Summary and paginated review use the same classification. Names alone do not identify a duplicate, explicit target mappings are preserved, and converted Leads retain their intentional Contact relationship.
For a pilot, prepare a small representative export with stable source IDs, related organizations/contacts/deals/activities, field/owner/stage mappings, timezone/currency choices and a known duplicate/conflict example. Include attachments only through a supported package. Reconcile created, updated, held, skipped and rejected outcomes and inspect relationships before widening the batch. Retrying under a new source name can defeat intended identity matching; keep the verified source identity stable.
Retained package/archive source binaries use company-private cloud storage. Workers verify byte count and digest through temporary local spools; a worker restart is not permission to read a different source. Full workspace restore, external credentials, live worker state and marketing consent are not inferred from a file import.
Reading the preview summary
Preview cards show source-row, currently-valid and exception counts. Valid source rows are not necessarily new records: inspect the proposed operations, duplicate decisions and the separate capacity forecast before approving. The existing complete-review download and row/file outcomes remain available below the summary.
Advanced feature coverage
Use the migration and integration coverage matrix before promising replacement of source quotes, custom fields, reports, forecasts or automation. Wider historical file support does not extend ongoing Zoho Contact sync. Personal Google email/calendar setup and recovery have a separate Sales connections guide.