Migrate from e-shot to HubSpot

HubSpot's primary CRM object. All e-shot contact properties migrate as HubSpot contact properties. First name, last name, email, phone, job title, and address fields map directly. Custom e-shot properties become HubSpot custom contact properties after your admin creates the schema in HubSpot.

e-shot stores company as a text property per contact. We extract unique company names, create HubSpot Company records, and link each contact to their primary Company via the HubSpot association. Secondary company associations (N:1 in e-shot) surface as additional Company associations in HubSpot.

e-shot campaign data per contact migrates to HubSpot Campaigns with campaign membership records. Each e-shot campaign becomes a HubSpot Campaign object; contact participation maps as Campaign Members with activity type and date preserved. Campaign names and IDs stored in HubSpot for reconciliation.

e-shot engagement events (opens, clicks, unsubscribes, bounces) are too granular for HubSpot's native activity model. We summarize engagement history as custom properties on the Contact (e.g., last_email_open_date, total_email_opens, last_click_date) and attach a structured engagement log as a CSV file uploaded to the contact's file attachments for audit reference.

Every e-shot custom contact property requires a corresponding HubSpot custom property. Your admin creates the HubSpot property first (Settings > Properties > Contact properties) with the correct type (string, number, date, enumeration). We surface the full property list in the migration plan so nothing is missed before data lands.

e-shot contact tags or segment membership migrate to HubSpot as either static lists (one per tag) or as a multi-select custom contact property (tags_as_string__c). Multi-select is preferred for compatibility with HubSpot's list and workflow engine. Your admin chooses the strategy before migration runs.

e-shot user records map to HubSpot users by email address match. Unmatched users are flagged before migration — your team either creates HubSpot user accounts first or assigns records to a fallback HubSpot owner. No record lands without a valid HubSpot owner assignment.

e-shot form submission data per contact migrates as HubSpot contact properties (submission date, form name, utm source) and a Note attached to the contact record. Form field values that differ from standard contact properties become custom contact properties created in HubSpot before migration.

e-shot automated series and workflow definitions do not have a HubSpot equivalent at the data layer. They must be rebuilt in HubSpot's workflow engine post-migration. We export your e-shot series definitions as a structured JSON reference document for your HubSpot admin to use during the rebuild phase.

e-shot landing pages are HTML assets that cannot be imported into HubSpot's landing page module. The content, form fields, and lead-gen URL structure are documented in the migration plan. Your team rebuilds landing pages in HubSpot's design manager using the content as a reference.

Files attached to e-shot contact records download and re-upload to HubSpot's file manager, linked to the contact record via the Files tool. File size limits follow HubSpot's file upload constraints (up to 256MB per file in most plans). Inline images in email templates are re-hosted and URL-updated.

e-shot SMS campaign membership migrates to HubSpot as custom contact properties tracking SMS opt-in status, last SMS send date, and campaign name. Full SMS campaign history and message content requires HubSpot's paid SMS add-on, which your team configures post-migration. These properties enable basic SMS attribution in HubSpot reports and list segmentation. Full message content remains in e-shot until your team configures HubSpot's SMS add-on.