By Touchbase Technologies · Published

A customer contact backup plan you can actually restore

A downloaded contact list is useful only if you know what it contains and can recover the records you need from it. A file of names and email addresses may leave out company relationships, deal history, notes, contact preferences or the IDs needed to update records without creating duplicates.

Build a small recovery process before you need it. Inventory the records, check what each export includes, store an independent copy securely and test a limited restore with sending disabled. You do not need to move your whole business to another CRM to find out whether the backup works.

Two colleagues compare restored customer records with a checklist beside an independent backup drive and a locked filing cabinet.

Start with the work you need to recover

Ask what you would need if the primary account were temporarily unavailable or a mistaken import changed important records. Would you need to return a customer’s call, identify the owner of an open deal, honor an unsubscribe request or rebuild the sequence of a service conversation?

Write down those tasks. Then identify which information each task requires and which system currently holds it. This turns “back up the CRM” into a list you can check. NIST’s small-business cybersecurity guidance recommends inventorying important assets and services and protecting and testing backups. The inventory below applies that principle to contact operations.

Record groupDetails to identifyA recovery question
People and organizationsStable IDs, names, contact details, company relationshipsCan you match a person to the correct organization?
OpportunitiesDeal IDs, stages, owners and related contactsCan you find who was handling an open opportunity?
Activity contextNotes, calls, emails or links to their separate archiveCan you understand what was discussed without guessing?
Contact preferencesSubscriptions, opt-outs, source and relevant datesCan you prevent a restore from restarting unwanted contact?
Supporting filesDocuments and attachments referenced by recordsCan you actually open the material, rather than only its filename?
ConfigurationProperty definitions, mappings and relevant workflow settingsCan you interpret the exported fields?

Some of those items may need separate exports or a dedicated recovery service. Do not assume one CSV includes everything in the table.

Check what the platform exports

Use the platform’s current documentation and the permissions available in your account. In HubSpot, record exports contain current property values and associations, and exporting requires the appropriate permission. The documentation distinguishes record exports from exporting activities such as notes and calls. Review the selected view, properties and association options instead of assuming a default export is complete.

For Salesforce, its disaster-recovery guidance separates data backup from metadata backup and connects export frequency with recovery requirements. A data export and the configuration needed to interpret or recreate it are different parts of the plan. Available export schedules and recovery tools depend on the account and edition; verify those in the administrator’s current documentation.

Keep a short manifest beside each backup: system, account, export time and timezone, record groups, filters, field names, file count, approximate row count and the person who checked it. Record omissions. A clear statement that activity history is missing is more useful than a misleading folder named “complete backup.”

Preserve identifiers and relationships

Names are not reliable record keys. Two people can share a name, a company can change its name, and an email address can change or belong to a shared inbox. Preserve the source record IDs and the relationship fields your restore process needs.

If you are preparing an import into another system, decide how the source IDs will be stored or mapped. Do not assume a source system’s internal ID can be placed in the destination’s own ID field. Test the destination’s documented matching rules in a safe import area or sandbox first.

For a hypothetical appointment service, the backup might include these related entries:

FileExample keyRelationship to preserve
Organizationsorg-demo-17Organization associated with the customer
Contactscontact-demo-42Organization key org-demo-17
Opportunitiesdeal-demo-8Contact key contact-demo-42 and an assigned owner
Preferencescontact-demo-42A recorded do-not-email status and its source date

The example IDs are invented. The point is that recovering the contact’s name without its organization, owner or preference can produce an incomplete operational record.

Make the copy independent and access-controlled

A backup stored only inside the same account that you are trying to recover may not help when that account is unavailable. Choose a separate approved storage location, limit who can access it and use the storage provider’s access protections. Do not place a customer export in a public link or a shared folder available to people who do not need it.

The UK National Cyber Security Centre’s backup guide emphasizes checking restoration and protecting backup storage. If you use a removable drive, keep it secure and disconnect it when it is not being used. For online storage, use the account protections supported by that service.

Do not turn “independent” into “uncontrolled copies everywhere.” Give the backup a named owner, a documented location and a retention process appropriate to the information and your business obligations. Keep customer data out of public example files and avoid uploading raw exports to an unrelated AI tool merely to summarize them.

Choose a schedule from acceptable data loss

Decide how much recent work you could reasonably reconstruct and how long recovery may take. A business with frequent changes may need a different backup approach from one that updates a few contacts each month. Check the export or backup features actually available to you before promising a schedule to the team.

For example, suppose a team chooses a weekly export and then adds 30 contacts and changes 12 opportunity records before the next copy. A recovery from the older file would not contain those later changes. The numbers are hypothetical, but the gap is real: the existence of a backup does not mean it contains today’s work.

Record the last successful export, the last successful restore check and any failed run. A scheduled job that stopped producing usable files should be visible to someone who can fix it.

Run a small restore drill with sending disabled

Use a sandbox, test environment or isolated destination that does not automatically enroll restored contacts in campaigns. Keep reminders, integrations that trigger messages and other sending workflows disabled during the drill. Never use real customers to discover whether an import sends a welcome email.

  1. Choose a small authorized sample that represents different record types and contact preferences.
  2. Check the manifest and confirm that the files can be opened and their encoding and dates make sense.
  3. Map fields and identifiers according to the destination’s documented rules.
  4. Import or restore the sample without activating campaigns.
  5. Check relationships, owners, notes or their separate archive, and contact restrictions.
  6. Repeat the sample import only if appropriate and confirm that the matching rules do not silently create duplicates.
  7. Record what worked, what was missing and the changes needed before a larger recovery.

In the appointment-service example, a useful pass condition is that contact-demo-42 is linked to org-demo-17, the open opportunity has the correct owner, and the do-not-email status remains in force. A row-count match alone would not prove those conditions.

Distinguish sync from recovery

A connector that synchronizes new changes can be useful, but it is not automatically a historical backup. Check whether deletions and mistaken updates also synchronize, whether earlier versions are retained, and what a restore actually does. A second application showing the same current records may be a mirror of the mistake you need to undo.

Keep the recovery instructions somewhere authorized staff can reach if the primary application is unavailable. Include the responsible person and the checks required before any restored contacts are eligible for communication again. Restoration does not create new marketing permission.

Questions

Is a CSV enough to back up my customer contacts?

It can be part of the process. Check whether it includes the fields and relationships you need and whether activity history, files or configuration require separate exports. Test a sample restoration before relying on it.

How often should I export contacts?

Choose a frequency based on the changes you need to recover, the time you could tolerate losing and the features your account supports. Review the decision when the business or workflow changes.

Should restoring a contact restart its campaigns?

Keep sending disabled during a recovery test. Preserve contact preferences and suppression records, and review workflow enrollment before returning any recovered records to normal operations.

Published by the Touchbase editorial team. This is a general continuity checklist, not a claim that Touchbase supplies a complete CRM backup service. See current Touchbase plans for its product scope.

Prepared with AI assistance and checked against the sources linked in this guide.