---
title: "How many years of CRM data should you migrate?"
description: "There is no fixed number. Migrate every open record, set a cutoff for closed history by how you report, and archive the rest in an export you can search."
url: "https://flitstack.ai/answers/how-many-years-of-data-to-migrate-crm"
---

# How many years of data should we migrate when moving between CRMs?

Short answer

There's no standard number of years. Move every open record and every account with recent activity. For closed deals and activities, go back as far as your reporting and renewal cycles need, which is often two or three years. Export the older history to an archive you can search. Legal retention applies to that archive, not to the new CRM.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Ask us about your migration ](https://flitstack.ai/contact) [Read the full guide →](https://flitstack.ai/guides/crm-migration-checklist)

## Set the cutoff by object, not by date

People ask “how many years” as if one cutoff fits the whole CRM. It doesn’t. A contact from 2015 who renewed last month needs to move, while a lost deal from 2019 may not need to. Set the rule for each object, then check that the related records you keep still have their parents. An activity is useless if its contact stayed behind.

| Data                           | Typical rule                                       | Why                                                           |
| ------------------------------ | -------------------------------------------------- | ------------------------------------------------------------- |
| Open deals, tickets, tasks     | All of them                                        | Work in progress can’t stop at cutover                        |
| Accounts and contacts          | Active, plus anyone tied to an account you keep    | Associations break if the parent is missing                   |
| Closed-won deals               | As far back as your revenue and renewal reports go | Year-over-year reports need the prior years                   |
| Closed-lost deals              | One or two sales cycles                            | Useful for win/loss analysis, little use after that           |
| Emails, calls, notes, meetings | The same window as the records they belong to      | They make up most of the volume, so set this cutoff with care |
| Attachments                    | Contracts and signed documents; skip the rest      | File storage is often billed separately                       |
| Everything older               | A searchable archive, not the new CRM              | Kept for audits, not for daily use                            |

## Retention rules apply to the archive, not to the new CRM

Finance and HR data often has a legal retention period. The US IRS, for example, says to keep records for 3 years in most cases, 6 or 7 years in specific cases, and employment tax records for at least 4 years. That obliges you to keep the data. It does not oblige you to load it into the new CRM. An archive with the original IDs usually meets the rule for much less effort.

## What native tools do / where they stop

Native importers load whatever you give them. None of them helps you choose a cutoff. HubSpot, Salesforce and Zoho importers take files and match on keys, but they don’t check whether each activity’s parent record came across too. That check is the gap: if you filter the history by date and the accounts by “active”, you can end up with notes on contacts that were never imported.

## Steps

1. Count records by object and by year in the source.
2. Agree on a rule for each object with sales, finance and support.
3. Check that every record you keep has its parent records in the set you keep.
4. Export the full source to an archive before cutover.
5. Migrate the filtered set and reconcile the counts against the rules.

FlitStack AI can filter what moves and check parent links during the sample run. For ERP moves, most customers migrate 3–7 years of history, with a cutoff you can configure. Start from the [CRM migration checklist](https://flitstack.ai/guides/crm-migration-checklist) or [talk to us](https://flitstack.ai/contact).

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

Questions, answered

## A few useful answers.

Does migrating less history make the migration cheaper?

Usually, yes. Activities, emails and attachments make up most of the volume in a CRM, so a cutoff on activity history cuts run time and import volume more than a cutoff on contacts does.

Where should the history we don't migrate go?

Keep a full export of the old system in a format you can search, such as CSV or a database snapshot, with the original record IDs. Store it until your retention policy says you can delete it.

Should we migrate contacts who haven't engaged in years?

Only if you have a reason to keep them, such as an open account, a renewal or consent you can prove. Stale contacts add cost on destinations that bill per contact, and they skew your reports.

## Related

### [CRM migration checklist: what to do before, during and after the move](https://flitstack.ai/guides/crm-migration-checklist)

[Read →](https://flitstack.ai/guides/crm-migration-checklist)

### [How much does a CRM migration cost, and what drives the price?](https://flitstack.ai/guides/crm-migration-cost)

[Read →](https://flitstack.ai/guides/crm-migration-cost)

### [CRM migration](https://flitstack.ai/migrations/crm)

[Read →](https://flitstack.ai/migrations/crm)

### [Data migration services for CRM, help desk, ERP, PM and HR systems](https://flitstack.ai/services/data-migration)

[Read →](https://flitstack.ai/services/data-migration)

## Sources

1. [IRS: How long should I keep records?](https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records)
2. [Quora: How many years of data should one migrate when moving between CRMs?](https://www.quora.com/How-many-years-of-data-should-one-migrate-when-moving-between-CRMs)

A closer look

## Tell us what you’re moving.

Share your source, destination and rough record counts. We scope the migration and the process work with you and send you a quote.

[Get a quote](https://flitstack.ai/contact)
