Migrate from DinamikCRM to HubSpot

DinamikCRM's Customer entity holds both person and organization data in a single record. We split it during migration: name and contact details (email, phone, address) route to HubSpot Contact; company name and domain route to HubSpot Company, then the two are linked via the primary company association. Any remaining fields on the original Customer record that have no HubSpot equivalent are written to a DinamikCRM_Source_Record__c text field for reference.

DinamikCRM Lead records map directly to HubSpot Contacts with lifecycle_stage preset to 'lead'. The lead's status field from DinamikCRM is preserved as a custom pick-list property (Lead_Status_Source__c) so the history is available for rebuild reference even though HubSpot has no native equivalent status field.

HubSpot Company is the direct equivalent of DinamikCRM Company. Company name maps to Company Name, domain to Website, industry to Industry pick-list, and employee count to Number of employees. Parent-child company hierarchies in DinamikCRM map to HubSpot's Parent Company field. If a DinamikCRM Company has no name, we generate one from the domain field to satisfy HubSpot's non-null requirement.

DinamikCRM Deal records map to HubSpot Deals with deal name, amount, and close date migrating directly. The pipeline from DinamikCRM maps to a HubSpot pipeline; DinamikCRM's pipeline stage names map to HubSpot Deal stage names via value mapping. If DinamikCRM uses multiple pipelines, each pipeline's stage set is consolidated into the single HubSpot pipeline's stage list.

DinamikCRM Activity records carry a type field (call, email, meeting, note) that determines the HubSpot engagement type. Each activity's timestamp and owner email are preserved. Activities without a type are migrated as HubSpot notes with a type='other' flag. The parent DinamikCRM Customer reference is re-linked to the corresponding HubSpot Contact during migration.

DinamikCRM Appointment records map to HubSpot Meeting engagements with start time, end time, title, and owner preserved. Appointment location maps to the HubSpot meeting location field. If the appointment was linked to a DinamikCRM Customer, the association is re-created on the corresponding HubSpot Contact. Recurring appointments are migrated as individual meeting records; recurrence logic is captured as a custom text property for HubSpot workflow rebuild.

HubSpot has no native invoice object in the CRM core. We create a DinamikCRM_Invoice custom object in HubSpot with fields for invoice number, amount, currency, status, and linked Contact/Company. Alternatively, if invoice line items represent the actual deal product catalog, we map them to Deal product line items. Which approach is chosen depends on your reporting priority — we surface this decision in the pre-migration audit.

DinamikCRM Feedback records contain survey or NPS-style responses linked to Customers. HubSpot's survey integration lives in Service Hub and maps responses to contacts. We preserve Feedback records as a DinamikCRM_Feedback custom object with the response text and score, linked to the HubSpot Contact. Marketing-automation logic tied to feedback scores must be rebuilt in HubSpot's workflow builder.

Every DinamikCRM custom field that has no direct HubSpot equivalent becomes a HubSpot custom property. We generate the property definition during the pre-migration schema audit, including data type mapping (text → single-line text, number → number, date → date picker, pick-list → single-option or multi-option). HubSpot's property name restrictions (no reserved words, max 100 chars) are enforced in the definition. Properties are created in HubSpot before the migration run so field mapping can reference them.

DinamikCRM user records (name, email, role) are matched to HubSpot users by email address. Unmatched users — those without a HubSpot account at migration time — are flagged and assigned to a fallback HubSpot user. Role information from DinamikCRM (admin, manager, sales rep) is preserved as a text property (Source_Role__c) for reference. HubSpot's permission model (roles, teams, individual access) is separate from migration and must be configured post-migration.

If your DinamikCRM instance includes the DESK module, ticket records map to HubSpot Tickets with subject, description, status, priority, and owner preserved. Ticket pipeline stages from DinamikCRM map to HubSpot ticket pipeline stages. HubSpot Tickets are available on all paid Service Hub plans. Association to the related Contact/Company is re-linked during migration.

DinamikCRM SALES module proposals and orders have no direct HubSpot equivalent. Proposals migrate as a DinamikCRM_Proposal custom object with proposal content stored as a long-text field or re-uploaded as a HubSpot file attachment linked to the Deal. Order records that track revenue against a Deal map to Deal product line items. Quote and proposal builder functionality requires HubSpot's paid Sales Hub Professional tier.