Import records from a CSV or another CRM

Mesy has two ways in for existing data. One loads a single CSV file into one type. The other takes several files from another CRM and keeps the links between them. Both start from a type’s page in the sidebar and both show you a dry run before anything is written.

Import one CSV into a type

To load a CSV into the type you’re looking at:

1. Click Import CSV in the toolbar.
2. Click Click to select a CSV file and pick the file. The file must have a header row.
3. Check the column list. Each CSV header has a selector, pre-set to the field Mesy matched by name; change any that are wrong. A field already claimed by another column can’t be picked twice.
4. Read the summary line: it reads a number will import, a number will skip and of N rows. Below it, the first rows show what each will become.
5. Click Import followed by the number of records.
6. The result reads a number of records imported, and skipped when some were, with any row errors listed as Row and the reason.

A warning reading Required field not mapped names any required field with no column; rows missing it will be skipped. A choice field may receive values that aren’t among its options. A mapping list then lets you keep each value as-is, skip it, or map it to an existing option. Every change reruns the dry run so the counts stay current. There’s no undo for this single-file import.

Import several files from another CRM

This path takes a ZIP or several CSV files at once, up to 25 files. A typical set is an accounts file, a contacts file and an opportunities file. Mesy works out which type each file feeds and which columns link the files together.

To run it:

1. Click Import from another CRM in the toolbar.
2. Click Select your export: a ZIP or several CSVs and choose the files. Leave Auto-match with AI ticked to have Mesy find the links between files and map columns for you.
3. On the review screen, read the Import order and open each file’s card.
4. For each file, check the Type, the ID column (the column holding the source system’s record id) and the column mapping. Columns the AI matched are listed under AI matched.
5. Set Source timezone for date columns, and Owner column if a column names the record owner; otherwise the importer owns every record.
6. Tick Merge duplicates to update existing records instead of creating new ones. The summary then reads counts that will create, will update and, when a row matches more than one record, ambiguous.
7. Click Import followed by the total number of records.
8. The result reads the number created, updated and linked, with a per-file breakdown.

A file Mesy can’t place is listed as not matched and won’t import unless you pick a type for it. Choose one from its selector or leave skip.

Each file’s links show as the field, the target type and a count such as 12/14, with any unmatched rows counted. An unmatched link means the target row wasn’t in the files.

Create missing fields during a CRM import

A column with no matching field can become a new field. Under Create missing fields, tick the column and choose a field type. The note reads Creating a field requires an admin to commit. A member or manager can review and adjust the whole plan. The Import button reads Admin required to commit until an admin runs it. New choice options work the same way.

Reuse a mapping

On a file’s card, click Save this mapping and give it a name in the prompt. The next time you import, pick it from Load saved mapping… on any file card to apply the same type, columns and settings. Saved mappings are shared across the workspace.

Undo a CRM import

On the result screen, click Undo import. Mesy deletes every record the run created and puts back the previous values on records the run updated. The screen then reads Import reverted. Fields and options the import created stay; the result notes they’re not removed by undo, and an admin removes them by hand.