Migrate from ActiveDEMAND to HubSpot

ActiveDEMAND contacts map directly to HubSpot contacts. HubSpot deduplicates by email address on import — if two ActiveDEMAND contacts share an email, they merge into one HubSpot contact. Original ActiveDEMAND record IDs are preserved in a custom Source_System_ID__c property for traceability and delta-run deduplication.

ActiveDEMAND company records map 1:1 to HubSpot company records. Company name, domain, industry, phone, address, employee count, and annual revenue transfer as HubSpot native fields. Parent-company hierarchies in ActiveDEMAND map to HubSpot's parent company field using HubSpot's parent_company_id reference. Custom properties on the company record migrate as HubSpot custom company properties, preserving pick-list values. Duplicate companies are resolved using name and domain matching before import.

ActiveDEMAND deals map to HubSpot deals with stage, pipeline, and owner mapping. ActiveDEMAND deal stages are custom pick-list values scoped to each pipeline — we map them to HubSpot deal stages under the appropriate HubSpot deal pipeline, creating new stage values if ActiveDEMAND stages have no HubSpot equivalent. Deal properties like source campaign and buyer journey data migrate as custom deal properties in HubSpot.

ActiveDEMAND lifecycle stages (e.g., 'active', 'member', 'lead') do not map directly to HubSpot's native lifecycle_stage pick-list values. We create a HubSpot custom contact property Lifecycle_Stage__c using ActiveDEMAND's exact value set so historical segmentation is preserved. A separate custom datetime property records when the stage was last updated in ActiveDEMAND.

ActiveDEMAND's numeric engagement and contact scores map to a HubSpot custom number property. HubSpot has its own HubSpot Score property, but it is recalculated by HubSpot's scoring model post-migration — the ActiveDEMAND score is preserved as AD_Score__c so the historical baseline is available for comparison during the transition period.

ActiveDEMAND's Collective Buyers' Journey Attribution data — touchpoint timelines, channel attribution, and conversion path data — migrates as a set of HubSpot custom properties on the contact record. The attribution model itself (first-touch, last-touch, linear) is noted in the migration plan for rebuild in HubSpot's attribution reporting.

ActiveDEMAND call records include tracking number, call duration, disposition, recording URL, and call source. These map to HubSpot call-logged engagements with ActiveDEMAND tracking numbers and disposition data preserved in custom properties. Call recording URLs are preserved as a custom URL property on the contact record; HubSpot's native call tracking is a separate feature that requires post-migration configuration.

ActiveDEMAND email send and open records migrate as HubSpot email engagements on the contact timeline. Original send timestamp, open timestamp, and click events are preserved as engagement metadata. Subject line and campaign name are preserved in the engagement record so historical email performance is visible in HubSpot.

ActiveDEMAND meeting records — including subject, start/end time, location, and meeting type — migrate as HubSpot meeting engagements on the contact record. Owner of the meeting in ActiveDEMAND resolves to the corresponding HubSpot user by email match and is set as the meeting owner in HubSpot.

ActiveDEMAND allows a contact to be associated with multiple companies simultaneously. HubSpot supports one primary CompanyId per contact plus secondary associations via the Associations v4 API. We set the most recently modified or your designated primary company as the HubSpot primary company; all additional ActiveDEMAND company associations are created as secondary HubSpot company associations. If a contact had no company in ActiveDEMAND, it lands as an unassociated HubSpot contact.

ActiveDEMAND Enterprise custom fields — including brand fields, campaign tracking fields, and industry-specific custom fields — map to HubSpot custom properties of the matching type. Pick-list custom fields in ActiveDEMAND require value-by-value mapping to HubSpot pick-list options; if HubSpot does not have a matching option, we create a new HubSpot pick-list value during migration.

ActiveDEMAND file attachments on contacts, companies, and deals are downloaded and re-uploaded to HubSpot Files. File name, description, and original upload date are preserved. HubSpot's 50MB per-file limit applies; attachments exceeding this are flagged and handled per your instruction — either split or excluded from the migration with a manifest.