Migrate from Attio to Freshsales

Attio People records map to Freshsales Contact. The email address field becomes the dedupe key during import. All custom attributes on the People object map to Freshsales custom Contact fields. Relationship links to Companies become Account lookups. Owner assignments from Attio resolve to Freshsales Users by email match. We preserve the full People record including any linked interaction timestamps as Contact activity timeline entries.

Attio Companies map to Freshsales Accounts. The company domain becomes the Account Website field and the dedupe key. All custom Company attributes map to Freshsales custom Account fields. Parent-company relationships in Attio map to Freshsales Account hierarchy if configured. Companies must import before People so that AccountId is resolved for Contact inserts.

Attio Deals map to Freshsales Deals. Deal status values map to Freshsales sales cycle stages (Qualification, Proposal, Negotiation, Closed Won, Closed Lost). Relationship links to Companies and People must be resolved before Deal import: the parent AccountId is required, and linked People become Deal contacts via the Deal Contact Roles object. Closed-Lost reason and Closed-Won reason from Attio custom fields migrate to Freshsales deal loss reason and deal notes.

Attio custom objects (Subscriptions, Investors, Partnerships, Projects) do not have a direct Freshsales equivalent because Freshsales does not expose a custom object API. We evaluate each custom object during scoping: objects with a simple field set map to custom fields on the nearest standard object (Contact, Account, or Deal); objects with their own relationship attributes map to a related record pattern (e.g., a Subscription custom object linked to Account becomes a custom Deal or a Note with structured fields). If the destination plan does not support sufficient custom fields (Growth supports 35 custom fields per object), we recommend consolidation or a plan upgrade before migration.

Attio Lists are workflow-context collections of record entries, not standalone records. We extract list memberships for each Contact and Account and write them as Freshsales Tags (flat label assignments) or Contact Group entries. List names become tag names with a list_ prefix to distinguish them from ad-hoc tags. If a List represents a segment with complex membership criteria (e.g., 'all Contacts with Deal value over $50k in the Enterprise segment'), we document the criteria as a Freshsales smart list or contact filter specification for the admin to configure post-migration.

Attio Relationship Attributes define cross-object links (e.g., which People are linked to a Deal, which Companies are linked to a Person). We resolve these as foreign-key lookups in Freshsales: Deal-to-Account as AccountId, Deal-to-Contact via Deal Contact Roles, and Account-to-Contact via the standard AccountId on Contact. Many-to-many links (multiple People linked to one Deal) use the junction object pattern. Without resolving these before import, Deals arrive orphaned from their Accounts and Contacts.

Attio Notes attach to records as threads and are first-class API objects. We migrate Notes with timestamps, author attribution, and record associations preserved. Notes link to the parent Contact, Account, or Deal in Freshsales via the Notes widget on the record. Rich text content preserves formatting where the destination field type allows.

Attio Tasks attach to records with assignee, due date, and status attributes. We migrate Tasks 1:1 with owner assignments preserved as User references in Freshsales. Task status values (open, completed, cancelled) map to Freshsales task status. Due date and priority transfer directly. Tasks linked to specific Deals or Contacts maintain their parent-record associations in Freshsales.