Prepare a clear source

Identify the customer accounts and contacts you want to bring across. Check names, email addresses, duplicates and the identifiers that connect contacts to accounts. Agree which source is authoritative when the same customer appears in more than one file.

Keep a copy of the original data and work with a representative sample first. A small test should include the awkward cases, not only the easiest rows.

Map and review before committing

  • Match source columns to the intended destination fields.
  • Check required fields, formats and customer relationships.
  • Review validation errors and skipped rows.
  • Compare the imported records with the source sample.

For example, importing contacts without their account relationship may leave useful names disconnected from the customer history. Include that relationship in the sample review.

Agree the migration scope

An account-and-contact import is a different project from moving emails, files, custom objects, ownership rules and historical activity. Confirm which data types the chosen tool supports, then plan the remaining work explicitly.

HOW THIS RELATES TO ATLAS

In the current workspace

Pro and Enterprise include supported Account/Contact CSV staging and import flows. Enterprise also exposes bounded Salesforce discovery and extraction/staging. A complete migration of every Salesforce object, attachment and activity is not currently provided.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.