Migrate from Function 365 to HubSpot

Dynamics 365 Accounts map directly to HubSpot Companies. Account.Name becomes Company name, Account.Address fields map to HubSpot's address property group. Parent Account hierarchy in Dynamics 365 preserves as HubSpot parent company association. Multi-address accounts collapse to HubSpot's primary address with additional addresses stored as custom properties.

Dynamics 365 Contacts migrate 1:1 to HubSpot Contacts. Full name splits into firstname and lastname properties; email, phone, mobilephone, and jobtitle map directly. Primary contact's account link resolves to the mapped HubSpot Company via email-domain matching or explicit AccountId lookup.

Dynamics 365 Opportunities map to HubSpot Deals. Opportunity.Name becomes Deal name, Amount and CloseDate map directly. Opportunity.StageName (Dynamics pick-list) maps to HubSpot dealstage via value mapping per pipeline. Probability, forecast category, and stepphase are preserved as custom properties since HubSpot calculates deal probability from pipeline stage weights.

Dynamics 365 Leads that have not been qualified into Opportunities split based on lead status: 'Qualified' leads route to HubSpot Contacts (or Deals) depending on your deal-creation rule; 'Disqualified' leads are preserved as HubSpot Contacts with a lead_status property set to Disqualified and a lead_disqualified_at timestamp.

Dynamics 365 Products migrate to HubSpot Products, where Product.Name, Product.Number (SKU), Product.Price, and Product.Unit map directly to HubSpot’s name, sku, price, and unit fields. Because HubSpot’s native product model emphasizes pricing and inventory, detailed product descriptions, images, and custom attributes are stored as custom text, file, or numeric properties. Currency values are transferred as numeric amounts, preserving the original currency code in a separate custom property.

Dynamics 365 Opportunity Product records map to HubSpot Line Items linked to the migrated Deal. Each line item carries quantity, unit price, and amount from the source, preserving the relationship to the deal and the product. HubSpot's Line Item object stores its own quantity and price independently of the parent deal amount.

Dynamics 365 activity records (PhoneCall, Email, Task, Appointment) migrate as HubSpot Engagements of the matching type. Original timestamps, owners, and Regarding links to Contact, Account, or Opportunity are preserved. The activity subject or description maps to HubSpot engagement body text.

Dynamics 365 Notes (including annotations on other entities) migrate as HubSpot Notes. If the note contains a file attachment, the file is downloaded and re-uploaded to HubSpot's file storage, with the note body updated to include the file link. Rich-text formatting in Dynamics notes is simplified to plain text in HubSpot.

Dynamics 365 custom entities map to HubSpot custom objects. The custom entity name and all custom fields are created as HubSpot custom object properties. N:N relationships between custom entities in Dynamics 365 require HubSpot custom junction objects or association properties — this is surfaced in the pre-migration mapping plan.

Dynamics 365 Connections (N:N semantic links between any two entities) map to HubSpot associations. Where Connections use a named role (e.g., 'refers_to', 'manages'), that role becomes a custom association label in HubSpot. HubSpot's association model is simpler — if a Connection links two records that both have HubSpot equivalents, the association is created; otherwise the relationship is stored as a custom property holding the related record's ID.

Dynamics 365 Users are matched to HubSpot Users by email address before migration. OwnerId on any record (Contact, Account, Opportunity) resolves to the matched HubSpot user. Unmatched owners — users in Dynamics 365 who do not have HubSpot accounts — are flagged in a pre-flight report; their records are assigned to a fallback owner or held pending invitation to HubSpot.

Dynamics 365 Marketing Lists (static member lists) can be migrated as HubSpot static contact lists. Dynamic marketing lists with fetch-xml-based membership rules have no HubSpot equivalent — the list schema can be documented as a rebuild reference for HubSpot lists, but the dynamic rules must be recreated manually in HubSpot's list builder.