Migrate from Apollo ERP to HubSpot

Apollo contact maps 1:1 to HubSpot contact. All standard properties (name, email, phone, title, address) migrate as HubSpot native fields. Records without email are flagged and excluded — HubSpot enforces one email per contact, and there is no override or bulk exception for this requirement.

Apollo account maps to HubSpot company. Company name, domain, industry, employee count, annual revenue, and founded year migrate as native HubSpot company properties. Industry values require pick-list alignment — Apollo industry values not in HubSpot's default list are added as custom pick-list values before migration runs.

Apollo opportunity maps to HubSpot deal. Deal name, amount, stage, close date, owner, and pipeline migrate. Deal stage is a HubSpot deal-stage pick-list value scoped to the specific pipeline — each Apollo stage value requires explicit value mapping before migration runs.

Apollo custom contact fields (string, number, date, boolean) migrate to HubSpot custom properties on the contact object. Each custom field is created in HubSpot before migration runs, using the same field type as the Apollo source. Type mismatches are flagged for admin review.

Apollo custom account fields map to HubSpot custom properties on the company object. Field type (string, number, date, boolean) is preserved exactly. Multi-select or pick-list fields require value alignment between Apollo's options and HubSpot's pick-list values before migration.

Apollo custom opportunity fields migrate to HubSpot deal custom properties. Number and date fields migrate cleanly. Pick-list fields require value mapping — stage-probability or forecast-category fields from Apollo need HubSpot equivalents created before migration.

Apollo email logs migrate as HubSpot engagement records with type 'email'. Original send timestamp, sender, recipient, and subject line are preserved. Open rates, click rates, and reply rates tied to Apollo's sending infrastructure do not transfer — those metrics belong to Apollo's email engine.

Apollo call records migrate as HubSpot engagements with type 'call'. Call duration, direction (inbound/outbound), outcome, and original timestamp are preserved. Call recording URLs stored in Apollo custom fields migrate as HubSpot custom properties — the audio files are not rehosted automatically.

Apollo notes migrate as HubSpot engagement notes. Original author, timestamp, and note body are preserved. Notes attached to specific contacts, accounts, or opportunities are linked to the corresponding HubSpot record by unique identifier.

Apollo sequences have no native HubSpot equivalent and cannot be migrated directly. FlitStack exports complete sequence definitions — including step timing, email templates, step conditions, and personalization tokens — as a structured rebuild reference for HubSpot Automation workflows. Each sequence must be manually rebuilt in HubSpot using the exported definitions.

Apollo contacts linked to accounts migrate with the primary account reference preserved. HubSpot associates contacts with companies via the company association on the contact record. Multiple-account contacts from Apollo are linked to the primary account only — secondary associations are documented in a gap report.

Apollo contacts linked to opportunities migrate as deal-contact associations in HubSpot. The association is preserved by matching contact email and opportunity ID. Contacts without email are excluded from migration, and this breaks the association for those records.

Apollo owner records (sales rep, SDR) resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — the team either invites the user to HubSpot first or assigns records to a designated fallback owner. No record lands without a valid HubSpot owner.

Apollo's enrichment data — LinkedIn profile URL, buyer intent signals, technology stack — has no native HubSpot equivalent. These migrate as custom properties on the contact record, preserved for reference but not surfaced in HubSpot's standard UI without custom card setup.

If Apollo stores lead status as a custom field, it maps to HubSpot's lifecyclestage property. Value mapping is required — Apollo's custom status labels must be matched to HubSpot's standard lifecycle stage values or added as a separate custom pick-list.