Migrate from eTrigue to HubSpot

eTrigue Prospects map directly to HubSpot Contacts. All standard contact properties (name, email, phone, title, address) migrate as HubSpot contact properties. eTrigue prospects without a company association land in HubSpot as contacts with no CompanyId — your team assigns them in HubSpot after migration or during a post-migration cleanup pass.

eTrigue Prospects can be split into HubSpot Leads and Contacts based on lifecycle indicators. If eTrigue tracks a 'stage' or 'status' field that indicates early engagement (e.g., 'Prospect', 'Marketing Qualified'), those records land as HubSpot Leads. Records with closed-won or customer indicators route to HubSpot Contacts. The split rule is configurable based on your eTrigue property values before migration runs.

eTrigue stores company name, domain, industry, and employee count as properties on the Prospect record. We extract these into HubSpot's Company object, deduplicating by company name or domain. The resulting Company record links to the Contact via the HubSpot company_id property. If the same company appears across multiple Prospects, we create one Company record and associate all related Contacts.

eTrigue Campaigns map to HubSpot marketing Campaigns as reference records. Campaign names, descriptions, start dates, and status migrate. Campaign membership — which Prospects were in each campaign — becomes a custom contact property (e.g., 'eTrigue_Campaign_Name') or a HubSpot static list membership, preserving the marketing attribution trail.

eTrigue's Campaign Score is a numeric value per Prospect reflecting engagement with campaign content. HubSpot has no native Campaign Score equivalent — we create a custom number property (e.g., 'eTrigue_Campaign_Score__c' or using HubSpot's property naming) on the Contact record and migrate the static score value. HubSpot's own lead scoring must be configured separately if needed.

eTrigue's Activity Score reflects prospect engagement across emails, page visits, and form submissions. This migrates as a static custom number property on the HubSpot contact — the underlying scoring logic is not replicated. HubSpot's engagement scoring (if enabled in your tier) replaces this behavior going forward.

eTrigue's email engagement records — sent, opened, clicked — migrate as HubSpot engagement timeline entries on the contact record. Each engagement event creates a logged email activity with the original timestamp, campaign name, and subject line preserved. The HubSpot timeline shows this as historical engagement data alongside any HubSpot-native email activities.

eTrigue's page view tracking per Prospect migrates as HubSpot timeline events. Each page view records the URL, page title, and timestamp as a contact timeline entry. The data preserves the prospect's behavioral history for sales follow-up context even though HubSpot's own tracking pixel will generate fresh page view events going forward.

eTrigue form submission records — including form name, submitted fields, and timestamp — migrate as HubSpot contact timeline events of type 'form submission.' The submission data is preserved for reference even though the actual form routing logic (eTrigue's form-to-campaign mapping) must be rebuilt in HubSpot Forms and Workflows.

eTrigue's Boolean, text, number, and date custom fields on Prospects map to HubSpot custom contact properties with equivalent field types. Boolean fields become HubSpot checkboxes. Date fields migrate using HubSpot's date property format. The property name in HubSpot uses camelCase (e.g., 'preferredContactMethod') matching HubSpot's naming conventions. We create the property in HubSpot before the migration run if it doesn't already exist.

eTrigue campaign workflows — including time-based email nurture sequences, behavioral triggers, and enrollment rules — have no direct equivalent in HubSpot that preserves the existing logic. We export eTrigue workflow definitions as a reference document for your HubSpot admin to rebuild in HubSpot's Workflows tool (for CRM-level automation) or Sales Hub Sequences (for outbound sales sequences). This is disclosed honestly and included in the migration scope as a rebuild reference, not as data that migrates.

eTrigue's campaign landing pages export as static HTML reference files. HubSpot's CMS Pages are a separate product with a different editor and hosting model — eTrigue landing pages cannot be imported directly. We deliver the exported HTML so your team can port content, but the pages must be rebuilt in HubSpot CMS or imported into your preferred landing page tool.

eTrigue dynamic lists based on behavioral rules (e.g., 'opened any campaign in last 30 days') have no direct HubSpot equivalent that preserves the dynamic logic. We migrate the static snapshot of list membership (the contacts that matched at export time) to HubSpot static lists. The dynamic rule itself must be rebuilt using HubSpot Workflows or list filters.