Move the do-not-contact history before you move the campaign
Preserve opt-outs, wrong-number flags, contact preferences and consent context during a CRM migration before enabling messaging in the new workspace.
·3 min read
A contact export often looks complete because it includes names and phone numbers. The dangerous omissions are less visible: an opt-out date, a wrong-number note, an unresolved complaint or the reason the old CRM stopped messaging.
Make suppression the first migration workstream. The goal is to preserve contact choices and useful operating context while the team changes tools. Registration with a provider does not replace the need to evaluate each audience's eligibility.
Inventory suppression wherever it lives
Review the old CRM, messaging provider, spreadsheets, vendor records and manual agent notes. Identify global opt-outs, number-level blocks, channel preferences, wrong-number flags and internal holds. These records may not all be included in a default contact export.
Record the source and timestamp when available. Separate a person's request to stop texting from a technical delivery failure. Do not flatten every non-active record into one ambiguous status that the new team cannot interpret.
Normalize matching keys carefully
Standardize phone numbers with explicit country context and retain original values for reconciliation. Keep email and external IDs as supporting keys. A misplaced country code can cause a suppression record to miss its corresponding contact.
Handle shared numbers and conflicting records conservatively. If one matching record is opted out and another looks active, flag the conflict before enabling sends. Do not choose the active value merely because it makes the import easier.
Map operational flags and consent context
Document which destination field or suppression mechanism represents each source status. Carry the consent source, evidence reference and recorded time where available. Missing evidence should remain missing; do not manufacture a consent date during migration.
Create a separate hold reason for unresolved records. An archived conversation may still need suppression, while an active conversation may already be opted out. Folder location is not a reliable messaging-eligibility rule.
Verify suppression before enrolling anyone
Use internal test records representing an opt-out, wrong number, missing consent context and eligible contact. Attempt the planned enrollment or send path and confirm the expected outcomes. Reconcile imported suppression totals against the source.
Check all send paths you intend to use: campaign, manual message, AI response and vendor-triggered enrollment. A block that works in one screen but is ignored by an integration leaves the migration incomplete.
Control the overlap period
Choose which system owns new outreach and stop competing campaigns during cutover. Keep the old system accessible for reconciliation where your retention arrangements allow it. Document how new opt-outs received during the transition reach the new workspace.
Run a small eligible pilot after the suppression checks pass. Review exceptions and source totals before expanding. Exporting contacts is a technical step; preserving their history is what makes the operational move dependable.
Key takeaways
- →Export suppression from every relevant system, not only contacts.
- →Keep opt-outs distinct from delivery failures and archive status.
- →Resolve conflicting flags before enabling outreach.
- →Test suppression across campaigns, manual sends, AI and integrations.
Put this into practice with Text2Sale
Import leads, create follow-up campaigns, organize replies, and connect texting, calling, and appointments in one workspace.
Frequently asked questions
Can I reset opt-outs when moving to a new CRM?
A change of software does not erase the contact's request or establish new consent. Preserve the suppression and handle any legitimate renewed permission under the applicable rules and provider policies.
Do I need to migrate every historical message?
Determine what the destination supports and what your retention requirements require. At minimum, preserve the actionable suppression, preferences, evidence references and context needed to handle the person appropriately.