How to Migrate from OnePageCRM to Attio
Move OnePageCRM contacts, deals and notes into Attio: which export to take, what Import2 covers and what happens to Next Actions and stored emails.
- Difficulty
- Moderate
- Typical duration
- Estimate after a representative sample
- Downtime
- None needed if you freeze edits between the sample and the final import
- Native importer
- Import2 (OnePage CRM is a listed source on Plus, Pro, Enterprise and Ultra plans); CSV is the alternative
| OnePageCRM | maps to | Attio | What to watch |
|---|---|---|---|
| Contact | Person | Attio matches existing people by email. Import2 does not overwrite attribute values on a matched person. | |
| Organization (on a contact or deal) | Company | Attio matches companies by domain; OnePageCRM exports an organization name, so check that websites are filled in. | |
| Deal | Deal | The export includes pipeline name, deal stage, amount, close date, owner and deal custom fields. Enable the Deals object in Attio first. | |
| Next Action (text and date) | Task | OnePageCRM lists Next Action text and date as contact import fields. Check in the export file whether they are present before you plan on them. | |
| Note and call history | Note | Use the Contacts dataset that includes notes and calls. Check call entries after import. | |
| Stored email and attachment | Not migrated | OnePageCRM states that emails and attachments stored in the CRM cannot be exported. | |
| Tag | Attribute (select) or list | Contact export filters include Tag, Status and Lead source. Decide whether each becomes a select attribute. |
What transfers cleanly
- Contacts and organizations with the person-to-company link.
- Deals with stage, amount and close date.
- Notes and calls from the contacts export that includes them.
What doesn't come across
- Emails and attachments stored in OnePageCRM cannot be exported, so they stay behind.
- Delivery pipeline deals export only as Closed Deals.
- Import2 does not update attributes on Attio records that already exist.
- Phone numbers need a country code and emails must be valid, or Attio rejects the value.
Migration order that works
- Export contacts under Import and Export, Contacts Export to file, with the dataset Contacts (Inc. notes, calls, etc.).
- Export deals twice, as Pending Deals and as Closed Deals (Won or Lost).
- Save the files. They are the only copy of stored-email history you will have outside OnePageCRM.
- Enable Deals in Attio and create the pipeline stages you want.
- Run an Import2 sample and compare 10 contacts, 5 pending deals and 5 closed deals.
- [object Object]
- Run the full import and have each deal owner confirm their pipeline.
Two exports, one decision
OnePageCRM splits its export: contacts under Import and Export, Contacts Export to file, and deals under Deals Export to file. The contacts dataset has an option that adds notes and calls. The deals file carries pipeline name, stage, amount, close date and custom fields. Take both before any import and keep them.
Next Actions are the part that needs a choice
OnePageCRM is built around the Next Action: every contact can carry one, with a date. Attio has tasks, and Import2 moves tasks. Whether your Next Actions come across depends on what is in your export file, which the help article does not settle. Open the contacts file, find the Next Action columns, and recreate the open ones as Attio tasks assigned to the right owner. Completed ones rarely justify the effort.
What stays in OnePageCRM
Stored emails and attachments cannot be exported. If your team negotiates by email inside OnePageCRM, keep the account on a read-only plan for the period you need that history, or save the threads from the mailbox. Attio's mailbox sync covers mail from the day you connect.
Need help moving from OnePageCRM 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.

