CRM migration
Field-level mapping, validation, and rollback between Combit CRM and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Combit CRM
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
14 of 14
objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
48–72 hours
Overview
Combit CRM and Microsoft Dynamics 365 Sales take different approaches to CRM data architecture. Combit CRM stores contacts, companies, and deals as flat relational records with extensive custom-field support and built-in workflow automation. Dynamics 365 Sales structures data using the Dataverse data model: Accounts (companies), Contacts (people), Leads, and Opportunities (deals), with record types governing page layouts and stage pick-lists per business unit. We map Combit contacts directly to Dynamics 365 Contacts, Combit companies to Accounts, and Combit deals to Opportunities, applying value-mapping for stage names and preserving custom fields as Dynamics 365 custom fields. Combit workflows and process automations cannot migrate—they require rebuilding using Dynamics 365 Business Process Flows or Power Automate. Activity history (calls, emails, meetings, notes) migrates to Dynamics 365 Activities with original timestamps and owner attribution. Our migration uses Combit's export API or direct database access, transforms records through our mapping engine, and loads via the Dynamics 365 Data Import API or Dataverse bulk operations. A 24–48 hour delta-pickup window captures in-flight changes during cutover, and an audit log plus rollback capability protects against reconciliation failures.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Combit CRM platform overview
Scorecard, SWOT, gotchas, and pricing for Combit CRM.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Combit CRM object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Combit CRM
Contact (Person)
Microsoft Dynamics 365 Sales
Contact
1:1Combit CRM person records map directly to Dynamics 365 Contacts. The primary company link in Combit translates to the Contact.AccountId lookup in Dynamics. For Combit contacts without a primary company, we attach to a placeholder Account or flag for manual assignment.
Combit CRM
Company
Microsoft Dynamics 365 Sales
Account
1:1Combit CRM company records map 1:1 to Dynamics 365 Accounts. Company hierarchies (parent/child) in Combit translate to Account.ParentAccountId in Dynamics. Multi-company associations on Combit contacts migrate as Account Contact Relationships in Dynamics. We also ensure that address fields map correctly and any custom fields on the company object are transferred to custom fields on Account.
Combit CRM
Deal / Opportunity
Microsoft Dynamics 365 Sales
Opportunity
1:1Combit CRM deals map to Dynamics 365 Opportunities. Deal name becomes Opportunity.Name, amount maps to Amount, and close date maps to CloseDate. Stage names require value-mapping to Dynamics 365 OpportunityStage pick-list values scoped by record type. We also map probability and forecast category based on the stage mapping, and preserve any custom fields on the deal as Opportunity custom fields.
Combit CRM
Pipeline
Microsoft Dynamics 365 Sales
Business Process Flow + Record Type
1:1Combit CRM pipelines have independent stage sets. Each pipeline in Combit maps to a separate Record Type in Dynamics 365 Sales, which scopes the Opportunity Stage pick-list values. We generate the mapping plan; your Dynamics admin creates the record types before data lands.
Combit CRM
Activity (Call, Email, Meeting, Note)
Microsoft Dynamics 365 Sales
Activity (Task, Email, Appointment, Note)
1:1Combit CRM calls map to Dynamics 365 Tasks with Type='Phone Call'. Emails map to Tasks with Type='Email'. Meetings map to Appointments. Notes map to Dynamics 365 Notes (modern Notes entity, not legacy). Original timestamps and owner attribution preserved in the migrated records.
Combit CRM
Custom Fields (Person)
Microsoft Dynamics 365 Sales
Contact Custom Fields (__c)
1:1Combit CRM stores custom fields per contact as typed properties. Dynamics 365 Sales requires these as custom fields on the Contact object with __c suffix. We create a schema setup plan listing each custom field, its data type, and whether a pick-list value map is needed before migration runs.
Combit CRM
Custom Fields (Company)
Microsoft Dynamics 365 Sales
Account Custom Fields (__c)
1:1Combit CRM company-level custom fields migrate as Account custom fields in Dynamics 365. Industry codes, registration numbers, VAT IDs, and regional flags stored in Combit become custom text, number, or pick-list fields on Account based on the data type analysis.
Combit CRM
Custom Fields (Deal)
Microsoft Dynamics 365 Sales
Opportunity Custom Fields (__c)
1:1Combit deal-level custom fields (discount codes, product references, internal flags) map to Opportunity custom fields. Stage-entry timestamps in Combit become custom datetime fields on Opportunity for reporting continuity. Probability overrides stored in Combit migrate as custom fields.
Combit CRM
Custom Objects
Microsoft Dynamics 365 Sales
Custom Entities (Dataverse)
1:1Combit CRM custom objects (Enterprise tier) map 1:1 to Dataverse custom entities. If the Combit custom object uses N:N associations, we create a junction table entity in Dataverse. We surface the full custom-object dependency graph in the pre-migration plan. This helps avoid circular references during the migration.
Combit CRM
Owner / User
Microsoft Dynamics 365 Sales
SystemUser → OwnerId
1:1Combit CRM owner IDs resolve by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged with a fallback assignment rule (you specify the default). Owner history in Combit migrates as a custom audit field on the record for reporting continuity.
Combit CRM
Workflow Definitions
Microsoft Dynamics 365 Sales
Power Automate Flows (not migrated—rebuilt)
1:1Combit CRM workflow definitions and automation sequences do not migrate. We export workflow definitions as a reference document for your Dynamics 365 admin to rebuild using Power Automate or Business Process Flows. Workflow metadata (trigger types, step logic) is preserved in the export.
Combit CRM
Report / Dashboard Definitions
Microsoft Dynamics 365 Sales
Reports (not migrated—rebuilt)
1:1Combit CRM reports and dashboard configurations are source-platform constructs. The underlying data migrates to Dynamics 365; reports must be rebuilt using Dynamics 365 Reports, Excel templates, or Power BI. We provide a data dictionary showing where each Combit report field lands in Dynamics.
Combit CRM
Attachment / File
Microsoft Dynamics 365 Sales
SharePoint Document Location + Note
1:1Combit CRM file attachments migrate to SharePoint Document Locations linked from Dynamics 365 records (if SharePoint integration is enabled) or as Note attachments. We preserve the original filename, content type, and upload date. Inline images in Combit notes are extracted and re-hosted as file attachments.
Combit CRM
Product Catalog
Microsoft Dynamics 365 Sales
Opportunity Product Lines
1:1Combit CRM products map to Dynamics 365 Opportunity Product records linked via Opportunity Product Bundle or individual line items. Unit price, quantity, and discount fields translate directly. Product relationships in Combit become product relationships in Dynamics 365. We also ensure that any product-specific custom fields are migrated as Opportunity Product custom fields.
| Combit CRM | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact (Person) | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal / Opportunity | Opportunity1:1 | Fully supported | |
| Pipeline | Business Process Flow + Record Type1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note) | Activity (Task, Email, Appointment, Note)1:1 | Fully supported | |
| Custom Fields (Person) | Contact Custom Fields (__c)1:1 | Fully supported | |
| Custom Fields (Company) | Account Custom Fields (__c)1:1 | Fully supported | |
| Custom Fields (Deal) | Opportunity Custom Fields (__c)1:1 | Fully supported | |
| Custom Objects | Custom Entities (Dataverse)1:1 | Fully supported | |
| Owner / User | SystemUser → OwnerId1:1 | Fully supported | |
| Workflow Definitions | Power Automate Flows (not migrated—rebuilt)1:1 | Fully supported | |
| Report / Dashboard Definitions | Reports (not migrated—rebuilt)1:1 | Fully supported | |
| Attachment / File | SharePoint Document Location + Note1:1 | Fully supported | |
| Product Catalog | Opportunity Product Lines1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Combit CRM gotchas
No documented REST API for automated migration
German-language interface complicates discovery
On-premise deployments require database-level extraction
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Audit Combit CRM Data and Generate Schema Setup Plan
We connect to Combit CRM via your provided API credentials or direct database export and extract all object schemas (standard and custom fields, pick-list values, pipeline definitions). We analyze the data model against Dynamics 365's Account/Contact/Lead/Opportunity structure and generate a schema setup plan listing which Dynamics 365 record types, custom fields (__c suffix), and opportunity stage pick-lists must be created before migration. Your Dynamics admin completes this step; we verify readiness before proceeding.
Map Owner and User Records by Email Match
Combit CRM owner IDs are resolved against Dynamics 365 SystemUser records by email address. We generate a pre-flight owner mapping report showing matched users, unmatched Combit owners, and your chosen fallback rule (default owner or unassigned flag). No CRM record migrates without an OwnerId resolved or flagged. If a Combit user has no corresponding Dynamics 365 user account, your team either creates the account first or designates a migration owner for all their records.
Sequence Migration: Accounts → Contacts → Opportunities → Activities
Dynamics 365 enforces foreign-key dependency order: Accounts must exist before Contacts (via AccountId), and Contacts must exist before Opportunities (via Contact Roles and AccountId). We sequence the migration to resolve these dependencies correctly. Companies migrate first, then contacts with company assignments, then deals with stage mapping and record-type assignment, then activity history linked to the migrated records. Custom entities migrate after parent standard objects.
Run Sample Migration with Field-Level Diff
A representative slice of records (typically 100–500 per object) migrates to a Dynamics 365 sandbox or dev environment first. We generate a field-level diff comparing each source field against its destination value, flagging transformation issues, value-mapping mismatches, and truncation risks. You review the diff and approve the mapping before the full run commits. This step catches record-type assignment errors, pick-list value gaps, and custom field type mismatches before production data moves.
Execute Full Migration with Delta-Pickup Window
The full migration runs against Dynamics 365 production. After the bulk load completes, a delta-pickup window of 24–48 hours captures any Combit CRM records created or modified during the cutover window—your team continues working in Combit throughout. An audit log records every record created, updated, or skipped. If reconciliation reveals record-count gaps or data integrity issues, one-click rollback reverts the Dynamics 365 environment to its pre-migration state.
Platform deep dives
Combit CRM
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Combit CRM and Microsoft Dynamics 365 Sales .
Object compatibility
All 8 core objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Combit CRM: Not publicly documented.
Data volume sensitivity
Combit CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Combit CRM to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Combit CRM to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Combit CRM
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.