Close to Dynamics 365 migration
We migrate Leads, Contacts, Companies, and Opportunities from Close into Microsoft Microsoft Dynamics 365 Sales with the Lead-to-Account conversion workflow resolved upfront, activity history preserved through the Dynamics 365 Data Migration Framework, and every Close Custom Field mapped to a typed Dynamics 365 field before cutover.
FlitStack AI migrates leads, contacts, accounts, opportunities and record type + sales process from Close to Dynamics 365, 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.

What moves from Close to Dynamics 365?
Moving from Close to Microsoft Microsoft Dynamics 365 Sales is a structural migration that reshapes the data model.
Read the full summary
Close collapses prospects into Leads and Contacts with a shared inbox; Dynamics 365 separates these into Lead, Contact, and Account with an explicit Convert action and a required Account as the parent of every Contact. We resolve the entity hierarchy during scoping, design the Lead-to-Contact-to-Account chain before any records move, and preserve the original Close status labels in custom fields for audit. Activity history (calls, emails, SMS, tasks) migrates as Dynamics 365 Activity records attached to the correct parent entity using the Dynamics 365 Bulk API. Close Workflows, Smart Views, and Custom Activities do not migrate as logic; we deliver a written inventory of every active Workflow and Custom Activity type for the customer's admin to rebuild in Dynamics 365.
Lead → Lead
Close Leads map directly to Dynamics 365 Lead.
How it maps
The Close status label (e.g. Potential, Contacted, Qualified) migrates to a custom Lead field close_original_status__c for audit. We set Lead.Status to a Dynamics 365 standard status value that most closely matches the original Close label, with a mapping table agreed upon during scoping. The close_date field maps to estimatedclose Date. Lead.OwnerId is resolved via email match against the destination User table.
Contact → Contact
Close Contacts require an Account parent in Dynamics 365.
How it maps
We first create Account records from Close Companies (or from the organisation field on Close Contact if no Company exists). Then we create Contact records linked to the resolved AccountId. Any Contact without an organisation in Close becomes a Contact linked to a placeholder Account, flagged for the customer admin to merge or resolve post-migration. The original Close contact ID migrates to a custom field close_contact_id__c for reconciliation.
Company → Account
Close Company records map to Dynamics 365 Account.
How it maps
The Company name becomes Account.Name, domain becomes Account.Website, and address fields map to Address composite fields. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert time. We use Company.name as the dedupe key during Account creation to avoid duplicates from any overlapping Contact-level organisation entries.
Opportunity → Opportunity
Close Opportunities map to Dynamics 365 Opportunity.
How it maps
The pipeline-stage assignment maps to a Microsoft Dynamics 365 Sales Process and Record Type configured before migration. Opportunity.Amount migrates to EstimatedValue; close_date migrates to estimatedclose Date. If Close Opportunity is linked to a Contact (no Company), we resolve the Contact's parent Account and set AccountId before insert.
Pipeline → Record Type + Sales Process
Each Close Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values.
How it maps
Stage probability percentages migrate from Close to the Dynamics 365 Stage Probability field. Stage ordering is preserved per the pipeline sequence in Close.
Pipeline Stage → Opportunity Stage
Close pipeline stages map to Dynamics 365 Stage values within the corresponding Sales Process.
How it maps
Stage names and display labels carry over directly. If Close has custom stage probability weights, these are set on the OpportunitySalesProcess entity after the Sales Process is deployed.
- LeadLead1:1
- ContactContactsplit
- CompanyAccount1:1
- OpportunityOpportunity1:1
- PipelineRecord Typetransformed
- Pipeline StageOpportunity Stagetransformed
+ 6 more in the mapping below
How Close and Dynamics 365 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.
| Dimension | Close | Dynamics 365 |
|---|---|---|
| Prospect entity model | Leads and Contacts with shared inbox and no required Account | Lead (unqualified) converts to Contact under an Account (qualified) |
| Company entity | Companies as standalone records optionally linked to Contacts | Accounts required as parent of every Contact; no standalone Contact without Account in standard model |
| Pipeline and stages | Multiple pipelines with custom stage names per pipeline | Sales Processes and Record Types replicate pipeline/stage structure at all paid tiers |
| Activity types | Calls, emails, SMS, tasks, and Custom Activities as distinct types in one thread | Tasks, Appointments, Emails with EmailMessages; phone call logged as Task with CallType |
| Custom object support | Custom Activities and Custom Objects on Growth and Scale plans ($99-149/seat) | Custom entities and attributes available from Sales Professional ($65/user) onward |
| Pricing model | Per-seat with no marketing-contact billing; calling features require Growth or Scale | Per-user module licensing; Sales Professional from $65/user/mo with no per-contact metering |
| Workflow automation | Property-triggered Workflows gated at Growth ($99) and Scale ($139) | Dynamics Automate (Power Automate) with connectors to Dataverse from any Sales tier |
| Mobile experience | Widely criticised for missed notifications and refresh friction | Native app with Outlook and Teams integration; strong mobile UX ratings |
What to watch for in a Close to Dynamics 365 migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Close CSV exports silently drop all activity history
Close's CSV export format omits activity data by design.
How we handle it
Calls, emails, SMS, and tasks appear only in JSON exports. If the customer has been using CSV exports for their data, their full activity history is not present in the exported file. We request JSON-only exports for all activity-bearing records and flag any account that appears to have used CSV exports during scoping. Without JSON, we cannot migrate the engagement timeline that sales reps rely on for context when reopening accounts.
Accounts are required in Dynamics 365; Close has no equivalent
Dynamics 365 requires an Account as the parent of every Contact in the standard model.
How we handle it
Close has Companies optionally linked to Contacts but no mandatory Account entity. We must denormalise every Close Contact that has an organisation name into an Account record first, then link the Contact to it. Contacts with no organisation field become Contacts attached to a placeholder Account flagged for admin resolution. Skipping this step produces orphaned Contacts that fail Dynamics 365 validation on insert.
Close Workflows do not migrate to Dynamics 365 Automate
Close Workflows (Growth and Scale plans only) automate outreach based on triggers and steps.
How we handle it
Dynamics 365 uses Power Automate with a different event model and connector set. We do not migrate Workflows as code. We deliver a written inventory of every active Close Workflow with its trigger, conditions, and actions, plus a recommended Power Automate flow equivalent. The customer's admin or a Microsoft partner rebuilds them post-migration.
Custom Activities require strict three-phase dependency ordering
A Close Custom Activity Type must be created in Dynamics 365 as a Dataverse entity before any Custom Field scoped to that type can be added, and both must exist before activity instances can be imported.
How we handle it
Attempting to import in the wrong order returns validation errors from the Dataverse API. We sequence Custom Activity migration as a three-phase pipeline: create entity, create type-scoped attributes, import instances. Any missing phase halts the dependent phase until corrected.
Dynamics 365 field security and validation rules can block bulk import
Dynamics 365 orgs commonly enforce required field rules, conditional field requirements, and option set whitelists that differ from Close's schema.
How we handle it
A migration user performing bulk inserts must have the necessary Security Role permissions on the target entity and the Bulk Import privilege. We coordinate with the customer's Dynamics 365 admin to grant the migration user the correct role before import and either temporarily relax blocking validation rules or extend them with a migration-context bypass condition.
How the migration runs
Discovery and source audit
We audit the source Close account across plan tier (Solo/Essentials/Growth/Scale), active Custom Activities and Custom Objects, pipeline count, stage definitions, Smart View filters, active Workflows, and activity volume per type.
What this step covers
We verify the export method (JSON vs CSV) with the customer because CSV exports strip activity history silently. We pair this with a Dynamics 365 edition review: Sales Professional ($65/user) covers most migrations; Sales Enterprise ($105/user) is required for advanced AI insights, conversation intelligence, or customisability at scale.
Schema design and Account strategy
We design the destination Dynamics 365 schema.
What this step covers
This includes provisioning custom attributes on Lead, Contact, and Opportunity; creating Record Types and Sales Processes per Close Pipeline; creating Dataverse entities for Custom Activity Types; and resolving the Account strategy for Contacts without a Company in Close. The schema is deployed into a Dynamics 365 Sandbox via the Dataverse Web API for validation before production migration begins.
Sandbox migration and reconciliation
We run a full migration into a Dynamics 365 Sandbox using production-like data volume.
What this step covers
The customer's RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the Close source, and signs off the schema and mapping before production migration. Any mapping corrections and Account-resolution issues surface here.
Owner reconciliation and User provisioning
We extract every distinct Close Owner referenced on Lead, Contact, Opportunity, and Activity records and match by email against the Dynamics 365 destination org's User table.
What this step covers
Owners without a matching User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before record import resumes because OwnerId references are required on most standard entities.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Close Companies), Leads (with original status preserved in close_original_status__c), Contacts (with AccountId resolved from Company or placeholder), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activity history (Tasks, Appointments, EmailMessages via Dynamics 365 Bulk API with batch chunking), Custom Activity Types and fields (phase one and two), Custom Activity instances (phase three), Attachments and Call Recordings.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and Workflow rebuild handoff
We freeze Close writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record.
What this step covers
We deliver the Workflow inventory document to the customer's admin team listing every active Close Workflow with its trigger, conditions, actions, and recommended Power Automate equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Close Workflows as Power Automate flows inside the migration scope; that is a separate engagement or an internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom object count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Close to Dynamics 365 →Why teams move from Close to Dynamics 365
- Teams needing Microsoft 365 native integration (Outlook email and calendar tracking, Teams collaboration, SharePoint document management) move to Dynamics 365 because the integration is built in rather than requiring Zapier or API workarounds. Reviewers on Reddit and comparison blogs cite the lack of native Slack integration in Close as a recurring friction point; Dynamics 365 resolves this by natively connecting the Microsoft stack that many enterprise teams already use.
- Close's feature set is deliberately narrower than enterprise CRMs. Teams that need advanced reporting, multi-territory pipeline analysis, complex workflow logic, or CPQ capabilities find the product's boundaries frustrating. Microsoft Dynamics 365 Sales provides deeper customisation, Business Rules, and Power BI reporting without third-party tooling, which attracts RevOps teams outgrowing Close's flat feature model.
- Custom Activities and Custom Objects in Close are gated behind Growth ($99/seat) and Scale ($139/seat) plans and introduce dependency-ordering complexity during migration. Microsoft Dynamics 365 Sales Professional ($65/user) supports custom entities and attributes natively with no per-feature surcharge, which lowers the cost ceiling for teams that need custom data models but do not want to pay Close's Scale-tier pricing.
- Mobile app frustration is one of the most consistent complaints in Close's Capterra and G2 reviews, with users citing missed call notifications, stale inbox data, and the need to manually reopen the app to refresh. Dynamics 365 mobile receives strong satisfaction scores and provides native push notifications tied to Outlook and Teams, which is a meaningful quality-of-life improvement for field sales and outside-rep teams.
- Some teams reach Close's ceiling on reporting flexibility when analysing multi-dimensional pipeline performance across product lines, territories, or custom attribution models. Microsoft Dynamics 365 Sales with Power BI provides enterprise-grade pipeline analytics that integrate directly with Dataverse without requiring a data warehouse export, which attracts data-driven sales leadership making the switch.
Questions, answered
Close to Dynamics 365 migration questions
How long does a Close to Microsoft Microsoft Dynamics 365 Sales migration take?
Most migrations land between three and five weeks for accounts under 20,000 Leads and Contacts, 3,000 Opportunities, and no Custom Activities. Migrations with Custom Activities, multi-pipeline structures, large activity histories (over 300,000 records), or Companies requiring denormalisation to Accounts move to eight to fourteen weeks because of the three-phase Custom Activity pipeline, Dynamics 365 API pagination, and Workflow documentation scope.
Do Close Workflows, Smart Views, and Custom Activities migrate to Dynamics 365?
No. Close Workflows and Dynamics 365 Power Automate are different automation models with different triggers, connectors, and action types. We do not migrate them as code. We deliver a written inventory of every active Close Workflow and every Custom Activity Type with its schema and field definitions for the customer's admin or a Microsoft partner to rebuild. Smart Views are exported as named saved search filter criteria; they must be recreated manually in Dynamics 365 Advanced Find or as saved views.
Why do we need to create Account records when Close has Companies?
Dynamics 365 requires every Contact to be attached to an Account as the organisational parent. Close's Company is a more flexible entity that can exist independently or be linked to Contacts. During migration, we create an Account from every Close Company and link each Contact to its corresponding Account. Any Contact without a Company in Close becomes a Contact attached to a placeholder Account that the customer's admin resolves post-migration. This structural difference is one of the most important decisions to make during scoping.
Can we keep Close for calling while moving sales to Dynamics 365?
Yes. A hybrid stack is one of the more common patterns we migrate. Some teams keep Close as the dialling and SMS tool while using Dynamics 365 for pipeline management, reporting, and Account-based selling. In this pattern we migrate Leads, Contacts, Accounts, and Opportunities to Dynamics 365 and preserve the activity history from Close in Dynamics 365 Activity records. The customer runs two systems in parallel, which introduces a sync overhead we flag clearly during scoping. The alternative is to adopt Microsoft Dynamics 365 Sales for the full stack and retrain the team on its calling interface.
Do we lose historical call recordings and SMS history during migration?
No. Call recordings and SMS history are exported from Close via JSON and re-uploaded as Note records in Dynamics 365 attached to the matching Activity Task. Recording duration and disposition migrate to custom fields on the Task. We flag any recording exceeding Dynamics 365 file size limits before migration and resolve with the customer admin. The full activity timeline with timestamps is preserved.
Can FlitStack AI also migrate from Close to Dynamics 365 Business Central?
Yes. Close to Dynamics 365 Business Central is a valid migration scope when the customer moves from a CRM-only tool to a CRM-plus-ERP combined platform. The migration maps Close's Accounts and Contacts to Business Central's Customers and Contacts respectively, and maps Opportunities to Sales Orders or Jobs depending on the business process. We handle the CRM layer migration as described in this page and coordinate with the customer's Business Central partner on the ERP data model separately.
Related migrations
Dynamics 365 implementation
Set up Dynamics 365 and migrate into it as one engagement.
See the service → Leadforce CRM to Dynamics 365Mapping · history · rollbackHoneyBook to Dynamics 365Mapping · history · rollbackHousecall Pro to Dynamics 365Mapping · history · rollbackJobber to Dynamics 365Mapping · history · rollbackYardi to Dynamics 365Mapping · history · rollbackInsightly CRM to Dynamics 365Mapping · history · rollback Close to monday CRMMapping · history · rollbackClose to HubSpotMapping · history · rollbackClose to SalesforceMapping · history · rollbackSources: official documentation
- Dynamics 365 environment strategy — Microsoft Learn
- Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)
- Import data (all record types) — Power Platform | Microsoft Learn
- Execute Batch Operations on Dataverse — Microsoft Learn
- Service protection limits (Microsoft Dataverse)
- Entity relationship behavior — Microsoft Learn
Get a quote
Moving from Close to Dynamics 365?
Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.
Get a quote