Migrate from eSalesTrack to HubSpot

eSalesTrack contacts map directly to HubSpot contacts. HubSpot's unified contact model means no lead/contact split — the lifecycle_stage property carries forward any status classification from eSalesTrack. Contacts without a primary company association land in HubSpot with no associatedcompanyid value. This ensures continuity of lead tracking in the new system.

eSalesTrack companies map to HubSpot companies. Company hierarchies (parent/child) in eSalesTrack preserve via HubSpot's parent company property. Multi-company associations that eSalesTrack supports via N:N relationships collapse to one primary company in HubSpot with additional associations surfaced via company contact relationships.

eSalesTrack deals map to HubSpot deals. Each eSalesTrack deal stage maps to a corresponding HubSpot pipeline stage via value mapping. Deal amount, close date, and owner transfer directly. Deals without a contact association require manual linking post-migration or a default association rule applied during migration.

eSalesTrack leads merge into HubSpot contacts since HubSpot has no separate Lead object. Lead status or lead score from eSalesTrack migrates as a HubSpot contact property. Original lead creation date and lead source are preserved as custom properties for attribution continuity.

eSalesTrack call logs migrate to HubSpot as call activities on the contact timeline. Original call date, duration, outcome, and owner transfer. HubSpot stores call metadata in engagement properties; the full call record attaches to the associated contact. All call outcomes are preserved for future reporting and follow-up tracking.

eSalesTrack email logs migrate to HubSpot as email activities on the contact timeline. Subject, body content, and timestamp transfer. Email associations to multiple contacts create separate activity records per contact in HubSpot. This separation ensures each contact’s timeline reflects its own email interactions without duplication.

eSalesTrack meeting records migrate to HubSpot meetings with original start/end times, title, and attendees. Meeting body and notes transfer to HubSpot's meeting record. HubSpot meeting associations require contact matching by email address. If a contact’s email cannot be matched, the meeting may attach to the related company record for visibility.

eSalesTrack notes migrate to HubSpot notes attached to the corresponding contact or company record. Rich-text formatting in eSalesTrack notes converts to HubSpot's note body format. Notes without an associated contact land on the related company record. All notes retain their original timestamps for audit purposes.

eSalesTrack custom fields defined on contacts create HubSpot custom contact properties. Field type conversion applies: eSalesTrack pick-list fields become HubSpot dropdown properties, numeric fields become number properties, date fields become date properties. Each custom property requires HubSpot-side creation before migration.

eSalesTrack custom fields on deals translate to HubSpot deal custom properties. Pick-list values in eSalesTrack map to HubSpot deal property options. The pipeline association for the deal determines which HubSpot pipeline the custom property appears in. Each property’s type must be defined in HubSpot before migration to ensure accurate data mapping.

eSalesTrack file attachments re-upload to HubSpot Files and attach to the corresponding contact, company, or deal record. File size limits apply (HubSpot handles up to 250MB per file). Inline images in notes download and rehost in HubSpot's file storage. All files retain their original naming conventions for straightforward identification.

eSalesTrack user IDs resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — teams either invite the user to HubSpot first or assign their records to a fallback HubSpot user. No record lands without an assigned HubSpot owner.