CRM migration

Migrate from Combit CRM to Microsoft Dynamics 365 Sales

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 logo

Combit CRM

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

100%

14 of 14

objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Combit CRM logo

Combit CRM

What's pushing teams away

  • Interface feels technical and sophisticated—multiple reviewers describe the UI as complex, with input masks that lack a modern design feel.
  • Difficulty mapping daily work processes—users report that intuitive process mapping is harder than expected despite the automation capabilities.
  • Feature gaps relative to modern CRMs—some reviewers noted the platform required more features than it provided during their evaluation period.
  • German-only language barrier—businesses outside German-speaking regions cannot use the platform, limiting international team adoption.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How Combit CRM objects map to Microsoft Dynamics 365 Sales

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)

maps to

Microsoft Dynamics 365 Sales

Contact

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Account

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Opportunity

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Business Process Flow + Record Type

1:1
Fully supported

Combit 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)

maps to

Microsoft Dynamics 365 Sales

Activity (Task, Email, Appointment, Note)

1:1
Fully supported

Combit 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)

maps to

Microsoft Dynamics 365 Sales

Contact Custom Fields (__c)

1:1
Fully supported

Combit 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)

maps to

Microsoft Dynamics 365 Sales

Account Custom Fields (__c)

1:1
Fully supported

Combit 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)

maps to

Microsoft Dynamics 365 Sales

Opportunity Custom Fields (__c)

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Custom Entities (Dataverse)

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

SystemUser → OwnerId

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Power Automate Flows (not migrated—rebuilt)

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Reports (not migrated—rebuilt)

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

SharePoint Document Location + Note

1:1
Fully supported

Combit 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

maps to

Microsoft Dynamics 365 Sales

Opportunity Product Lines

1:1
Fully supported

Combit 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.

Gotchas + challenges

What specifically takes care here

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 logo

Combit CRM gotchas

High

No documented REST API for automated migration

Medium

German-language interface complicates discovery

Medium

On-premise deployments require database-level extraction

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • Record-Type Scoping Creates Schema Planning Overhead Before Data Lands

    Combit CRM has no concept of record types—pipelines and stages exist in a single namespace. Dynamics 365 Sales scopes Opportunity Stage pick-list values to individual Record Types, which means each Combit pipeline requires a corresponding Dynamics 365 Record Type before stage mapping can succeed. We deliver a record-type setup plan as part of the migration scope; your Dynamics admin must pre-create the record types in the target environment before we load opportunities. This is a pre-condition, not an afterthought—the schema plan details exactly which record types, page layouts, and security roles need to exist.

  • Combit Workflow Definitions Cannot Migrate—Export-for-Rebuild Required

    Combit CRM embeds workflow automation, input masks, and step-based process logic directly in the CRM configuration. These are not data records—they are platform-level schema constructs with no Dynamics 365 equivalent in the same data layer. Dynamics 365 handles equivalent logic via Power Automate flows and Business Process Flows, which are separate solutions from the CRM records themselves. We export your Combit workflow definitions as a structured reference document (trigger types, step logic, condition branches) so your Dynamics admin can rebuild them in Power Automate. This is disclosed, not handled silently.

  • Multi-Company Contact Associations Collapse to Primary AccountId

    Combit CRM supports assigning a contact to multiple companies natively—a single contact record can reference N companies without a junction table. Dynamics 365 Contacts have a single primary AccountId; additional company relationships use the Account Contact Relationship entity (introduced in Dynamics 365 v9.x). We migrate the most-recently-modified primary company as AccountId and surface remaining company associations as Account Contact Relationships. Your team decides whether to use all migrated relationships or collapse to a primary account.

  • German-Language Data May Need Locale Validation in Dynamics 365

    Combit CRM is primarily used in German-speaking markets; many Combit deployments store umlauts (ä, ö, ü, ß), special characters, and German-specific address formats. Dynamics 365 field character limits and locale settings must be validated against Combit data samples before bulk migration. We run a character-encoding check on the pre-migration sample and flag any records that exceed Dynamics 365 field length limits or contain characters that require Unicode normalization. We also recommend setting the Dynamics 365 language pack to German to preserve display fidelity.

  • Custom Field Creation Must Precede Migration—Field API Names Are Case-Sensitive

    Combit CRM custom field names are flexible and case-insensitive. Dynamics 365 Dataverse custom field API names follow the __c suffix convention and are case-sensitive (e.g., CustomerPriority__c vs. customerpriority__c). Our schema plan lists each Combit custom field with its target Dynamics 365 API name in the correct __c format. Your admin must create these fields in the Dynamics 365 environment before migration runs—attempting to create custom fields during migration introduces a circular dependency and can cause field-level validation failures on opportunity and contact records.

Migration approach

Six steps for a successful Combit CRM to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Combit CRM logo

Combit CRM

Source

Strengths

  • Deep workflow automation with configurable triggers across departments and record types.
  • Highly flexible data model with user-defined fields and customizable pipelines.
  • Strong integration connectivity for external tools and peripheral systems.
  • Configurable interfaces and data entry masks tailored to organization-specific needs.
  • Supports both cloud and on-premise deployment options.

Weaknesses

  • Platform is German-language only, limiting adoption for non-German-speaking teams.
  • No publicly documented REST API, restricting programmatic access and migration automation.
  • Interface described as technically sophisticated and not intuitively modern.
  • Fewer third-party integrations compared to major global CRM platforms.
  • Limited availability of English-language documentation and support resources.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. All 8 core objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Combit CRM and Microsoft Dynamics 365 Sales .

  • Object compatibility

    A

    All 8 core objects map 1:1 between Combit CRM and Microsoft Dynamics 365 Sales .

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Combit CRM: Not publicly documented.

  • Data volume sensitivity

    B

    Combit CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Combit CRM to Microsoft Dynamics 365 Sales migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Combit CRM to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during Combit CRM to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Combit CRM to Dynamics 365 migrations complete within 48–72 hours for under 50,000 records. Complex migrations with 500,000+ records, multiple custom entities, or extensive custom-field sets extend to 5–10 days. The record-type setup phase (creating Dynamics 365 schemas before data lands) typically runs in parallel and does not add to the migration clock. This timeline assumes a stable network connection and timely provision of source credentials.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Combit CRM.
Land in Microsoft Dynamics 365 Sales , intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day