How Much Historical Data Should You Migrate to a New CRM?
Everything can be migrated; the question is what earns a place in the new system. A practical rule for what to migrate, what to archive and what to retire, decided object by object.
Every CRM migration starts with an optimistic question: can we move everything? The better question is which history earns a place in the new system. Migrating everything is possible in theory and costly in practice, because it carries old duplicates, dead leads and attachments nobody has opened in years into a system people now have to trust. Migrating too little is just as damaging: an account manager who cannot see the recent history of a customer relationship will recreate it in a spreadsheet within a week.
The answer is not one retention number. It is a written rule, agreed per object, that sends every record to one of three destinations: migrate, archive or retire.
Key takeaways
- Every record needs one of three destinations: migrate, archive or retire.
- Set the active horizon from contracts, support obligations and how far back management reports.
- Effort follows volume and complexity, not business value — attachments usually dominate both.
- Sign-off is a business decision: reconcile counts, check a sample and prove retrieval.
Three destinations, not one decision
Migrate: records the business needs to operate, report on and make decisions with in the new CRM.
Archive: records that must be kept for legal, contractual or historical reasons but are not part of daily work. The archive should be read-only, searchable and owned by a named person.
Retire: duplicates, test data, abandoned pipelines, obsolete custom objects and records you are not permitted to keep. Retiring is a decision that needs an owner, not an accident. It does not mean losing evidence. Export what you need first, then record why it was not carried forward.
Most migration arguments come from treating this as one decision. "Are we migrating the data?" is unanswerable. "Which accounts, opportunities and cases are migrating, and where does everything else live?" is a decision a team can make.
Start from decisions, not record counts
Ask the people who use the CRM which decisions history supports. Which renewals need past orders? Which service conversations need older cases? Which reports compare current performance with previous years? Then set an active horizon for each object: all open records, plus closed records whose outcome still affects current work.
The horizon should follow the business, not a default. Contract or warranty length, sales cycle, support obligations and statutory retention all matter. A business with short, repeating transactions and a business with ten-year infrastructure contracts need different rules. Write the horizon down and get the business owner to sign it, not only IT. The owner is the person who will be asked why a record is missing.
Teams that are still running on spreadsheets usually reach this question earlier, because the workbook is already the archive. If that is where you are, the Excel to CRM migration decisions apply before any of the mapping work below.
An object-by-object disposition
Use this table as a starting point, then adjust it with the business owner and the person responsible for legal retention.
| Object | Default treatment | Question that decides it |
|---|---|---|
| Accounts and companies | Migrate those with active work or open obligations; archive the rest | Is there a live contract, open case or planned opportunity? |
| Contacts | Migrate contacts linked to migrated accounts; archive the rest | Would a user act on this person in the next planning cycle? |
| Leads | Migrate open leads and those needed for source reporting; archive or retire the rest | Does anyone still need the lead source and its history? |
| Opportunities | Migrate all open deals plus closed deals inside the reporting horizon | Are old deals used for renewals, repeat business or revenue reporting? |
| Cases and service requests | Migrate all open cases; archive closed cases beyond the support or legal horizon | Is there a contractual or legal duty to retrieve this case? |
| Activities, notes and emails | Migrate what users reference; archive by date | Would a user need this to serve the customer now? |
| Attachments and documents | Migrate only those with a current purpose or legal duty | Is this document still governed by a retention requirement, or still in use? |
| Custom objects | Migrate only if the process still exists and has an owner | Who uses it, and what decision does it support? |
| Legacy or unused objects | Archive unless still in use | Is anyone maintaining this object today? |
The table is deliberately conservative. When a record has no clear operational use and no clear retention duty, it belongs in the archive or in retirement, not in the new system by default.
Settle retention and legal questions early
Do not assume that keeping more history is automatically safer. More personal data means more obligations: retention limits, access rules and deletion requests. Agree early on the minimum retention period, where the archive lives, who can access it and how a deletion request is handled across both the CRM and the archive. If you cannot retrieve an archived record, you cannot claim to have retained it. If you keep data with no purpose and no owner, you have created risk rather than value.
What actually drives migration cost
Effort follows volume and complexity: the number of records, the attachments, the relationships, the duplicates, the field mapping and the depth of history. A large set of clean contacts can cost less than a smaller set of accounts with messy hierarchies and scanned documents. Business value does not grow in the same way, which is why "migrate everything" is rarely a rational default. Budget by object and estimate attachment volume separately, because documents often dominate the effort while adding the least day-to-day value.
The phases themselves are predictable — extract, cleanse, map, load, reconcile. What varies is how much of each you do per object, which is the sequence set out in CRM data migration strategy, planning and execution.
How to archive so it stays usable
A migration archive is a system, not a folder. It needs:
- A data dictionary: object, fields, meaning, source and date range.
- Stable identifiers, so a record in the new CRM can be traced back to the old one.
- Read-only access and search, with named access owners.
- Tested retrieval using real questions users will ask, such as finding a specific contract from a particular year.
- A retention end date, and a named person who will act on it.
- An export path in case the archive platform is retired.
If the old CRM can remain read-only and supported, it can serve as the archive. That is acceptable only if it stays secure, searchable and licensed, with a plan for the day the vendor or licence ends.
A worked example
Consider a B2B equipment manufacturer moving roughly ten years of pipeline from an older CRM. It agrees a policy like this:
- Migrate all open opportunities, all accounts with a live service contract or recent activity, and all open cases.
- Migrate closed-won opportunities inside the renewal and reporting horizon.
- Archive closed-lost opportunities and older closed cases, plus most activity history, as read-only records with source identifiers.
- Retire duplicate accounts, test records and two custom objects whose processes no longer exist.
The horizons here are illustrative. The point is the shape: every object has a destination, the reason is written down, and the archive has an owner and a retrieval test. Before cutover, the team reconciles counts by object and status, checks a sample of records field by field, confirms that relationships survive and proves that old documents open from the archive.
The same shape holds when the source is a different platform: the lessons from migrating Salesforce to Creatio are mostly about disposition decisions taken too late.
What sign-off should actually prove
Before cutover, show that:
- Record counts reconcile by object and status, with every difference explained.
- Relationships survive, including contacts to accounts and cases to accounts.
- Financial totals match where money is migrated.
- A sample of records matches the source field by field.
- Attachments and notes open from the archive.
- Users can answer three real historical questions in the new system.
Name one business owner who signs off. "IT tested it" is not acceptance, because IT cannot decide whether the history is sufficient for the work.
Common failure modes
- Treating "we moved every record" as success.
- Migrating attachments nobody needs.
- Losing source identifiers, so nobody can trace an old record.
- Archiving without search, access or an owner.
- Leaving duplicates to be resolved later, when they are harder to see.
- Never making a deletion decision, so obsolete data follows the business forever.
- Testing retrieval only when an auditor or a customer asks.
Frequently asked questions
Should we migrate all historical opportunities?
Only those that support current reporting, renewals or repeat business. Older closed deals usually belong in an archive unless a contract or regulation requires them to remain in the CRM.
How far back should we go?
Set the horizon from your business cycle and obligations rather than a generic number: contract length, support terms, statutory retention and how far back management actually reports.
Can we keep the old CRM read-only instead of building an archive?
Yes, if it remains secure, searchable and supported, with a named owner and a plan for when the licence or vendor support ends. A read-only old system is an archive with an expiry risk.
Can we delete records we do not need?
Only with a documented decision and after checking legal and contractual duties. Export what must be kept, record the decision and keep the audit trail.
Apply this to your operating process
Decide the rule before you write the mapping. A short written policy, covering what is migrated, what is archived, what is retired, for how long and who owns each, prevents most of the arguments that stall a migration late. Then test retrieval, not just import counts.
If you are planning a CRM migration, I can help you define the disposition policy, reconcile the data and prove the cutover. Book a free 30-minute CRM clarity call, or read more about the data migration service.
The policy also outlives the project. Once the system is live, the question shifts from which records came across to who keeps them accurate — the ownership and governance question covered in CRM data quality and ownership.
Deciding this on a live migration?
Bring the object list and the retention question you cannot answer. A free 30-minute CRM clarity call is usually enough to settle the disposition policy before the mapping work starts.
Book a Free 30-Min CRM Clarity Call More articles