Importing

Bring your records in from another system, or from a file, any time. Owners and admins import in Setup with Import From File.

What a File Looks Like

An import file is JSON. It names each module and its rows, in an order where every link points to a record that comes earlier in the file (companies before contacts, invoices before their lines):

{ "format": "mountdev-ops-import", "version": 1, "modules": [
  { "module": "crm.companies", "rows": [ { "source_id": "old:1", "name": "Acme" } ] },
  { "module": "crm.contacts", "rows": [ { "source_id": "old:7", "name": "Ann Lee", "company": { "source_id": "old:1" } } ] }
] }

• source_id: the record's id in the system it came from. Each row needs one.
• Links to another imported record are written { "source_id": "..." }.
• _created_at and _updated_at keep the original dates.

How It Works

Rows go in a few hundred at a time (action core.records.import), with a progress bar, until the whole file is in.

• A row whose source_id is new is added. A row whose source_id is already here updates that record instead, so running the same import again never makes copies, and it is safe to run again after fixing something.
• Every value is checked exactly as it is for records added by hand. A row that does not fit is skipped and listed with the reason; the rest go in.
• Each record's history notes that it was imported.
• Imported records count as usage (Records imported).

For AI Agents

AI agents never import. Bringing in records in bulk stays with people.