Migrate from Microsoft Dynamics 365 Sales to Freshsales

Dynamics 365 Accounts map directly to Freshsales Accounts. We extract the account name, website, industry, address fields, and primary contact lookup. The Dataverse accountid becomes the external_id for reconciliation. Freshsales Accounts do not support a separate Company type distinction, so the account name and type (customer, prospect, partner) migrate as a single record with the type stored in the Type picklist field.

Dynamics Contacts map to Freshsales Contacts with the parent Account resolved via accountid-to-Freshsales Account lookup. Email address is the dedupe key. We preserve the full name split (firstname, lastname), phone numbers, job title, lifecycle stage if present, and owner. Contacts without an email are flagged during scoping and mapped to a placeholder or held for admin review before import.

Dynamics Leads map to Freshsales Leads. The leadscore, leadsource, and qualification status fields migrate to Freshsales's lead_score, lead_source, and status fields. We preserve the original created_on timestamp for historical attribution. If the destination Freshsales account uses automatic lead conversion, we configure lead-to-contact conversion mapping before migration so converted Leads land in the correct Freshsales Contact and Account.

Dynamics Opportunities map to Freshsales Deals. The opportunityname becomes deal_name, estimatedvalue maps to deal_value, closedate maps to close_date, and pipeline_stage maps to Freshsales deal stage via a stage-mapping table built during scoping. We preserve the parent Account lookup, probability percentage, and loss or win reason custom fields. Closed-won and closed-lost Deals migrate with their status preserved so historical pipeline reporting is intact.

Dynamics Quotes, Orders, and Invoices are a three-tier commercial document chain that Freshsales does not model natively as separate objects. We flatten these into the parent Freshsales Deal as line-item-style Notes with a structured format (product name, quantity, unit price, total) and attach a PDF summary if available. The customer chooses during scoping whether to preserve the full document hierarchy or consolidate to deal-level summaries for simplicity.

Dynamics Products migrate to Freshsales Products with the product name, SKU (hs_sku equivalent), and unit price preserved. Product bundles in Dynamics are decomposed to individual line items during migration. Freshsales Products are available to all Deals after import and can be reattached during deal management.

Dynamics Price Lists define quantity-based pricing tiers per product. We extract the price-list structure and create Freshsales Product pricing entries at the equivalent tier level. If the destination uses a single standard price per product, we collapse multi-tier price lists to a median or most-common tier during scoping. The customer reviews and approves the collapsing strategy before migration runs.

Dynamics Activity entities (Task, Email, PhoneCall, Appointment) map to Freshsales Task and Event records. We preserve the activity type, subject, description, date, and owner. Phone calls migrate as Tasks with a call_disposition custom field. Emails migrate as Tasks with a notes_body field containing the email body. Meetings and appointments migrate as Events with start_time, end_time, and location preserved. Regarding (polymorphic) lookup resolves to the target Freshsales Contact, Account, or Deal ID at migration time.

Dynamics Annotations (text notes) migrate to Freshsales Notes attached to the parent Contact, Account, Lead, or Deal. We extract the notetext body, created_on timestamp, and owner. File attachments stored as Dataverse annotations migrate as Freshsales attachments linked to the same parent record.

Dynamics Users referenced as record owners on Accounts, Contacts, Opportunities, and Activities map to Freshsales Users by email address. We run a pre-migration owner audit: any Dynamics User without a matching Freshsales User email is flagged and mapped to a designated migration admin account or an inactive owner placeholder so no record is orphaned. Active users are provisioned in Freshsales before migration begins; inactive users are held in a reconciliation queue for the customer's admin.