Migrate from mQuest to HubSpot

Direct map. mQuest contact records map 1:1 to HubSpot Contacts. All standard properties (name, email, phone, job title, address) translate directly. Contacts without a primary company association in mQuest land in HubSpot as standalone contacts and can be associated after migration.

Direct map. mQuest company records map to HubSpot Companies with a 1:1 field translation. Company name, domain, industry, employee count, and annual revenue fields map directly to their HubSpot equivalents. Parent-child company hierarchies in mQuest map to HubSpot's parent company association using the same relationship structure.

Direct map. mQuest deal records map to HubSpot Deals with field-level translation. Deal name, amount, close date, and owner translate directly. The deal pipeline and stage in mQuest map to HubSpot's deal pipeline and dealstage property with value-by-value mapping of stage names across each pipeline.

mQuest pipelines map to HubSpot deal pipelines. Each mQuest pipeline becomes a named HubSpot deal pipeline with its own set of stages. If mQuest has multiple pipelines, we create corresponding HubSpot pipelines and map deal-stage values per pipeline during migration.

Stage names mapped value-by-value from mQuest to HubSpot deal stages per pipeline. Stage probability and forecast category are re-applied based on HubSpot's stage configuration. HubSpot requires each pipeline to have its own set of stages — we preserve the full stage history as custom datetime fields for reporting continuity.

mQuest activities map to HubSpot engagements. Calls map to HubSpot logged calls, emails to logged emails, meetings to meetings, and notes to HubSpot notes. Original timestamps, owners, and parent-record links are preserved. HubSpot's timeline view renders all engagement types chronologically per record.

mQuest custom fields require HubSpot custom properties to be created before migration. We audit the full list of mQuest custom fields, determine each field's HubSpot type (text, number, date, dropdown, checkbox), create the properties in HubSpot, and then map values during migration. Properties that cannot map to a compatible HubSpot type are flagged for manual review.

mQuest N:N contact-to-company associations translate to HubSpot's primary company association plus secondary associations via the Company Contact Associations feature. The primary company defaults to the most recently modified association in mQuest, or follows a rule you specify before migration runs.

mQuest engagement scoring fields have no HubSpot native equivalent. We migrate these as custom number properties on the Contact object so the score data is available for segmentation and reporting, though the scoring algorithm must be rebuilt in HubSpot using workflow enrollments or the Breeze AI scoring model.

mQuest file attachments re-upload to HubSpot Files and are associated back to the original record. Files are downloaded from mQuest's storage and re-uploaded to HubSpot's file manager with the same name and association. HubSpot's 115 MB per-file limit applies; files exceeding this are flagged before migration.

mQuest owner IDs resolve to HubSpot users by email address match. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts first or assigns those records to a fallback HubSpot owner. No record lands in HubSpot without a valid owner.

mQuest contact-to-deal association labels (e.g., Decision Maker, Influencer, Champion) have no direct HubSpot equivalent. We export the full association-label structure from mQuest as a reference CSV. Your HubSpot admin rebuilds these using custom dropdown properties on the deal-contact association or custom objects depending on the label complexity.