# Move your Attio CRM data into Salesforce CRM

Your own attributes, your notes, your relationships. Not only the fields both apps happen to have in common.

Migratez runs Attio CRM to Salesforce CRM migrations. The assessment is free and comes before any commitment.

Canonical page: https://migratez.com/migrations/attio-to-salesforce-crm-migration

## What lands in Salesforce CRM

- Companies → Accounts
- People → Contacts
- Deals → Opportunities
- Notes → Salesforce tasks, on the record they were attached to (Salesforce keeps a note as a file rather than as an activity, so a task is where the text stays readable and reportable)
- Tasks → Tasks
- Files → Salesforce Files, on the record they were attached to
- Deal stages → Matched to the opportunity stages your Salesforce org already has (with any stage that has nowhere to go named before the run)
- The objects you added to your workspace → Salesforce custom objects, one for each
- The attributes you added → Created as custom fields on the object they belong to
- Workspace members → Matched to your Salesforce users by email (and you name who inherits the records of anyone with no match)
- References between records → Salesforce lookups and the contact roles on an opportunity (an opportunity keeps every person the Attio deal named rather than the first one)

## What comes across

Comprehensive by default, customizable on request.

- **Relationships, not just records.** The graph survives. Deals stay attached to the right contacts and companies, activities stay on the record they belong to, and the links between them are rebuilt in Salesforce CRM rather than left behind.
- **Your custom fields come with you.** They are found in Attio CRM and created in Salesforce CRM before a single record is written. Not flattened into a notes field.
- **History, not just the current state.** Notes, calls and meetings arrive on the record they belong to, with their owners and timestamps intact.
- **Owners, pipelines and stages are reconciled.** Matched to your Salesforce CRM users and stages rather than reset to a default.
- **Nothing is silently rewritten.** Where a conversion is genuinely lossy, the original value comes across alongside the converted one, so you can always see what the data was before we touched it.
- **A field with no home is brought along.** If Salesforce CRM has no native place for something you use, we can create one for it rather than drop it.

## What happens to the rest

- **How many custom fields Salesforce will hold per object depends on your edition** (requires_action). Salesforce caps custom fields per object, and the cap moves with your edition. An Attio workspace that has grown a lot of attributes of its own can exceed it. Instead: We count yours in the free assessment and show you the number against your edition's limit, so you can decide what to bring rather than find out during the run. Verified against https://help.salesforce.com/s/articleView?language=en_US&id=platform.custom_field_allocations.htm&type=5
- **Attached files count against a fixed storage allowance in your Salesforce org** (requires_action). Salesforce gives an org a file storage allowance rather than charging per file, and your Attio workspace's attachments land inside it. A workspace with a lot of attached files can push an org over. Instead: We total the bytes in the free assessment so the number is in front of you before anything is written. Verified against https://help.salesforce.com/s/articleView?id=xcloud.overview_storage.htm&language=en_US&type=5
- **Your notes and tasks share one pool of custom fields** (degraded). Your Attio notes land as Salesforce tasks, and Salesforce gives activities one allocation of custom fields shared across tasks and events, up to 300, rather than one each. So the attributes you added to notes in Attio and the ones you added to tasks draw on that single allowance. Instead: The free assessment counts them together, which is how Salesforce counts them. Verified against https://help.salesforce.com/s/articleView?language=en_US&id=platform.custom_field_allocations.htm&type=5
- **Attio CRM has no call, email or meeting to hand over** (unsupported). Attio has no record for a call, an email or a meeting. What it keeps instead is a handful of interaction attributes on a person or a company, first and last email, and first, last and next calendar event. Those are timestamps the Attio system maintains and nothing can write, which is a different thing from a history of who spoke to whom. So there is nothing to hand over, and Salesforce CRM's calls, emails and meetings will be empty of anything from before the move. Instead: Your notes, your tasks and the files attached to your records are the history that does come with you. Verified against https://docs.attio.com/rest-api/attribute-types/attribute-types-interaction
- **Nobody owned your companies** (unsupported). Attio's writeable attributes for a company carry no owner. Ownership lives on the deal in Attio. So Salesforce CRM's owner field on those records has nothing in your workspace to read, and you decide who inherits them rather than us guessing. Instead: You name who inherits them rather than us guessing, and every other field on those records comes across. Verified against https://docs.attio.com/docs/standard-objects/standard-objects-companies
- **Every deal value arrives in one currency** (degraded). Attio fixes a currency on the attribute rather than on the record, and its own reference says the code is shared among all values of that attribute and cannot be overridden for one record. So every deal value arrives in that one currency. If you traded in more than one, that is a thing to put right in Salesforce CRM afterwards rather than something this migration can recover. Instead: Every figure comes across intact. If you traded in more than one currency, the code is the thing to put right afterwards. Verified against https://docs.attio.com/rest-api/attribute-types/attribute-types-currency

## If it goes wrong

- **Undo the records we wrote.** Every write into Salesforce CRM is recorded, so one action takes the records we wrote back out again, in reverse. If it is not what you expected, restore and retry.
- **Paused, not lost.** A stop, an error or an API limit pauses the run at its last checkpoint rather than killing it. Nothing is lost and nothing is written twice.
- **Read-only in Attio CRM.** Nothing is ever written back into Attio CRM. It is the system you are leaving, and we only read it.
- **A last catch-up before you switch over.** After the main load, one action brings across everything that changed in Attio CRM since, so you can verify with both systems live and then switch over.

## What it costs

One price, one time, set by how many records you move.

- **From $399.** That covers up to 20,000 records. The price steps up with volume and it is for the migration, not a subscription. Nothing recurs.
- **The free assessment settles the number.** It reads Attio CRM and reports what is actually in it, so your price comes from your real record count rather than a sales call. You see it before you commit to anything.
- **A 30-day money-back guarantee.** Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of Salesforce CRM and refund you.

## Questions about moving Attio CRM to Salesforce CRM

### What happens to my call and meeting history?

There is none to move, and the reason is Attio's shape rather than ours. Attio has no record for a call, an email or a meeting. What it keeps instead is a handful of interaction timestamps on a person or a company, first and last email and first, last and next calendar event, which the Attio system maintains and nothing can write. So there is nothing to hand over one at a time. Salesforce has a place for calls, emails and events, and it will be empty of your Attio history. Your notes and tasks come across in full.

### Why do my notes land as tasks?

Because that is where they stay readable and reportable. Salesforce keeps a modern note as a file rather than as an activity, which puts the text out of reach of reports and list views. Landing your Attio notes as tasks on the record they belonged to keeps the text, the date and the record it was about, all of which a Salesforce report can see.

### Will the attributes I added in Attio come across?

Yes. The free assessment finds them in your workspace, and they are created as custom fields on the matching Salesforce object before a single record is written. You see that mapping before anything runs, and you can drop the attributes nobody fills in any more rather than carry them over.

### What about the objects I added to my workspace?

Each one becomes a Salesforce custom object, with its records and the attributes you use on them. The free assessment counts them against your edition's object and field allowances before you commit to anything.

### What happens to my deal stages?

Your deals are routed onto the opportunity stages your Salesforce org already has rather than into new ones we create, matched by what each stage meant. Attio keeps one ordered list, so there is one set of stages to place rather than several funnels. A stage with nowhere to go is named before the run rather than discovered during it.

### Who owns my accounts and contacts afterwards?

Attio models ownership on the deal and has no owner on a company or a person, so there is nothing in your workspace to fill the Salesforce owner field on those records. Your deal owners come across and are matched to your Salesforce users by email. On accounts and contacts you name who they should belong to, rather than us inventing an answer.

### What about products and the value on my deals?

An Attio deal carries a single value rather than priced lines, and Attio ships no catalogue object, so there is no price book and there are no opportunity line items to bring. The value on each deal comes across. One thing worth knowing is that an Attio workspace holds one currency per attribute rather than one per record, so every opportunity arrives in that same currency.

### Do I have to build a field map?

No. The mapping is written for this one direction and shown to you before anything runs, so your part is reviewing it rather than assembling it. An Attio attribute with no native home in Salesforce can be brought along as a new field instead of being left behind.

### Who actually runs the migration?

You create an account and connect Attio, and the free assessment tells you what is in it and what it costs. Salesforce is connected next, so we can check it against what your edition can hold. I run the migration itself and stay reachable while it does. Nothing moves until you ask for it.

### Can I keep working in Attio while this happens?

Yes. Nothing is ever written back into Attio, we only read it. After the main load, one action brings across everything that changed in Attio since, so you can verify with both systems live and switch over when you are ready.

### What if the result is not what I expected?

Every write into Salesforce is recorded, so one action takes the records we wrote back out again. You can sort out what was wrong and run it again.

### What does it cost?

One price, one time, based on how many records the migration moves. The free assessment counts them in your Attio workspace and gives you the exact price before you commit to anything. There is no subscription and no card form.