Chapter 3: Asset Taxonomy and Pre-Migration Hygiene

When a team prepares to move to a new CRM, the most common instinct is to simply export the entire historical database and push it into the new system.

This is a dangerous misconception. If you migrate broken, duplicate, or outdated processes, you do not solve your operational problems — you simply transplant them into a new, often more expensive, environment.

The Pre-Migration Purge

Think of a CRM migration like moving to a new physical headquarters. You would not pack up the garbage from your old office and pay to ship it to the new one.

Your legacy CRM is likely full of clutter. Before migrating, you must systematically audit your current instance and permanently remove data you do not plan to use in the future.

Purge Completion

GDPR Compliance Mandate

Retaining unengaged contacts for more than two years is a direct compliance violation under regulations like GDPR. You must actively avoid carrying non-compliant data over to your new system. Purging this data is not just good database hygiene — it is a legal necessity.

The Asset Taxonomy: Migration vs. Translation

Once the dead data is purged, you must categorize what remains. Different systems use different underlying architectures, so not everything can be moved the same way.

Migration Assets

Direct 1:1 mapping — standard fields and logs that copy cleanly between systems.

Translation Assets

Manual rebuild required — automation, forms, and reports that break on direct import.

■ Migration — Direct 1:1 mapping ■ Translation — Manual rebuild

If you encounter translation assets too complex to adapt easily, your task force must establish a plan before the migration begins. You may decide to back them up externally or sunset them entirely.