CRM Data Archival: What to Migrate vs What to Archive
Dragging every old closed deal and inactive contact into the new CRM "just in case" slows search, inflates licence tiers, and muddies reporting. A clear archive vs migrate policy preserves access without polluting the live system.
We design the retention rules and the archive so your new CRM stays lean and performant.
Sound Familiar?
These are the exact issues our clients faced when "migrate everything" was the default:
- Leadership wants every closed deal and inactive contact "just in case", so the new CRM inherits nine years of dead weight
- Search and list views crawl because obsolete records sit next to active pipeline
- Marketing and CRM licence quotes are priced on total record count, including people nobody has emailed in years
- Reports mix live opportunities with ancient closed-lost deals, so forecasting looks worse than it is
- Nobody owns a written archive vs migrate policy, so the default becomes "bring everything across"
POPIA Section 14 forbids keeping personal information longer than necessary. "Just in case" is not a retention policy. Tax and company law set minimum floors for financial records, but inactive marketing contacts without a lawful basis should not live forever in production.
Archive vs Migrate, Made Explicit
Inventory → policy → archive → lean cutover. Historical access survives without bloating the live CRM.
Age the Dataset
Contact and deal histograms show how much history is truly active versus dormant
Set Retention Rules
Migrate, archive, or purge by record type with sales ops and compliance sign-off
Park History Offline
Closed deals and inactive contacts land in a searchable cold archive, not production
Cut Over Lean
The new CRM opens with active pipeline only: faster search, cleaner reports, lower tiers
Everything You Need for a Defensible Data Retention Plan
Archive vs Migrate Policy
A signed retention schedule by record type: what stays live, what moves to a searchable archive, and what can be purged under POPIA and tax rules.
Closed Deal Cut Lines
Migrate recent closed-won deals for pipeline context. Archive older closed deals and closed-lost history so the live CRM stays lean without losing audit access.
Inactive Contact Rules
Clear thresholds (typically 18–24 months with no engagement) that send dormant contacts to archive instead of inflating marketing and CRM tiers.
Searchable Cold Archive
Vendor-neutral CSV/JSON or warehouse archive with an access path for sales ops and compliance, so "just in case" does not mean "pollute production".
Licence & Storage Modelling
We show how fewer live records cut Salesforce storage add-ons, HubSpot contact tiers, and migration runtime before you renew or cut over.
POPIA Retention Alignment
Retention periods tied to purpose, Tax Administration Act and Companies Act floors, with deletion or de-identification when the lawful basis expires.
Platforms We've Planned Archival Strategies For
From 185,000 Live Records to a Lean Cutover
How a Johannesburg industrial distributor stopped "migrating everything", archived dead history, and avoided nearly R300,000 a year in storage and marketing-tier fees.
Migrate Everything
- 185,000 contacts plus 42,000 closed deals spanning nine years queued for HubSpot
- No written archive vs migrate policy; sales feared losing "just in case" history
- Salesforce already burning storage overage blocks on obsolete activity
- Marketing quote priced on full contact count, including dormant leads
- Forecast reports mixed live pipeline with ancient closed-lost noise
Archive Then Migrate
- 118,000 active and recent records moved into HubSpot
- 52,000 inactive contacts and older closed deals parked in a searchable cold archive
- 15,000 junk and test records purged under a signed retention schedule
- Sales ops retrieves archive hits within a business day when needed
- Live search and list loads felt roughly 40% faster after the cut
Before vs After a Clear Data Retention Policy
How It Works
From first inventory to lean go-live in 3–6 weeks for most mid-market databases.
Inventory the History
Age histograms for contacts, closed deals, activities, and attachments so leadership sees what "migrate everything" actually means.
Agree Retention Rules
Sales ops, finance, and compliance sign off on migrate, archive, and purge criteria by record type.
Build the Archive
Export historical sets into a searchable, vendor-neutral archive with access controls and an erasure path.
Migrate Lean
Only live-worthy records enter the new CRM. Spot-checks confirm counts, reporting, and archive retrieval before dual-licence cutover.
Frequently Asked Questions
What is the difference between cleaning data and archiving it?
Cleaning fixes or removes bad records (duplicates, bounced emails, junk) so what you migrate is accurate. Archiving is the strategic decision of what should live in the new CRM versus what should sit in a searchable offline store: old closed deals, inactive contacts, and obsolete history. You usually need both, but they solve different problems.
How many years of closed deals should we migrate?
Industry practice is to keep recent closed-won deals in the live CRM (often the last 24 months for sales context) and archive older closed history for the full commercial retention window, typically around 7 years for contract-related records. Closed-lost deals older than 12–24 months almost always belong in the archive, not in active pipeline views.
Will archiving break our ability to look up old customers?
No, if the archive is designed for retrieval. We leave a documented access path (ops request queue, read-only legacy window for 90 days, or a simple search against the archive). Request volume usually drops sharply after the first quarter. What you avoid is slowing every daily search and report for records almost nobody opens.
How does POPIA affect CRM data retention?
POPIA Section 14 says personal information must not be kept longer than necessary for the purpose it was collected. Indefinite "just in case" storage is not a policy. Tax and company law set floors (for example Tax Administration Act records for 5 years, certain Companies Act records for 7 years), but marketing contacts without a lawful basis should not sit forever in a live CRM. A written retention schedule is the compliance artefact regulators expect.
How much storage cost can archival save?
Salesforce data storage overages are commonly quoted at about $125 per 500 MB per month (roughly R24,800 per block per year at current rates). File storage add-ons sit around $5 per GB per month. External cold archive storage is orders of magnitude cheaper. HubSpot and other platforms often price marketing capacity on contact volume, so inactive records you never message still raise the bill.
How much does a CRM archival strategy cost?
Policy design plus archive build and lean migration cutover for mid-market databases typically sits between R35,000 and R85,000 depending on volume and how many objects need retention rules. Against avoided storage add-ons, lower marketing tiers, and faster daily work, most clients see payback inside the first two quarters on the new platform.
Stop Dragging Dead Records Into Your New CRM
If your migration plan still says "bring everything across", you are about to pay for slower search, higher licence tiers, and murkier reporting for years.
Tell us which CRM you are leaving, how many contacts and closed deals you hold, and who needs historical access. We will show you a concrete archive vs migrate split and what it saves.