Migrate from OPEX 365 CRM to HubSpot

Direct map. D365 Contact maps to HubSpot Contact with all standard fields such as first name, last name, email address, phone number, and physical address preserved. D365 Contact.CompanyId translates to HubSpot Contact.associatedCompanyId, a lookup that links the contact to its parent Company; because this lookup requires the Company record to exist, the migration sequence must load Account (Company) data before Contact records.

D365 Lead routes to HubSpot Contact based on lead status: Leads with status 'Open - Not Contacted', 'Working - Contacted', or 'Qualified' map to HubSpot Contacts with lifecycle_stage = 'lead' or 'marketingqualifiedlead'. Converted D365 Leads (status = 'Converted') map with lifecycle_stage = 'customer'. Lead source, rating, and budget information become custom properties on the HubSpot Contact.

Direct map. D365 Account maps to HubSpot Company with all standard fields such as company name, website URL, industry, number of employees, and annual revenue preserved. D365 parent-account hierarchy (Account.ParentId) translates to HubSpot Company.associatedCompanyId for subsidiary relationships, and D365 N:N Account relationships are converted into HubSpot Company association labels, allowing flexible labeling of multi-company connections.

Direct map. D365 Opportunity becomes HubSpot Deal with the opportunity name used as the deal name, and pipeline/stage names translate to HubSpot Deal pipeline and stage. Core attributes (amount, close date, probability, owner) map directly. The Opportunity.ContactId (primary contact role) populates HubSpot Deal.associatedContactIds, linking the main contact; additional contact roles can be stored as custom properties.

D365 OpportunityProduct records become HubSpot Line Items linked to the Deal via dealId. Quantity, unit price, manual discount, and product description map to HubSpot Line Item properties. If D365 uses a product catalog (ProductId lookup), we resolve to a HubSpot Line Item with product name and price — HubSpot Line Items do not require a pre-existing product database.

D365 Task entity maps to HubSpot Engagement, appearing as a Task on the contact or deal timeline. Original created-on timestamp, due date, and owner (resolved via email lookup) are preserved, and the regarding object link keeps the parent relationship. Task subject, description, and priority map directly to HubSpot task subject, body, and priority fields; the original D365 task ID is stored as a custom property for audit continuity.

D365 email records map to HubSpot Email engagements on the contact timeline, preserving the subject line, HTML body, sent/received timestamp, and both from and to addresses. CC/BCC fields and any inline attachments are retained, and the original D365 email ID is stored as a custom property for reference. HubSpot's native email tracking flags (email_open, email_click) are set according to the read status captured in D365, allowing continuity of engagement data.

D365 PhoneCall records map to HubSpot Call engagements, preserving call duration, direction (inbound or outbound), outcome (answered, missed, voicemail), and the original timestamp. Call notes and disposition are transferred to the HubSpot call body, while the D365 call recording URL is stored as a custom property; HubSpot's native call recording capability is used for any new calls logged after cutover.

D365 Appointment records map to HubSpot Meeting engagements, preserving the start and end times, location, and rich text body, as well as required and optional attendee lists. Attendee email addresses are resolved to existing HubSpot contacts; those without matches are retained as display-name strings. Meeting conference URLs, dial-in details, and any attachments are carried over, and the original D365 appointment ID is saved as a custom property for audit continuity.

D365 Annotation (notes) are mapped to HubSpot Notes on the appropriate contact, company, or deal timeline. The note text, created-on timestamp, and the modifying user are all preserved, and any attachments linked to the annotation are migrated to HubSpot Files. The original D365 annotation ID is stored as a custom property, ensuring traceability back to the source record while the note remains attached to the correct HubSpot entity.

D365 custom entities map 1:1 to HubSpot custom objects (Enterprise tier required). Custom entity attributes become custom properties on the HubSpot custom object. N:N relationships between custom entities in D365 map to HubSpot custom object associations via association labels. Custom entity ownership resolves to HubSpot owners by email match.

D365 Connection records (N:N entity associations) map to HubSpot association labels. Connection role name becomes the association label name. Effective/from-to dates are stored as custom properties on the association if HubSpot supports temporal associations — otherwise the label is created without dates.