Migrate from HubSpot to Microsoft Dynamics 365 Sales

HubSpot Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead route to Dynamics 365 Lead. Lifecycle Stage of SQL, customer, evangelist, or other qualified states route to Dynamics 365 Contact attached to an Account. We apply this split as a transform during migration using HubSpot's lifecyclestage property, and write the original Lifecycle Stage into a custom field hs_original_lifecycle on both Lead and Contact for reconciliation.

HubSpot Company records map directly to Dynamics 365 Account. The HubSpot company domain becomes the Account Website field and acts as a dedupe key during import. Account is provisioned before any Contact or Lead import so that the CustomerId (Account) lookup is satisfied at the moment of insert. Dynamics 365 does not have a separate Company entity; all organizational records land in Account.

HubSpot Deals map to Dynamics 365 Opportunity. The HubSpot dealstage property maps to the active Business Process Flow stage on Opportunity. We configure the Business Process Flow (BPF) during migration setup to match the HubSpot pipeline's stage names, step order, and category labels so that deal history reflects the correct progression.

Each HubSpot Deal pipeline becomes a Dynamics 365 Business Process Flow attached to the Opportunity entity. We define the BPF stages, step categories, and step labels during migration setup in the destination Dynamics environment, matching the HubSpot pipeline configuration. Multi-pipeline accounts require multiple BPFs, and we configure which BPF applies to each Opportunity at migration time via the Process field.

HubSpot Products map to Dynamics 365 Product records with Standard Price List entries created during import. ProductCode maps from HubSpot hs_sku. Dynamics Products carry a Product Type (Sales, Services) that we set based on HubSpot product categorization.

HubSpot Line Items attach to Deals and map to Dynamics 365 Opportunity Product records linked to the parent Opportunity. We resolve the Product reference, Quantity, and Unit Price at migration time. Opportunity Product is inserted after the Opportunity and Product records exist in the destination.

HubSpot Owners map to Dynamics 365 User records by email match. Any HubSpot Owner without a matching Dynamics User enters a reconciliation queue; the customer's admin provisions missing Users before record import resumes because Owner (OwningUser) references are required on most standard entities in Dynamics.

HubSpot email engagements migrate to Dynamics 365 Email records linked to the regarding record (Lead, Contact, or Opportunity) via the regardingobjectid GUID. Email body, subject, from, to, and cc fields transfer directly. We resolve the parent record GUID using the email-address-to-contact/lead cross-reference table created during scoping.

HubSpot call engagements map to Dynamics 365 Phone Call activity with Subject, Description, Direction (inbound/outbound), Duration, and Call Purpose preserved in custom fields. The Phone Call is linked to the Contact, Lead, or Opportunity via the Regarding lookup. Call recording URLs transfer as a text field for manual re-association post-migration.

HubSpot meeting engagements map to Dynamics 365 Appointment records. Start Time, End Time, Location, and Subject migrate directly. Attendee records map to Dynamics ActivityParty entries linked to the Appointment, with the Party reference pointing to the corresponding Contact, Lead, or User record.

HubSpot Task engagements migrate to Dynamics 365 Task records with Subject, Description, Priority, Status, and Due Date preserved. Assigned Owner resolves via the User mapping table. Tasks are linked to the parent record via Regarding lookup using the GUID cross-reference.

HubSpot Notes (engagement type NOTE) migrate to Dynamics 365 Annotation records linked via the ObjectId and ObjectTypeCode to the parent record (Lead, Contact, Account, or Opportunity). Note body migrates as plain text or HTML depending on source format. File attachments on notes migrate as Dynamics 365 Note attachments linked via Annotation.

HubSpot Tickets migrate to Dynamics 365 Case if the destination environment includes the Customer Service management app. Ticket pipeline stages map to Case Status values, and ticket priority and owner migrate to the corresponding Case fields. Ticket conversations migrate as Email or Note annotations on the Case.

HubSpot custom objects (Enterprise-only on source) migrate to Dynamics 365 custom entities created in Dataverse before migration begins. We define the custom entity schema, attributes, and lookup relationships to standard entities (Account, Contact, Opportunity) during the migration setup phase, matching the HubSpot custom object API name where possible and applying a __c-equivalent naming convention in Dataverse.