How to Migrate from SuiteCRM to Attio
Move Accounts, Contacts, Leads and Opportunities from SuiteCRM to Attio: which route Attio supports, what the export contains and what you rebuild by hand.
- Difficulty
- Moderate; depends on custom modules and the number of Leads
- Typical duration
- Estimate after a representative sample
- Downtime
- Agree a cutover and change-capture plan
- Native importer
- Import2 on paid Attio plans (SuiteCRM is a listed source); CSV and API are alternative routes
| SuiteCRM | maps to | Attio | What to watch |
|---|---|---|---|
| Account | Company | Attio matches companies by root domain; check the SuiteCRM website field and rows without one. | |
| Contact | Person | Attio matches people by email address; Contacts without an email become new records and can duplicate. | |
| Opportunity | Deal | Map sales stage, amount and close date to a Deal pipeline you set up first. | |
| Lead | Person, or Deal | No Lead object in Attio. Unconverted Leads need a rule: a status attribute on People, or a list. | |
| Note | Note | Import2 carries notes; Attio's CSV importer does not. | |
| Call, Meeting or Task | Task, note, or archive | Attio imports tasks through Import2 or the API, not CSV. Decide per activity type what is worth keeping. | |
| Custom module | Custom object | Create the Attio object and attributes before the import. |
What transfers cleanly
- Companies, people and deals, with the person-to-company link where SuiteCRM had one.
- Notes and tasks on Import2; the CSV route moves record fields only.
What doesn't come across
- Attio's Import2 does not bring over lists, call recordings, or attribute values on records that already exist in Attio.
- SuiteCRM workflows and reports are not data; rebuild the ones the team still uses.
- Drop-down fields export as their database IDs, so re-label them before a CSV import.
Migration order that works
- Count records per module in SuiteCRM and note which custom modules and fields are in use.
- Decide what happens to unconverted Leads and to related Calls, Meetings and Documents.
- Create the target Deal pipeline, select options and custom attributes in Attio.
- Run the Import2 sample on a paid plan, or export CSV from each module's list view and import with matching on domain and email.
- Import in dependency order on the CSV route: Accounts first, then Contacts, then Opportunities.
- Compare counts and spot-check associations, owners and dates, then agree a cutover date.
- Keep SuiteCRM read-only until owners sign off.
Choose the route first
Attio's page on migrating from another CRM lists SuiteCRM as a supported Import2 source. It needs a paid plan, an admin to run it, and a sample migration before the full run. The alternative is CSV: in SuiteCRM, tick records in a module's list view, open the Bulk Action menu, choose Export, and pick selected records, the current page or the whole module.
What the SuiteCRM export gives you
The CSV holds the fields in that module's export list and the record ID. Drop-down fields come out as database IDs, so a Priority of "High" can arrive as 1. Replace these with labels in the sheet. Attio's CSV importer takes up to 100,000 rows, 100 columns and 100 MB per file.
Import in dependency order
SuiteCRM's own guide advises importing Accounts before Contacts so relationships form. The same logic holds in Attio: Companies, then People, then Deals. Attio matches Companies by domain and People by email, so clean both columns first. Notes and tasks cannot come through CSV; use Import2 or Attio's API for them.
Need help moving from SuiteCRM to Attio?
Craftt, the CRM team behind weekcrm, plans and runs the migration: field mapping, deduplication, history and a cutover your team won't notice. You get a fixed quote within one business day.

