Migrate from Attio to Salesforce Sales Cloud

Attio People with no associated Deal or Company relationship, or with lifecycle_status set to unqualified, map to Salesforce Lead. 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.

Attio Company records map 1:1 to Salesforce Account. 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.

Attio Deal records map 1:1 to Salesforce Opportunity. 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.

Attio relationship attributes encode foreign-key links (e.g., a Deal linked to a Company). 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.

Attio Deals linked to multiple People records use relationship attributes to define a many-to-many chain. 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.

Attio custom objects (Gated: Free 3, Plus 5, Pro 12, Enterprise unlimited) migrate to Salesforce custom objects of matching API name with __c suffix. 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.

Attio relationship attributes between two custom objects map to Salesforce custom Lookup fields on the child object. We resolve the parent custom object record ID via the Attio API before writing the foreign key. Cross-object relationships spanning more than two hops require multi-pass import sequencing to ensure parent records exist before children are inserted.

Attio Notes are first-class API objects with timestamps and author attribution. They migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Rich text formatting is preserved as Salesforce-compatible HTML. Note body and created-at timestamps migrate directly.

Attio Tasks attach to records and have assignee, due date, and status attributes. We map assignee by email to Salesforce User records via the Owner reconciliation step, then write Task with OwnerId, Status, Priority, and ActivityDate preserved. Tasks attached to Attio custom objects migrate as Salesforce Tasks linked via WhatId to the custom object record.

Attio Lists are workflow-context collections of record entries, not standalone records. We extract list memberships during scoping, map each Attio List to a Salesforce Campaign (for behavioral or segmentation lists) or a static List View, and create CampaignMember records linking the constituent Leads or Contacts. The customer's admin chooses the strategy during scoping.

Attio workspace Users can be enabled as objects with owner assignments across records. We resolve Attio owner references by email match against the destination Salesforce org's User table. Any Attio Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId is a required reference on most standard object inserts.

Attio's automatic email and calendar sync covers People and Company records only. Email history migrates to Salesforce EmailMessage records linked to the resolved Contact or Lead; calendar events migrate to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Attende mappings create EventRelation records. Activity records are loaded via Salesforce Bulk API 2.0 with batch chunking and parent-record lookup resolution.

Attio email and calendar sync does not attach to custom object records such as Subscriptions, Projects, or Partnerships. Any activity history scoped to custom object records cannot be imported directly and is not recoverable via API. We flag this as a data-loss risk during scoping and recommend documenting the affected records manually before migration cutover. Notes attached to custom objects do migrate; automatic activity history does not.