Attio to Salesforce migration
We migrate People, Companies, Deals, Custom Objects, and relationship attribute chains from Attio into Salesforce Sales Cloud, resolving the CSV flattening gotcha by querying relationship attributes via the API before writing foreign-key chains, and flagging every object that exceeds Salesforce tier capacity before any data moves.
FlitStack AI migrates lead or contacts, accounts, opportunities, opportunity accountid lookups and opportunitycontactroles from Attio to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Attio to Salesforce?
Moving from Attio to Salesforce Sales Cloud is a schema-translation migration.
Read the full summary
Attio's flexible object model treats records as rows across configurable tables, while Salesforce enforces a fixed Account-Contact-Opportunity hierarchy with a separate Lead object for unqualified prospects. We resolve that structural split during scoping, reconstruct relationship chains that Attio's flat CSV exports discard, and validate that the destination Salesforce plan supports the full object count before migration begins. We migrate People (split by lifecycle), Companies (1:1 to Account), Deals (1:1 to Opportunity with stage mapping), Custom Objects, Notes, Tasks, and engagement history via the Bulk API 2.0. Attio Lists become segmentation logic in Salesforce; we do not migrate Attio Workflows, Sequences, or automations as code and instead deliver a written inventory for the customer's admin to rebuild in Salesforce Flow.
People → Lead or Contact (split required)
Attio People with no associated Deal or Company relationship, or with lifecycle_status set to unqualified, map to Salesforce Lead.
How it maps
People linked to Deals or Companies map to Salesforce Contact attached to the corresponding Account. We compute the split using Attio's relationship attributes and lifecycle_status at migration time, and preserve the original lifecycle_status in a custom field attio_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.
Companies → Account
Attio Company records map 1:1 to Salesforce Account.
How it maps
The company domain becomes the Account Website field and serves as the dedupe key during import. Account is created before any Contact import so the AccountId Lookup is satisfied at the moment of Contact insert, preventing orphaned Contact records.
Deals → Opportunity
Attio Deal records map 1:1 to Salesforce Opportunity.
How it maps
The Attio deal pipeline and stage attributes map to a Salesforce Record Type and Sales Process we configure before migration. Closed-Won and Closed-Lost reason attributes from Attio become Salesforce Loss Reason and custom Win Reason fields. We set CloseDate from the Attio expected_close_date attribute, defaulting to 30 days if the field is null.
Relationship Attributes (Deal → Company) → Opportunity AccountId Lookup
Attio relationship attributes encode foreign-key links (e.g., a Deal linked to a Company).
How it maps
CSV exports flatten these links. We query relationship attributes via the Attio API to reconstruct the Deal-to-Company chain before migration, then write the resolved AccountId to the Opportunity during import. Without this step, Opportunities arrive orphaned from Accounts.
Relationship Attributes (Deal → People) → OpportunityContactRole
Attio Deals linked to multiple People records use relationship attributes to define a many-to-many chain.
How it maps
We resolve each linked Person to a Salesforce Contact via the Lead-Contact split, then create OpportunityContactRole junction records during migration to preserve the deal-to-contact association. Null Contact references (unresolved People) are held in a reconciliation queue.
Custom Objects → Custom Object (__c)
Attio custom objects (Gated: Free 3, Plus 5, Pro 12, Enterprise unlimited) migrate to Salesforce custom objects of matching API name with __c suffix.
How it maps
We pre-create the destination schema in Salesforce before any data import, including all custom fields, picklist values, and lookup relationships. If the source workspace uses more custom objects than the destination Salesforce plan supports, we flag the excess during scoping and either recommend a Salesforce edition upgrade or consolidate objects.
- PeopleLead or Contactsplit
- CompaniesAccount1:1
- DealsOpportunity1:1
- Relationship AttributesOpportunity AccountId Lookuptransformed
- Relationship AttributesOpportunityContactRoletransformed
- Custom ObjectsCustom Object1:1
+ 7 more in the mapping below
How Attio and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Attio | Salesforce |
|---|---|---|
| Object model | Flexible relational — create any object, define any attribute type | Fixed Account-Contact-Lead-Opportunity hierarchy with custom objects on Professional+ |
| Custom object availability | Free 3, Plus 5, Pro 12, Enterprise unlimited | Professional ($80/user) unlocks unlimited custom objects without setup fee |
| Pipeline count | Single pipeline on Free/Plus; multiple pipelines on Pro and Enterprise | Unlimited Opportunity record types and sales processes at all paid tiers |
| Pricing model | Per-seat plus unpredictable workspace credit consumption for automation | Per-user; no consumption-based surprises on the base license |
| Reporting depth | Weak pipeline analytics, limited data visualization per G2 reviews | Advanced multi-dimensional reporting with custom fiscal periods and territory analysis |
| Integration ecosystem | Thin native library; third-party sync platforms required for common GTM tools | AppExchange with 9,000+ certified integrations including ERP, CPQ, and revenue intelligence |
| Activity timeline | Automatic email and calendar sync for People and Company records only | Task, Event, and EmailMessage objects with full engagement history importable via Bulk API |
What to watch for in a Attio to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
CSV exports flatten relationship attribute chains
Attio's workspace export produces flat CSV files per object.
How we handle it
Relationship attributes (which Company a Deal belongs to, which People are linked to a Deal, which custom object is a parent to another) do not export as join keys. We handle this by querying relationship attributes directly via the Attio API to reconstruct the full parent-child chain before writing any records to Salesforce. Without this step, Deals arrive orphaned from their Companies, Opportunities lack Contact roles, and custom object hierarchies are severed. This is a pair-specific risk because Salesforce's foreign-key model makes orphan records immediately visible as broken Lookups.
Custom object count may exceed Salesforce plan capacity
Attio plans gate total object count (3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise).
How we handle it
If the source workspace has more custom objects than the destination Salesforce plan supports, migration fails on object creation. Salesforce Professional ($80/user) provides unlimited custom objects. We audit the source object count during scoping, map it against the destination plan, and flag a Salesforce edition upgrade recommendation before migration begins. This is pair-specific because Attio's object model encourages more custom objects than traditional CRMs, making the ceiling more likely to bind.
Email and calendar sync does not cover custom object records
Attio's automatic email and calendar sync only attaches to People and Company records.
How we handle it
Custom object records—Subscriptions, Projects, Partnerships, Investors—cannot receive activity history imports via Attio's sync or API. We flag this during scoping and note it in the data loss disclosure. Notes attached to custom objects do migrate; automatic engagement history does not. Salesforce Activity records created from this gap cannot be backfilled post-migration from Attio's side.
Attio Lists are not records and have no direct Salesforce equivalent
Attio Lists are dynamic or static collections of record IDs scoped to a workflow context, not standalone records with timestamps or ownership.
How we handle it
There is no 1:1 migration to a single Salesforce object. We extract list memberships and reconstruct them as Salesforce Campaign members (for behavioral segmentation) or static List Views (for team-facing segmentation), but the original list creation date and owner attribution do not carry over. The customer's admin chooses the reconstruction strategy during scoping.
Credit-gated objects require plan audit before migration
Attio's plan tiers gate object creation, email sync, and workspace credits.
How we handle it
Plus plans include 1,500 credits/month consumed by AI enrichment and automation steps. If the source workspace is on a lower plan during migration scoping, some features may not be available via API even if the data exists. We validate the source plan tier and credit balance during discovery and flag any API-gated exports that require a plan upgrade or credit pack purchase before export begins.
How the migration runs
Discovery and plan audit
We audit the source Attio workspace across plan tier (Free/Plus/Pro/Enterprise), total object count, custom object names and attribute types, relationship attribute chains, People lifecycle status distribution, active Deals with stage values, Notes volume, Tasks, and engagement history.
What this step covers
We validate the workspace credit balance and flag any API-gated exports that require plan upgrades. We pair this with a Salesforce edition assessment: Professional ($80/user) covers most migrations; Enterprise ($165/user) is required for advanced Flow, multi-org, or territory management. Discovery output is a written migration scope with object inventory, plan comparison, and a Salesforce edition recommendation.
Relationship chain reconstruction via API
We query Attio's relationship attributes via the API for every object pair that has cross-references (Deal → Company, Deal → People, custom object → custom object).
What this step covers
We build a relationship index that maps each Attio record ID to its parent and child record IDs. This index is the critical input to the Salesforce import step; without it, CSV exports alone produce orphaned records in Salesforce's Lookup-heavy model. We validate the relationship chain completeness and flag any records with broken references before the first Salesforce insert.
Salesforce schema design and tier validation
We design the destination Salesforce schema: custom objects (with __c API names matched to Attio names), custom fields, Record Types per Attio pipeline, Sales Processes per Record Type, Page Layouts, and the Lead-Contact split rule based on the customer's Attio lifecycle_status distribution.
What this step covers
We validate that the destination Salesforce plan supports the full object count and custom field count before schema deployment. Schema is deployed into a Salesforce Sandbox first for validation; production deployment follows after sign-off.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-like data volume.
What this step covers
The customer's RevOps lead reconciles record counts across all objects, spot-checks 25-50 random records against the Attio source for field-level accuracy, and verifies that relationship chains are intact (e.g., Opportunities have AccountIds, Contacts have AccountIds, Deal-to-Contact roles are present). Any mapping corrections happen in the sandbox, not in production. Owner reconciliation also completes here with admin provisioning missing Users.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Attio Companies), Leads and Contacts (with lifecycle split applied and AccountId resolved), Opportunities (with AccountId, OwnerId, RecordTypeId, and CloseDate resolved), Products and Pricebook entries (if migrating quoting), OpportunityLineItems, Notes (via ContentDocumentLink), Tasks, Activity history (EmailMessage, Task with subtype, Event via Bulk API 2.0), Custom Objects (with custom field lookups resolved from the relationship index), and Campaign members (from Attio Lists).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, delta sync, and handoff documentation
We freeze writes in Attio during cutover, run a final delta migration of any records created or modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We deliver a written inventory of every Attio Workflow and Sequence with its trigger, conditions, and recommended Salesforce Flow equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Attio Workflows or Sequences as Salesforce Flow within the migration scope; that is a separate engagement or an internal admin task. We do not migrate Attio Forms; Salesforce Web-to-Lead or Experience Cloud forms are the recommended replacement.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, relationship chain complexity, and custom object count. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Attio to Salesforce →Why teams move from Attio to Salesforce
- Attio's reporting features lack depth compared to Salesforce. Users consistently cite weak pipeline analytics, missing date-based segmentation, and limited data visualization as ongoing frustrations on G2 and Capterra. Salesforce Sales Cloud delivers multi-dimensional reporting with custom fiscal periods, territory analysis, and cross-object reporting types that Attio's current feature set cannot match, especially for teams managing complex multi-product or multi-geography pipelines.
- Attio's integration library is thin and requires third-party sync platforms for common GTM tools like Aircall, Outreach, and Marketo. Salesforce's AppExchange with over 9,000 certified integrations provides native or partner-certified connections to ERP systems, CPQ platforms, revenue intelligence tools, and industry-specific applications that Attio cannot match without custom API work.
- Attio's workspace credit model creates unpredictable monthly costs. AI enrichment, automation steps, and data enrichment each consume credits from a shared bucket, and teams running workflows at volume purchase additional credit packs ($70/month for +5,000 credits) on top of seat pricing. Salesforce's per-user model is more predictable for established sales teams, removing the consumption-surprise dynamic that inflates Attio's effective cost beyond the seat price.
- Attio's flexibility creates a steep learning curve for non-technical team members. Features that attract technical founders—schema-on-write, custom attribute types, relational object design—become adoption blockers for sales reps, marketers, and CS teams who expect a pre-built CRM experience. Salesforce's established UI patterns, documentation, and partner ecosystem make it easier to onboard diverse team members even if the admin experience is more complex.
- Teams using Attio's Pro plan at its 12-object ceiling need to move to Enterprise for unlimited objects. Salesforce Professional ($80/user) provides unlimited custom objects at a lower per-seat price than Attio Enterprise custom pricing, making Salesforce the more cost-effective destination for data-model-heavy use cases like Subscriptions, Investors, or Partnerships.
Questions, answered
Attio to Salesforce migration questions
How long does an Attio to Salesforce migration take?
Most migrations land between four and six weeks for accounts under 20,000 People, 8,000 Deals, and fewer than five custom objects with clean relationship chains. Migrations with custom objects, multi-hop relationship graphs, large activity histories (over 300,000 records), or Salesforce edition upgrades driven by object-count analysis move to eight to fourteen weeks. Relationship chain reconstruction via the Attio API and Salesforce Bulk API chunking for activity history are the primary timeline drivers.
Do Attio Workflows and Sequences migrate to Salesforce?
No. Attio Workflows consume workspace credits and are automation-context objects; Salesforce Flow is a structurally different record-triggered, scheduled, and screen flow model. Sequences (Pro and Enterprise only in Attio) are sales engagement cadence objects with no direct Salesforce Sales Cloud equivalent. We do not migrate them as code. We deliver a written inventory of every active Attio Workflow and Sequence with its trigger, conditions, action blocks, and a recommended Salesforce Flow or Sales Engagement equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration.
Will we lose the relationship chains between Attio records?
No, if the migration uses API-based relationship querying rather than flat CSV export. Attio's workspace export produces separate CSV files per object with no join keys for relationship attributes. We query relationship attributes directly via the Attio API to reconstruct the full parent-child chain (Deal → Company, Deal → People, custom object → custom object) before writing to Salesforce. This is the critical step that prevents Deals from arriving orphaned from Accounts and Opportunities from arriving without Contact roles. If you attempt migration using only CSV exports without API-based relationship reconstruction, relationship chains will be broken.
What happens to our Attio Lists in Salesforce?
Attio Lists are dynamic or static collections of record entries with no standalone timestamp or ownership; they do not map directly to any single Salesforce object. We extract the list memberships during scoping and reconstruct them as Salesforce Campaign members (for behavioral or segmentation lists) or static List Views (for team-facing lists). The customer's admin chooses the strategy during scoping. The original list creation date and list-owner attribution do not carry over in either reconstruction path.
Do we lose historical activity data on custom object records?
Yes, this is a known data loss risk. Attio's automatic email and calendar sync only covers People and Company records. Custom object records (Subscriptions, Projects, Partnerships, Investors) cannot receive activity history imports because Attio does not support email or calendar sync for custom objects. We flag this gap during scoping and recommend documenting the affected records manually before cutover. Notes attached to custom objects do migrate; automatic engagement history does not.
Can we migrate to Salesforce Professional if we have 12 custom objects in Attio?
Yes. Salesforce Professional ($80/user) supports unlimited custom objects without setup fees, whereas Attio Pro is capped at 12 custom objects and Attio Enterprise is required for unlimited custom objects. If your source workspace has 12 or fewer custom objects and you are moving to Salesforce Professional, the destination plan fully supports the migration. If your source workspace has more than 12 custom objects, we recommend Salesforce Enterprise or Unlimited. We validate the source object count against the destination plan during scoping and flag any plan upgrade recommendation before migration begins.
What about migrating Attio data to Salesforce if we also use HubSpot Marketing?
This is a common hybrid stack pattern. If you are moving sales from Attio to Salesforce while keeping HubSpot Marketing Hub for inbound and email marketing, we configure the HubSpot-to-Salesforce native bidirectional sync during migration so that new HubSpot Leads flow into Salesforce Leads and Salesforce Contacts and Opportunities sync back to HubSpot for attribution. You continue paying for HubSpot Marketing Contacts at the marketing layer while moving sales seat licensing to Salesforce. We do not migrate Attio to HubSpot simultaneously; that is a separate migration scope.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Sugarcrm to SalesforceMapping · history · rollbackBitrix24 to SalesforceMapping · history · rollbackClose to SalesforceMapping · history · rollbackPipedrive to SalesforceMapping · history · rollbackGoldMine to SalesforceMapping · history · rollbackAct! to SalesforceMapping · history · rollback Attio to HubSpotMapping · history · rollbackAttio to Odoo CRMMapping · history · rollbackAttio to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Attio to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote