Migrate from Apollo ERP to Freshsales

Apollo contacts migrate as Freshsales Contacts. Email, phone, name, and address fields map directly without transformation. Apollo's enrichment metadata — including LinkedIn URL, job seniority level, and company headcount scraped from public sources — migrates as custom fields on the Contact record, preserving all prospecting context in the destination CRM.

Apollo contacts that have not been worked (no task, no email, no meeting recorded in Apollo) route to Freshsales Lead. Contacts with engagement history route to Freshsales Contact. This split prevents duplicate records in Freshsales and aligns with Freshsales's Lead-to-Contact conversion model.

Apollo accounts map to Freshsales Accounts with direct field mapping for standard attributes. Apollo's domain field maps to Freshsales Website. Company phone and address fields map to Freshsales billing address fields. Parent-child company hierarchies in Apollo translate to Freshsales Account hierarchy via the parent_account_id field, preserving organizational structure in the destination.

Apollo opportunities map to Freshsales Deals with direct field mapping for standard attributes. Apollo stage names map value-by-value to Freshsales deal stage names per pipeline configuration. Deal amount, close date, owner, and probability map directly. Apollo's opportunity_type field becomes a custom field on the Freshsales Deal record for deal type classification.

Apollo custom fields on contacts — including enrichment signals, intent data, and demographic scrapes — migrate to Freshsales custom fields on Contact. Freshsales Growth plan limits custom field count per object. We flag any account exceeding that threshold before migration and propose consolidation or upgrade to Pro+ for additional field capacity.

Apollo custom fields on accounts including industry tags, employee ranges, and funding stage from enrichment data migrate as Freshsales Account custom fields. Field types are preserved: string, number, date, and boolean map directly to Freshsales equivalents. Pick-list fields require Freshsales option list creation before migration, which we handle as part of pre-migration schema setup.

Apollo opportunity custom fields migrate to Freshsales Deal custom fields preserving all enrichment attributes. Apollo's probability override field, deal source, and competitor tracking fields become Freshsales custom fields on Deal. Stage-entered timestamps from Apollo are stored as custom datetime fields on the Deal for reporting continuity and historical analysis.

Apollo email engagement data including sent, opened, and clicked events migrates to Freshsales Sales Activities with activity type = Email. Original timestamps, subject line, and activity owner are preserved during migration. Freshsales attaches these sales activities to the Contact or Lead record by email address matching for complete engagement history.

Apollo call logs migrate to Freshsales Sales Activities with activity type = Call. Call duration, outcome result, and owner information are all preserved during migration. Freshsales attaches each call activity to the appropriate Contact or Lead record based on contact matching, maintaining complete communication history in the destination CRM.

Apollo meeting records migrate to Freshsales Sales Activities with activity type = Meeting. Start time, end time, meeting title, and attendee list are all preserved during migration. Freshsales links each meeting to the associated Contact or Deal record automatically, ensuring meeting context is available to reps in their daily workflow.

Apollo opportunity owner_id resolves by email match against Freshsales users in the destination instance. Unmatched owners are flagged before migration begins for resolution. You either invite them to Freshsales first or assign their records to a fallback owner. No record lands in Freshsales without a valid owner assignment for accountability.

Apollo sequences and workflow rules do not migrate. They must be rebuilt in Freshsales using Freshsales Workflows (available on Growth+) or Freshsales Sales Sequences (Pro+). We export your Apollo sequence definitions as a rebuild reference document for your Freshsales admin.

Apollo tags on contacts, accounts, and opportunities migrate as Freshsales tags attached to the corresponding object records. Tag values are preserved exactly as they appear in Apollo — no transformation or renaming occurs during migration. Freshsales applies tags at the object level, matching Apollo's tagging behavior for consistent segmentation across both platforms.