Migrate from Constructor to HubSpot

Constructor contacts map directly to HubSpot contacts. Email address is the primary deduplication key. Constructor contact properties map to HubSpot built-in properties where name matches; custom properties create HubSpot custom properties. Owner resolution happens by email match against HubSpot users.

Constructor companies map to HubSpot companies. Domain field maps to HubSpot's domain field for company creation. Parent-child company hierarchies in Constructor translate to HubSpot's parent company association. Multi-company contacts resolve to a single primary company in HubSpot plus secondary associations.

Constructor deals map to HubSpot deals. Each Constructor pipeline maps to a HubSpot deal pipeline. Constructor deal stages map to HubSpot deal stages per pipeline. Deal amount, close date, owner, and associated contacts and companies transfer with original timestamps preserved in custom datetime fields.

Each Constructor pipeline becomes a separate HubSpot deal pipeline. We create HubSpot pipelines matching Constructor pipeline names and configure stage order to match the source. Stage probability values from Constructor migrate as custom fields since HubSpot auto-calculates probability from stage configuration.

Constructor stage names map value-by-value to HubSpot deal stages. Each stage receives the corresponding Constructor stage label. If Constructor uses custom stage names (e.g., 'Proposal Sent', 'Negotiation'), those exact values are created as HubSpot stage names. Stage order and probability metadata re-applied to match Constructor's configuration.

Constructor call logs migrate as HubSpot calls with original timestamp, duration, outcome, owner, and associated contact and company records preserved. Call direction (inbound or outbound) maps to HubSpot's call direction property. Call notes from Constructor transfer as call body text within the engagement record.

Constructor email logs migrate as HubSpot email engagements. The email subject line, body content, timestamp, sent or received status, and all associated records transfer completely. Email attachments stored in Constructor re-upload to HubSpot file storage and link back to the engagement record upon completion.

Constructor meetings map to HubSpot meetings with start and end times, subject, location details, and attendee lists included. Constructor notes map to HubSpot notes with body text content, assigned owner, and original timestamp preserved. Note associations to contacts, companies, and deals all transfer as HubSpot note associations.

Constructor custom objects (Enterprise tier) map 1:1 to HubSpot custom objects. Custom object properties migrate as HubSpot custom properties with matching field types. N:N relationships between custom objects in Constructor translate to HubSpot association definitions. We create the HubSpot custom object schema before migration.

Constructor tags on contacts, companies, and deals migrate as HubSpot labels. Tag values create label entries in HubSpot. For high-cardinality tag sets (100+ unique tags), we recommend filtering to the most-used tags and rebuilding the full set in HubSpot post-migration.

Constructor users resolve to HubSpot owners by email match. Active users in Constructor become active owners in HubSpot. Inactive Constructor users can migrate as inactive HubSpot owners or reassign to a default owner — your team decides the rule before migration.

Constructor workflows, automation rules, and sequence logic do not migrate. We export workflow definitions as a structured JSON reference so your HubSpot admin can rebuild rules in HubSpot's workflow builder. The export includes trigger conditions, action sequences, and filter logic.