Salesforce implementation

US · UAE · Global

Five years of history or the open deals: what to bring into Salesforce, archive or drop

By Shivanath DevinarayananPublished 9 min read
Written forThe Salesforce owner with an org that isn't working“Our Salesforce org is stuck.”

The short answer

How much history should a team bring from its old CRM into Salesforce?

Move the records a named person will open this quarter: open deals with their recent activity, active accounts and contacts, and live contracts. Archive what someone will only look up, read-only and searchable. Leave behind what nobody owns. If nobody can name who opens a record type, it waits. At Mindcat, we write that list in week one.

A stack of archive boxes on a hand truck beside a lamp-lit desk with one thin folder, with the words Archived after 365 days

Takeaways

  1. 01Salesforce archives events and closed tasks older than 365 days by default, so old activity you load drops out of reports.
  2. 02Most Salesforce records count about 2 KB of data storage; an Enterprise org starts at 10 GB plus 20 MB per user licence.
  3. 03The guides agree on three bins, move, archive and leave behind, but suggest different time windows.
  4. 04Our rule: a record type moves only when a named person will open it this quarter.
  5. 05Keep the old system read-only and searchable after go-live; most lookups come early.

If the old CRM export is bigger than anyone on the team has read, this is for you. So is an org that already loaded all of it and now has duplicate accounts and slow activity reports. The usual instinct is to bring all of it into Salesforce, just in case. That instinct costs storage, slows the load, and much of what it brings will not show up where your team looks. This is not for you if your org has no named Salesforce admin or owner to make the call, or if you are not moving or merging a CRM at all.

What goes wrong when you bring everything?

Most of the old activity lands out of sight. Salesforce Help says it archives events that ended more than 365 days ago and closed tasks due more than 365 days ago, and that "archived activities aren't included in reports." Archived activities also drop out of list views and the calendar view. The archive job runs every Sunday. Load five years of calls and meetings on a Saturday, and by the next week most of them sit on record pages only, out of every activity report.

The records still count against storage. Salesforce Help says most records use about 2 KB of data storage, and an HTML email message uses its actual size, so a 100 KB email counts as 100 KB. Enterprise Edition starts at 10 GB of data storage per org, plus 20 MB per user licence. Files count against a separate allocation.

ItemWhat Salesforce says
Activity archiveEvents and closed tasks older than 365 days; not in reports, list views or the calendar
Archive jobRuns every Sunday from 5 AM local time
Raise the thresholdAsk Salesforce Support; up to 3,650 days, about five years recommended; can slow activity reports and list views
Record sizeAbout 2 KB for most records; campaigns about 8 KB; HTML email at its real size
Enterprise data storage10 GB per org plus 20 MB per user licence
Data Import WizardUp to 50,000 records at a time; test a small CSV first

Do the arithmetic on a typical export. One million old activity records at 2 KB each is about 1.9 GB. A 30-user Enterprise org starts with 10.6 GB. One table from the old CRM can take nearly a fifth of the org's storage before anyone has logged a new deal.

Timeline: load on Saturday, archive job on Sunday, and on Monday reports show only the last 365 days of activities
The default Salesforce archive window, read 16 November 2026.

Bringing too little fails too. Rework's migration guide tells the story of an account executive whose renewal history was left out of the export. Three weeks after go-live, she asked a prospect a question they had already answered. The renewal closed, at a lower rate. Their verdict: "It was a planning failure. Nobody had made a decision about what to migrate and what to leave behind."

Where do the migration guides agree?

On the bins, not the window. Three guides published this year use the same three: move, archive, leave behind.

  • Umbrex, a consultancy, asks "what must be in the new system for the first selling cycle and first service cycle to work without calling the legacy team?" and calls the urge to migrate everything "just in case" the default impulse.
  • HubSpot's guide, updated 29 October 2026, sorts records into migrate and archive, and says the rest can be disposed of only under your organisation's retention rules.
  • Rework gives a matrix by age, record type and deal status, and says auto-logged email-open events should be discarded at any age.

The windows differ. Rework moves rep-entered notes from the last 12 months. CRMIT suggests two to three years of closed opportunities and cases for most organisations, and 18 months for fast, high-volume sellers. Umbrex says the window depends on regulation and how managers coach.

The spread is the useful part. No number of years is right for every team, because the window is set by who opens the record, not by its age.

Three cards: move open deals, accounts and contracts; archive closed deals; leave behind email-open events and duplicates
Three bins. The owner decides the bin, not the record's age.

How do we decide: move, archive or leave behind?

We start from people, not the export. For each record type in the old CRM, we write one line with three columns: who opens it, how often, and what they do with it.

  1. 01List every record type in the old CRM export: accounts, contacts, deals, activities, notes, files, custom tables.
  2. 02Next to each, name the person who opens it. A role is fine; 'everyone' is not an answer.
  3. 03Write when they open it: this week, this quarter, once a year, or only when someone asks.
  4. 04Write what they do with it: work it, report on it, or look something up.
  5. 05Give the line a call: move, archive or leave behind.
  6. 06For every record type that moves, write the match rule for duplicates (legacy ID, email domain, normalised company name) and merge before the load.

Then apply the rule. This is our rule, not a Salesforce rule.

What the line showsThe callWhy
A named person works it this quarter: open deals, active accounts and contacts, live contractsMoveDay one in Salesforce has to look like their week.
Recent notes and calls on those open deals and accountsMoveThe rep needs the last conversation before the next one.
Someone looks it up now and then: closed deals, old cases, past activityArchiveRead-only and searchable, outside the live org.
A retention rule says it must be keptArchive, unless the rule says it must be liveThe compliance owner decides, before the export.
Duplicate copies of an active account or contactMerge before the load, then leave the extra copies behindOtherwise the new org starts with the duplicates the old one had.
Auto-logged events, test records, anything nobody can name an owner forLeave behindNobody opens it, so nobody misses it.

Here is the list on a sample company. The company and every line are invented; the shape is the one we write.

Record typeWho opens itWhenCall
Open deals and their last 12 months of notesAccount executivesDaily
Active accounts and contactsSales and customer successWeekly
Live contracts and renewal datesCustomer success leadMonthly
Closed deals, two to five years oldSales manager, for a win-rate questionOnce a quarter
Duplicate accounts from two regional teamsSales opsBefore the load
Email-open and page-view eventsNobodyNever

Three lines move, one is archived, one is merged before the load, and one is left behind. The line that matters most is the one where nobody can say who opens it. That is a finding about the process, not the data, and it waits until someone owns it.

This is the first thing we write in Implement Around Your Process: the week of real work names who opens which record, and the migration scope comes from that week.
Flow: for one record type ask who opens it; a named person this quarter means move, someone now and then means archive
One question per record type: who opens it, and when.

Where should the archive live?

Somewhere the team can still search, or they will rebuild the old system on the side. Rework recommends keeping the source system "accessible for 90 days post-migration" because "most requests will come in the first two weeks." Umbrex recommends read-only access to the legacy system or an archive store, with clear search instructions.

Two habits make the archive usable:

  • Keep the old record ID. Store the legacy ID in an External ID field on each record you move. Reloads can then update the same record instead of creating a duplicate, and anyone can find the same customer in the archive.
  • Say where it is. Put the archive link and the date the old system goes read-only in the go-live note, so nobody has to ask.

If your team does need older activity in Salesforce reports, decide that before the load. Salesforce Help says a System Administrator can ask Support to raise the archive threshold, up to 3,650 days, with about five years recommended, and warns that a higher threshold can slow activity reports and list views. After an increase, Salesforce Help says archived records gradually become available again.

If you already loaded everything, the same list still works. Write who opens each record type, then merge the duplicates on the match rule, keeping as the master the record whose owner and last activity the team trusts. Export what nobody opens to the archive and delete it from the org, and decide with your team whether the archive window should change, before anyone buys more storage. If the org is already live and stuck, that is a rescue and optimize week, not a new build.

What breaks in the load itself?

Dates and volume. Vantage Point's activity migration guide points out that a task's completed date is set by Salesforce when the task closes, so 10,000 closed tasks loaded on migration day all show that day. Their fix: map the legacy date to the task's Date field, keep the original in a custom field, and decide before the first load whether the load user gets the Set Audit Fields upon Record Creation permission, which keeps the old created dates and works only when a record is first inserted.

Volume picks the tool. Salesforce Help says the Data Import Wizard imports up to 50,000 records at a time. The Salesforce Data Loader guide covers larger loads, objects the wizard does not support, and scheduled loads. Both start the same way: load a small file into a sandbox and check it with the people who will use it.

Five steps: write who opens what, set the archive window, load a small file to a sandbox, check it, load the rest
Decide the archive window before the first load, not after.

For the full plan around this decision, mapping, cleansing and cutover, read our Salesforce data migration strategy guide. If you are still deciding whether to move at all, we covered that in when we tell a team on HubSpot to stay.

Two people sort printed record sheets into gold, periwinkle and grey trays, with the words Who opens it this quarter?
Sort by who opens it, before anyone exports a file.

What would we do first?

At Mindcat, we call this method "Find your week." We spend week one in the org and in your real work, then write down who opens which record, how often, and what they do with it. The migration scope comes from that list, with the archive and the records left behind named on it, before anyone exports a file. You can see a sample note, on an invented org, before you send us anything.

The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. There is no number before week one, and a fixed price for a named piece after it. The build itself is our Salesforce implementation work.

Not for you if your org has no named Salesforce admin or owner yet, or if a retention rule requires every record to stay live in the CRM. Name the owner, or settle the rule with your compliance owner, then write the list.

Filed under

Salesforce implementationcrm migration what data to migratehow much history to migrate to salesforcecrm data archivesalesforce archived activities
Useful to someone on your team?

FAQ

Questions teams ask next

Will five years of activity history show up in Salesforce reports?
Not by default. Salesforce Help says it archives events that ended more than 365 days ago and closed tasks due more than 365 days ago, and archived activities are not included in reports. They stay on record pages and through the API. An admin can ask Salesforce Support to raise the threshold, up to 3,650 days, with a recommended maximum of about five years.
Should we use the Data Import Wizard or Data Loader?
Salesforce Help says the Data Import Wizard imports up to 50,000 records at a time and supports accounts, contacts, leads, solutions, campaign members, person accounts and custom objects. The Salesforce Data Loader guide covers larger loads and objects the wizard does not support. Whichever you use, Salesforce recommends testing a small CSV file first.
How much Salesforce storage will old CRM data use?
Salesforce Help says most records use about 2 KB of data storage, campaigns about 8 KB, and an HTML email message its actual size. Enterprise Edition starts at 10 GB of data storage per org plus 20 MB per user licence, and files count against a separate allocation. Check Storage Usage in Setup for the limit your org has.
What if a regulation says we must keep old records?
Then the record is kept, and the only question is where. Decide that with your compliance owner before the export, not after. A read-only archive can meet a retention need without loading the records into the live org, but the compliance owner, not the migration team, makes that call.

Sources

  1. 01Salesforce Help: Work with Archived ActivitiesAccessed 16 Nov 2026
  2. 02Salesforce Help: Increase Archive Days Limit for Activities (25 June 2026)Accessed 16 Nov 2026
  3. 03Salesforce Help: Data and File Storage AllocationsAccessed 16 Nov 2026
  4. 04Salesforce Help: Estimated Record Size by Object TypeAccessed 16 Nov 2026
  5. 05Salesforce Help: Data Import WizardAccessed 16 Nov 2026
  6. 06Salesforce Developers: When to Use Data LoaderAccessed 16 Nov 2026
  7. 07Umbrex: Data Quality and Migration Leadership (4 March 2026)Accessed 16 Nov 2026
  8. 08HubSpot: CRM migration guide (updated 29 October 2026)Accessed 16 Nov 2026
  9. 09Rework: Handling Historical Activities, Notes, and Emails During CRM Migration (18 April 2026)Accessed 16 Nov 2026
  10. 10CRMIT: Which CRM Data Should You Bring Into Salesforce? (29 September 2026)Accessed 16 Nov 2026
  11. 11Vantage Point: Migrating Activity History to Salesforce (1 October 2026)Accessed 16 Nov 2026
Shivanath Devinarayanan, founder of Mindcat

Written by

Shivanath Devinarayanan

Founder, Mindcat Consulting · Salesforce MVP Hall of Fame

Builds and runs AI agents in production. Reads every brief that comes in and signs the work that goes out.

About Shivanath

Implement Around Your Process · the written assessment

We work in real estate and right now, our Salesforce org is stuck.

Industry
Problem

Brief: Real estate. Leads from portals and WhatsApp. Follow-up has no owner. The org is stuck. Stabilise first, then decide what is worth finishing. From: /blog/crm-data-migration-what-to-move.