Migrate from Apollo ERP to Salesforce Sales Cloud

Apollo's contacts table has no separate lead concept. FlitStack splits by Apollo's person_status: 'customer' and 'opportunity' land as Salesforce Contacts; 'subscriber' and 'lead' route to Salesforce Leads. Any contacts with no person_status default to Salesforce Leads. The split happens during extraction so downstream field mappings route to the correct Salesforce object.

Apollo contacts identified as existing customers map directly to Salesforce Contact. Salesforce requires AccountId — the contact's primary Apollo company must have already been migrated as a Salesforce Account. FlitStack resolves AccountId via Apollo's organization_id before inserting the Contact record.

Apollo's organizations table maps to Salesforce Account. Domain field in Apollo (used for company identity) maps to Account Website. Parent-child hierarchies in Apollo (parent_organization_id) map to Account ParentId. Multi-company contacts (Apollo allows a contact to link multiple organizations) collapse to one primary AccountId plus AccountContactRelation records for secondary affiliations.

Apollo deals map to Salesforce Opportunity. The deal's pipeline name becomes a Salesforce Sales Process name scoped by RecordTypeId. A single Apollo pipeline equals one Salesforce record type. Deal stage names map to Opportunity StageName pick-list values under that record type. Close date, amount, owner, and custom deal fields carry over directly.

Apollo sequences have no Salesforce equivalent that can be imported. FlitStack exports sequence step definitions (step number, delay days, action type: email/call/LinkedIn) as a JSON blob stored on a custom Opportunity field called Sequence_Definition__c. Your Salesforce admin uses this as a reference spec to rebuild the cadence in Sales Engagement or Flow.

Apollo workflow rules and if-this-then-that automations do not export in any standard format. FlitStack captures each workflow's trigger object, condition fields, and action as a structured JSON export stored on a custom Opportunity field called Workflow_Rebuild_Reference__c. Your Salesforce admin rebuilds in Flow using this spec.

Every Apollo custom field on Contact, Organization, or Opportunity requires a pre-created Salesforce custom field before migration. The __c suffix is mandatory. FlitStack generates a Salesforce Setup Plan listing every custom field name, data type, and pick-list value that your admin must create before the migration batch runs. Fields that can't map to a Salesforce standard field (e.g., Apollo's engagement_score) land as Number or Text __c fields.

Apollo logged emails attach to contacts or deals. They migrate as Salesforce Tasks with Task.Type = 'Email', Task.Subject containing the email subject, Task.Description containing the body, and Task.WhoId pointing to the Contact or Lead. Original timestamps and owner IDs are preserved. Email attachments (files) migrate to Salesforce Files and relink to the Task record.

Apollo logged calls migrate as Salesforce Tasks with Task.Type = 'Call'. Apollo logged meetings (meetings have start_time and end_time) migrate as Salesforce Events with Event.StartDateTime and Event.EndDateTime preserved. Both carry the Apollo owner_id resolved to Salesforce OwnerId. Call duration, if stored, maps to Task.DurationInMinutes; meeting location copies to Event.Location.

Apollo notes migrate to Salesforce Notes (ContentNote for rich text). The note body maps to ContentNote.Content, linked to the parent Contact, Lead, or Opportunity via ContentDocumentLink. Original create date stored in Original_Create_Date__c for continuity. If Apollo stores a title, it maps to ContentNote.Title; any HTML formatting is preserved as-is. Attachments on Apollo notes are exported to Salesforce Files and linked through ContentDocumentLink.

Apollo's tagging system (applied to contacts and organizations) has no Salesforce equivalent. Tags migrate as a pipe-delimited custom text field (Apollo_Tags__c) on the Contact or Account. If your team uses tags for segmentation, FlitStack can alternatively write a custom report formula field to parse and filter tags in Salesforce reporting.

Apollo's activity timeline (stage changes, owner changes, note additions) preserves a timestamped audit log. FlitStack maps this as a custom text field (Stage_Change_Log__c) on the Opportunity, storing a JSON array of {timestamp, field, old_value, new_value}. Salesforce admins can parse this for reporting or display it in a Flow-powered component.