Migrate from Market Maker to HubSpot

Direct map. HubSpot uses FirstName, LastName, Email, Phone, and other standard contact properties. We match contacts by email for deduplication before insertion to prevent duplicate records in the destination portal. Email matching ensures that if multiple Market Maker records share the same email address, they consolidate into a single HubSpot contact rather than creating redundant entries during the bulk load process.

Direct map. HubSpot company records use Name, Domain, Industry, Number of Employees, and Annual Revenue. Parent-company relationships migrate via HubSpot's Parent Company field, which requires the parent company record to land first. Load ordering ensures parent companies insert before child companies to satisfy HubSpot's foreign-key requirement and maintain the correct organizational hierarchy in the destination.

HubSpot does not have a separate Lead object at the CRM tier — all persons land as Contacts with a lifecycle_stage property. We route all Market Maker lead records to the Contact object and set lifecycle_stage based on the source lead status or stage value.

Direct map. Market Maker deals map to HubSpot deal records with Deal Name, Amount, Close Date, and Pipeline. Stage names are mapped value-by-value to the target pipeline's stage values. Multiple Market Maker deal categories map to separate HubSpot pipelines. We create each target pipeline in HubSpot before the deal records load so the pipeline field resolves correctly during import and avoids null pipeline associations.

Market Maker's pipeline concept maps to HubSpot's multi-pipeline model. Each distinct pipeline in Market Maker becomes a separate HubSpot pipeline. We create the pipeline structure in HubSpot before the deal records load so stage pick-lists resolve correctly. Probability and forecast category per stage are applied from HubSpot defaults unless your team specifies custom values during the discovery phase.

Market Maker call logs migrate as HubSpot engagements with Type='Call'. Original call outcome, duration, and owner are preserved as custom engagement properties. Parent contact and company links are re-established via HubSpot's association model using the source association metadata to ensure the engagement timeline displays correctly on the contact record.

Market Maker email records map to HubSpot email engagements. Subject, body text, and timestamp are preserved. Attachments are downloaded and re-uploaded to HubSpot file storage. Association to the originating contact record is rebuilt using email-address matching to ensure the engagement appears on the correct contact timeline after migration completes.

Market Maker meeting records map to HubSpot meeting engagements. Start time, end time, location, and attendees are preserved. We re-link meeting engagements to the relevant contact and company records in HubSpot using the source association metadata to maintain the relationship between meetings and the associated contact or company.

Market Maker notes migrate as HubSpot engagement notes. Rich-text formatting is preserved where the source API exposes it. Notes are associated to the parent contact or company record using the source object's ID linkage to ensure they appear in the correct engagement timeline after the migration completes.

Market Maker custom objects migrate 1:1 to HubSpot custom objects if the source schema uses HubSpot's object-naming conventions. N:N relationships in Market Maker require HubSpot custom association definitions — we surface these in the pre-migration mapping plan and create the association types in HubSpot before the custom object records load.

File attachments on Market Maker records are downloaded from the source storage, re-uploaded to HubSpot's file manager, and linked back to the relevant contact, company, or deal record. File size limits per HubSpot's file storage apply at the destination and are checked during the pre-migration audit to flag files that may exceed platform constraints.

Market Maker owner records are resolved by email match against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns those records to a designated fallback owner in HubSpot. Owner resolution ensures that engagement history and deal records retain the correct owner attribution after migration.