Skip to content
Get a quote

Dynamics 365 to Freshsales migration

We migrate Accounts, Contacts, Leads, Opportunities, and Activities from Microsoft Dynamics 365 Sales into Freshsales with the Dataverse entity hierarchy flattened to Freshsales objects, owner resolution handled before import, and every custom field pre-created in the destination so no record fails at insert time.

Short answer

FlitStack AI migrates accounts, contacts, leads, deals and deal line items + notes from Dynamics 365 to Freshsales, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source Dynamics 365
DestinationFreshsales
AccountContactLeadDealDeal Line Items + Notes
Mapped field by field · sample run · one-click rollback

What moves from Dynamics 365 to Freshsales?

Moving from Microsoft Dynamics 365 Sales to Freshsales is a platform simplification migration.

Read the full summary

Microsoft Dynamics 365 Sales sits on the Dataverse data layer with a complex entity model, tiered licensing (Professional at $65, Enterprise at $105, Premium by quote), and deep Microsoft 365 integration that creates lock-in beyond the CRM itself. Freshsales by Freshworks targets SMB-to-midmarket teams that want a configured CRM without the overhead of a Microsoft partner ecosystem. We extract records from Dynamics via the Dataverse Web API, resolve the entity relationships (Account-to-Contact, Opportunity-to-Account), handle owner lookups for inactive users, and import into Freshsales in dependency order. Dynamics Power Automate workflows, Dataverse plug-ins, and Dynamics-specific territory hierarchies do not migrate as code; we deliver a written inventory of every active workflow and automation for the customer to rebuild inside Freshsales or as a separate automation engagement. October 2024 pricing increases of $15 per user per month across all Dynamics tiers apply at renewal and are a recurring cost driver that makes the Freshsales switch financially measurable against ongoing Dynamics licensing.

1:1

Account → Account

Dynamics 365 Accounts map directly to Freshsales Accounts.

How it maps

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.

1:1

Contact → Contact

Dynamics Contacts map to Freshsales Contacts with the parent Account resolved via accountid-to-Freshsales Account lookup.

How it maps

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.

1:1

Lead → Lead

Dynamics Leads map to Freshsales Leads.

How it maps

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.

1:1

Opportunity → Deal

Dynamics Opportunities map to Freshsales Deals.

How it maps

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.

1:N split

Quote, Order, Invoice → Deal Line Items + Notes

Dynamics Quotes, Orders, and Invoices are a three-tier commercial document chain that Freshsales does not model natively as separate objects.

How it maps

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.

1:1

Product → Product

Dynamics Products migrate to Freshsales Products with the product name, SKU (hs_sku equivalent), and unit price preserved.

How it maps

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.

What moves10 objects
Dynamics 365Freshsales
  • AccountAccount1:1
  • ContactContact1:1
  • LeadLead1:1
  • OpportunityDeal1:1
  • Quote, Order, InvoiceDeal Line Itemssplit
  • ProductProduct1:1

+ 4 more in the mapping below

How Dynamics 365 and Freshsales differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionDynamics 365Freshsales
License modelPer-user named licenses, Professional $65, Enterprise $105, Premium by quote; $15 increase from Oct 2024Per-user pricing starting at $29/user/mo on Growth, $49 on Pro, $89 on Enterprise; no per-contact metering
Custom table limitProfessional tier caps at 15 custom tables; Enterprise and Premium allow unlimitedAll paid tiers support custom fields and custom objects without a hard table ceiling
Automation modelPower Automate cloud flows, Dataverse plug-ins, and sales sequences configured at platform levelFreshsales Workflows with event-based triggers, task automation, and sequence cadences built natively
Activity storageActivities stored in Dataverse as separate entities (Task, Email, PhoneCall, Appointment) with a polymorphic Regarding lookupActivities stored as Tasks and Events with a typed foreign key to the parent record object
Territory managementTerritory hierarchies available on Enterprise tier onlyTerritories modeled as a picklist field with assignment rules, available at all paid tiers
Implementation modelTypically requires certified Microsoft implementation partners, adding 30-50% to total project costSelf-service setup with guided onboarding; professional services available but not required
Microsoft ecosystemNative integration with Outlook, Teams, SharePoint, and Power BI at the platform levelStandalone CRM with standard REST API and Zapier/Make integrations; no native Microsoft 365 deep-link

What to watch for in a Dynamics 365 to Freshsales migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Custom fields must be pre-created in Freshsales before import

Dynamics 365 allows creating custom fields through Advanced Settings or a solution package, then populating them via the Web API.

How we handle it

Freshsales requires custom fields to exist in the destination before API writes can land data into them. We coordinate with the customer's Freshsales admin to pre-create every target custom field (matching the Dynamics schema discovered during scoping) before our import job runs. Any missing custom field causes a silent skip or partial import for that field, which only surfaces during post-migration reconciliation. We generate a complete field-list document during scoping so nothing is missed.

high

Activity records with inactive owner IDs fail silently at the destination

Dynamics stores activity owners as a user ID reference.

How we handle it

If the original Dynamics user is inactive or unlicensed, the owner ID may not resolve in Freshsales, causing the activity to import without an owner or drop during the insert batch. We audit all Owner IDs referenced in Tasks, Emails, PhoneCalls, and Appointments before migration, map inactive owners to a designated migration admin or legacy-inactive placeholder in Freshsales, and preserve the original owner name in a custom field for audit so the assignment chain is reconstructable.

medium

Professional tier custom-table ceiling blocks migration without schema simplification

Microsoft Dynamics 365 Sales Professional caps custom tables at 15.

How we handle it

If the source environment has more than 15 custom Dataverse tables, records referencing tables above the limit cannot be imported without an Enterprise license upgrade or schema simplification before migration. We detect the exact custom table count during scoping. If the ceiling applies, we present the customer with a concrete list of tables to merge, archive, or drop, and we document which records reference them so no data is silently excluded during migration.

medium

Price list tier flattening changes historical deal values

Dynamics Price Lists support quantity-based pricing tiers per product.

How we handle it

Freshsales Products store a single unit price. If a Dynamics account uses multi-tier price lists with volume discounts, we collapse them to a median or most-common tier during migration. This means historical Deals that used a tier-3 price may show a different line-item total in Freshsales than in Dynamics. We present the flattening strategy during scoping, and the customer approves the approach before migration runs.

medium

Quote-Order-Invoice chain cannot map as separate Freshsales objects

Dynamics separates Quotes, Orders, and Invoices as three distinct entities with a conversion chain.

How we handle it

Freshsales does not model these as separate objects. We flatten the commercial document chain into Notes attached to the parent Deal with a structured format. If the customer requires full document-level fidelity (separate Quote and Invoice records with line items), we scope this as a post-migration manual rebuild or a separate Freshworks Freshdesk or Freshsales Enterprise configuration engagement rather than a migration item.

How the migration runs

  1. Discovery and scoping

    We audit the source Microsoft Dynamics 365 Sales environment via the Dataverse Web API, capturing Accounts, Contacts, Leads, Opportunities, Activities, Products, Price Lists, custom tables, and owner assignments.

    What this step covers

    We identify the Dynamics tier (Professional or Enterprise) to determine the custom table ceiling applicability, flag inactive owners, and assess engagement volume. We pair this with a Freshsales tier review (Growth, Pro, Enterprise) to confirm custom field and object capacity. The discovery output is a written migration scope, a custom field creation checklist for Freshsales, and a source-citation for the October 2024 pricing impact if renewal falls within the migration window.

  2. Schema pre-creation in Freshsales

    Before any data moves, we generate a complete Freshsales custom field creation checklist based on the Dynamics schema audit.

    What this step covers

    The customer's Freshsales admin creates each custom field in the destination UI and publishes. We validate the field list against the source schema during a staging check. If custom Dataverse tables exist above the Professional tier ceiling, we negotiate a simplification plan with the customer before proceeding: merge tables, archive stale data, or upgrade the Dynamics license. Schema readiness is a gate condition for migration.

  3. Sandbox migration and reconciliation

    We run a full migration into a Freshsales sandbox or staging environment using production-like record volumes.

    What this step covers

    The customer reconciles record counts (Accounts in, Contacts in, Leads in, Deals in, Tasks in), spot-checks 25-50 records field-by-field against the Dynamics source, and signs off the mapping. Any missing fields, incorrect lookups, or data transformations are corrected here. The sandbox run produces a reconciliation report that establishes the baseline for production cutover.

  4. Owner reconciliation and User provisioning

    We extract every distinct Dynamics User referenced as an owner on Contacts, Accounts, Opportunities, and Activities and match by email against the Freshsales destination User table.

    What this step covers

    Owners without a matching Freshsales User are flagged in a reconciliation queue. The customer's Freshsales admin provisions any missing Users (active or inactive based on whether the original Dynamics user is still employed). Migration cannot proceed past this step because OwnerID lookups are required on standard objects and unattributed records create data quality issues post-migration.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (first, because all other objects reference them), Contacts (with AccountId resolved), Leads (with status and score preserved), Deals (with AccountId, OwnerId, and stage resolved), Products (with pricing), Activities (Tasks and Events via REST API with batch chunking), Notes and Attachments.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. If the Dynamics environment has a large engagement history, we chunk the activity migration into batches of 500-1,000 records to stay within Freshsales API rate limits.

  6. Cutover, validation, and automation inventory handoff

    We freeze Dynamics writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record.

    What this step covers

    We deliver a written inventory of every active Dynamics Power Automate workflow and Dataverse automation with its trigger, conditions, and recommended Freshsales Workflow equivalent. We do not rebuild automations inside the migration scope. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's sales team during the first business week in Freshsales.

Dynamics 365 Freshsales
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · FreshsalesRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
7-12 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object complexity, and engagement history size. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Dynamics 365 to Freshsales →

Why teams move from Dynamics 365 to Freshsales

  • Implementation partner overhead makes Microsoft Dynamics 365 Sales expensive beyond licensing. Certified Microsoft partners typically add 30-50% to the total project cost for initial configuration, and ongoing changes require partner involvement for anything beyond basic administration. Freshsales provides a self-service setup path with guided onboarding, reducing the total cost of ownership for teams without dedicated IT staff and without a budget for ongoing partner retainers.
  • The Professional tier 15-custom-table ceiling forces a license upgrade to Enterprise before any migration can proceed if the source environment is customized. Teams that have built workflows on top of Dynamics Professional cannot move their custom tables without upgrading to Enterprise at $105 per user per month. Freshsales includes custom fields and custom objects at all paid tiers without a table-count ceiling, removing this structural constraint.
  • Non-Microsoft integrations require additional configuration or third-party middleware in Microsoft Dynamics 365 Sales . Reviewers on G2 and Reddit consistently cite integration complexity as a pain point when connecting to non-Microsoft tools like Slack, Google Workspace, or non-Microsoft ERPs. Freshsales offers a REST API and native Zapier and Make connectors for the SaaS tools most SMB and midmarket teams already use, reducing integration overhead without middleware.
  • Power Platform request limits throttle large-scale data extraction. Dataverse enforces per-environment API call quotas that restrict bulk export throughput for migrations with hundreds of thousands of records. Freshsales uses standard REST API imports with configurable batch sizes, avoiding the Power Platform quota management that adds engineering complexity to Dynamics exits.
  • October 2024 pricing increases of $15 per user per month across all Dynamics Sales tiers apply at renewal for existing customers. A 20-user team on Enterprise pays $2,400 more per year after renewal, compounding annually. Freshsales pricing at $29-$89 per user per month is predictable and does not include a mid-contract price increase mechanism, making the total cost difference measurable and growing over time.

Questions, answered

Dynamics 365 to Freshsales migration questions

How long does a Microsoft Dynamics 365 Sales to Freshsales migration take?

Migrations under 20,000 Contacts and 5,000 Opportunities with no custom Dataverse tables complete in three to five weeks. Migrations with custom tables, large activity histories (over 200,000 records), or territory re-modeling requirements move to seven to twelve weeks because of schema pre-creation coordination, activity batch processing, and the sandbox reconciliation gate. Discovery and scoping adds one to two weeks before migration begins regardless of size.

Do Dynamics Power Automate workflows and sales sequences migrate to Freshsales?

No. Power Automate cloud flows, Dataverse plug-ins, and Dynamics sales sequences are configured at the platform level and do not have a standard portable representation. We do not migrate them as code. We deliver a written inventory of every active Power Automate flow and sales sequence with its trigger, conditions, actions, and a recommended Freshsales Workflow or sequence equivalent. The customer's admin rebuilds them inside Freshsales or with a Freshsales professional services engagement. We scope the inventory as a standard deliverable but not as a rebuild task.

Will we lose historical activity data (calls, emails, meetings, tasks)?

No. We migrate the full engagement history from Dynamics Activities (Tasks, Emails, PhoneCalls, Appointments) into Freshsales Tasks and Events. Each activity retains its subject, description, date, owner, and the parent record reference (Contact, Account, or Deal). Activity timeline ordering is preserved by setting the created_at timestamp to the original Dynamics createdon value. Phone call disposition, duration, and meeting location migrate as custom fields on the corresponding Freshsales record.

Our Dynamics environment uses territory management. How is that handled?

Dynamics territory hierarchies are available on Enterprise tier only and are modeled as a structured geographic tree. Freshsales models territories as a picklist field on the Contact, Account, or Deal with assignment rules that run on import. We extract the Dynamics territory names and flatten them to Freshsales territory list values during migration. If the customer needs territory-based assignment rules, we configure Freshsales territory assignment rules during the staging phase to match the Dynamics hierarchy as closely as possible. Territory reports require rebuilding in Freshsales analytics.

We have custom Dataverse tables. Can we migrate them to Freshsales?

Yes, but only if the custom table count is within the destination Freshsales tier's capacity. All Freshsales paid tiers support custom objects and custom fields without a hard table ceiling, which is a direct improvement over Microsoft Dynamics 365 Sales Professional's 15-table limit. If the source Dynamics environment is on the Professional tier with more than 15 custom tables, the migration requires either an Enterprise license upgrade before migration or schema simplification (merging or archiving custom tables) before we can proceed. We detect the exact count during scoping and present options.

Can we test the migration before going live?

Yes, and we require it. We run a full migration into a Freshsales staging environment as a mandatory gate before production migration begins. The customer reviews record counts, spot-checks 25-50 records field-by-field against Dynamics, and signs off the mapping before we touch production data. Any corrections to field mapping, lookup resolution, or stage names happen in staging, not in production. This is standard FlitStack AI process and is included in the migration scope at no additional cost.

What happens to our Dynamics reports and dashboards after migration?

Dynamics reports built in the reporting workspace use FetchXML or Power BI and are tied to Dataverse entity contexts. These do not migrate. We export a list of all active Dynamics reports and dashboards during scoping as a separate deliverable so the customer's admin can rebuild them inside Freshsales Reports or connect Freshsales to the same Power BI workspace post-migration. Salesforce-style or Power BI-native report rebuilding is outside the migration scope and can be scoped as a separate analytics engagement.

Get a quote

Moving from Dynamics 365 to Freshsales?

Tell us roughly how many records and objects you have. We scope the mapping and the Freshsales setup with you, then send a quote.

Get a quote