Create Accountor Login
Docs

Importing

Part of the MountDev Ops Workspace documentation. Updated November 17, 2026

MountDev Ops Workspace documentation | Updated November 17, 2026

Bring your records in from another system, or from a file, any time. Owners and admins import on Settings, in the Import card (the gear's Import), with Import From File. It is the same for every company.

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.
  • settings (optional): { "helpdesk": { "inboxes": [...], "number_prefix": "RIV-", "receipt_text": "...", "own_domains": "example.com, example.net" }, "email_template": { ... }, "proposals": { "valid_days": 14 }, "invoices": { "from_name": "...", "account_url": "https://...", "notes": "...", "terms": "..." }, "numbering": { "code": "RIV", "prefixes": { "invoices.invoice": "RIVI-" }, "last": { "projects.project": 120 } }, "team_agreement": { "title": "...", "body": "...", "link": "https://..." } } sets up Helpdesk's addresses, ticket numbering, and Our Email Domains (Helpdesk Settings, action helpdesk.settings.import), the company email template (Email Template, action core.email_template.import), the days a proposal is valid (action proposals.settings.import), Invoices' Invoice Details (Billing Settings, action invoices.settings.import), your Company Code, number starts, and last numbers used (Numbering, action core.numbering.import), and your team agreement, published as version 1 only while none is published (Team Agreement, action core.agreement.import). Each fills in only what you have not set yet, so importing again changes nothing you chose.
  • threads (optional): each old ticket's email ids, so a client's reply to an old email joins its ticket (action helpdesk.threads.import).

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).
  • A file can hold records for an app you have not added yet: Import From File offers Add the Apps It Needs first. Records for an app that is not available yet (one still coming in a later release) are left out with a note, "These records are for apps not available yet", and come in when you import the same file again once that app is here.
  • Time entries in a file (the core.time module) go in through the workspace's time tracking (Time Tracking). One with no project or task comes in as Unassigned time.

Running an Import Again Keeps Your Team's Work

Running an import again, such as to bring in data for an app you just added, never undoes what people did in your workspace:

  • Changed here: if anyone changed an imported record in your workspace since it was last imported (a person, an automation, or an AI agent; anything other than an import), the import leaves that record exactly as it is. Its record history is what tells. The row is listed with the reason "Changed here since the last import".
  • Deleted here: if someone deleted an imported record in your workspace, the import does not bring it back. The workspace remembers which records were deleted by their source_id. The row is listed with the reason "Deleted here". This applies to records deleted from the October 2026 update on; one deleted before then is not remembered and can come back, and deleting it again keeps it out from then on.
  • Not changed here: a record nobody has changed since its last import is still updated from the file, as before.
  • New: a row with a new source_id is added, as before.

The same goes for time entries brought in with the time import (Time Tracking).

When the import finishes, the summary shows how many records were added, updated, already up to date, kept your changes, deleted here and left out, and skipped. Download the Skipped Rows gives a file of every row that did not go in, with the reason for each: rows that did not fit, and rows left out because they were changed or deleted here. To take a newer value from the other system for a record your team changed, change it on the record by hand.

For AI Agents

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

Ask Us Anything

We’d love to hear from you!