Data Import

Settings → Data Import brings records in from a spreadsheet saved as CSV: up to 10,000 rows at a time. Each row is saved exactly as if someone entered it by hand, so the same checks, duplicate rules, workflow rules and flows apply.

What you can import

Accounts, contacts, leads, opportunities, cases and products, with their standard and custom fields. You need the Import records permission (Admin and Manager profiles), and permission to create or edit the object you’re importing.

Choose	What happens to each row	Use it to
Add new records	Becomes a new record	Load data from a spreadsheet or another CRM
Update existing records	Updates the record with its Record ID; only filled-in cells change	Fix or enrich data you exported from CRMSix
Add or update by External ID	Updates the record with that External ID, or adds one if there is none	Keep CRMSix in step with another system, run after run

Prepare your file

Save it as CSV with a header row. From Excel, choose CSV UTF-8 so accented and non-Latin letters come through.
Up to 10,000 rows and 20 MB. Split bigger files.
Name columns after the fields (“Account Name”, “First Name”, “Email”, “Close Date”); CRMSix matches them automatically.
Dates: 2026-03-31 or 3/31/2026. Yes/no: yes, no, true, false, 1, 0 or x. Numbers: commas and currency signs are fine.
Picklists: the value or its label, in any case (“high” for High).
To update existing records, start from a Data Export: it has each record’s ID.

Import step by step

Go to Settings → Data Import.
Choose the object and what to do (add, update, or add or update by External ID).
Choose Choose CSV file. CRMSix shows how many rows and columns it found.
In Match columns to fields, check where each column goes; change any, or choose Don’t import for columns you don’t need. Required fields are marked with *.
In Check and import, look at how the first rows will be read and fix anything listed.
Choose Import … rows into …. A progress bar shows rows added, updated and with errors; you can Stop at any time.

Linking to other records

A row can link to another record, for example a contact to its account. In the mapping, choose how the column names it:

Link	Can be matched by
Account, Contact	Record ID or External ID
Owner	Email address, Record ID or External ID
Support team (cases)	Name

Tip: import accounts before contacts, opportunities and cases, so the rows they link to already exist.

Results and errors

Rows with a problem are skipped and listed with their line number and the reason, for example a missing required field or a picklist value that doesn’t exist. The others are saved.
Download rows with errors gives a CSV of just those rows with an Error column: fix them and import that file.
Past imports lists who imported what, when, and how many rows were added, updated and failed. Imports also appear in the Admin Activity Log, and field history shows the changes as Import.

Automation during an import

Workflow rules and flows run for each imported row, as they do when records are saved by hand, including the emails they send. If you don’t want those emails for a big load, deactivate the rules or flows that send them first, and turn them back on afterwards.

Tips

Try a small file (10 rows) first, then the rest.
Give records an External ID when they come from another system; later imports can then update them instead of adding duplicates.
Cases can also be imported from the Cases list (Import), which keeps original created dates.