The import completed without an error, but the customer notes were attached to the wrong accounts. That is a migration failure even if the new system reports that every row arrived.
Moving business data safely means preserving meaning, access, and usable records—not merely transferring files. A small company can make the process manageable by separating preparation, testing, cutover, and verification.
This is a general planning guide. Obtain qualified technical, legal, or compliance help when the data or consequences warrant it.
Name an owner and define the scope
Choose one person to approve decisions and keep a migration log. List the source system, destination, records being moved, required history, attachments, integrations, and people affected.
Decide what success looks like before exporting. For a CRM, that might include correct customer ownership, open opportunities, next-action dates, and accessible notes. For invoicing, it could include open balances and the records your accountant needs.
Do not assume every old field belongs in the new system. Unnecessary data creates cleanup work and can increase privacy risk.
Check contracts, permissions, and retention
Confirm that you can export the required information and that the destination is appropriate for it. Review vendor terms, data-processing arrangements, access controls, and any location or retention restrictions that apply.
Identify records that must be retained and those that should be deleted under the business’s policy. A migration is not a reason to bypass deletion requests or keep information indefinitely.
The FTC recommends limiting sensitive information to people who need it and protecting it during storage and transfer. 1
Create a protected source copy
Take an authorized export or backup before changing the old system. Store it in an access-controlled location, protect it appropriately, and document who can use it.
Confirm that the copy is readable and sufficiently complete for the planned recovery. A contact CSV may omit messages, attachments, or transaction details.
Do not place unencrypted exports containing sensitive information in ordinary email or an open shared folder. Avoid using real customer records in a test workspace unless that use is authorized and adequately protected.
Map fields and identifiers
Create a mapping table with source field, destination field, format, required status, transformation, and exception handling.
Inspect dates, time zones, phone formats, postal codes, currency, consent records, and multi-select fields. Spreadsheet applications can remove leading zeros or reinterpret dates, so verify the exported and imported values rather than trusting the display.
Use stable identifiers to link records. HubSpot’s import documentation, for example, describes unique identifiers for updating records, preventing duplicates, and maintaining associations. Your destination may use different rules or prioritize identifiers differently. 2
Never assume that a name alone is a safe match.
Clean carefully and document the decisions
Separate true duplicates from different people with similar details. Decide how conflicting phone numbers, ownership, and status values will be resolved.
Keep a record of important transformations. If “active” becomes “open customer” in the new system, document that meaning. Do not silently collapse categories that staff need for reporting or compliance.
Preserve an untouched source copy so a cleanup error can be investigated without guessing what the original value was.
Run a representative test import
Choose a small sample containing ordinary records and difficult cases: missing fields, nonstandard characters, multiple contacts at one company, attachments, and historical transactions.
If possible, use synthetic data that reflects those patterns. Where real records are necessary, use a controlled environment with appropriate permissions.
Validate more than row counts. Check relationships, amounts, dates, ownership, privacy settings, and searchability. Have an everyday user carry out an ordinary task using the imported record.
Inspect automation before importing. A bulk load should not unexpectedly send welcome emails, payment reminders, or customer notifications.
Plan the cutover and rollback
Choose a change window and tell staff which system is authoritative at each stage. Decide whether old-system edits will be paused or captured for a final transfer.
Write down the sequence: final export, protected copy, import, validation, integration updates, and approval to resume work. Identify who can stop the process.
A rollback plan should explain what triggers a return, who approves it, and how changes made after cutover will be reconciled. If both systems accept edits independently, a simple “switch back” can lose new work.
Verify before canceling the old service
Reconcile totals and investigate exceptions. Check a sample of records manually and get approval from the people responsible for operations, finance, or compliance as relevant.
Confirm forms, calendar connections, reports, and scheduled automations now point to the correct system. Remove temporary accounts and revoke unneeded vendor access.
Keep the old system available for a justified transition period if necessary, but avoid indefinite uncontrolled access. Verify export completeness, retention obligations, and the provider’s deletion process before cancellation.
Delete temporary working copies under an approved process once they are no longer needed. Document what remains and why.
Common questions
Can we migrate everything in one evening?
Possibly for a simple, well-tested case. Do not set the schedule before reviewing volume, attachments, export limits, testing, and rollback needs.
Is a vendor’s migration service enough?
It can help, but the business still needs to define correctness and approve the results. Clarify who handles exceptions and what the service excludes.
Is matching row counts proof of success?
No. The correct number of records can still contain wrong relationships, missing notes, altered dates, or incorrect permissions.
Bottom line
Treat migration as a controlled business change. Preserve a source copy, test representative cases, verify meaning as well as counts, and do not cancel the old service until the new records are demonstrably usable.
Related guides
Sources
1 FTC, Cybersecurity for Small Business.
2 HubSpot, Understand the import tool. Vendor-specific example; confirm the rules for your destination system.