Move your Salesforce CRM data into Attio CRM

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

They land as Attio people, where the rest of your contacts are. Attio has no lead object, and a record your team can work is better than one sitting in a pool waiting to be converted. Lead status, lead source and rating have no Attio attribute to land in, so those are named on your plan before you commit to anything.

Your Salesforce tasks land as Attio tasks, which Attio has natively. Tasks you logged as calls or emails, and your events, land in one activities object we create in your workspace, because Attio ships no record for an interaction at all. Keeping all three kinds in one object means your history costs your plan a single slot rather than three.

They stay in Salesforce. Salesforce keeps notes as files rather than as activities, so we cannot read them the way we read your calls, emails, tasks and events. That one is our limit rather than Attio's, and it is on your plan before you commit to anything.

Because landing them means adding an object to your workspace, and Attio allows that only from Pro upwards. It is a choice on your plan rather than a surprise. Leave them out and this migration creates nothing in your workspace at all, and your accounts, contacts, opportunities, tasks and files still come across.

The stages do, the processes do not. Every stage your opportunities sit in is created on Attio's deal stage list before the load runs, so each deal arrives in the stage it was in. Attio keeps one list rather than a picklist per record type, so two processes that both have a Qualification stage arrive as one, and which process an opportunity ran through is not recoverable afterwards.

It lands in the stage that meant won, because the stage itself is what carries the meaning in Attio. Attio publishes no separate won or lost flag on a deal, so we do not invent one from a stage name. The close date is the harder loss and it is on your plan before you pay, since an Attio deal has no close date field.

Each one becomes an Attio object of its own, with its records and the fields you use on them. That needs a Pro workspace, since Attio allows an object of your own only from Pro upwards, and the free assessment tells you how many objects your migration would add before you commit to anything.

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. A Salesforce field with no native home in Attio can be brought along as a new attribute instead of being left behind.

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

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

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

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