CRM migration

Migrate from Combit CRM to Nutshell

Field-level mapping, validation, and rollback between Combit CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Combit CRM logo

Combit CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Combit CRM and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Combit CRM to Nutshell is a bilingual, API-routing migration. Combit CRM has no publicly documented REST API and is German-language only, so we extract data via direct database access (on-premise) or structured CSV/Excel exports from the application, translate all field names and picklist values during transformation, then load into Nutshell via its REST API. Nutshell's data model differs from Combit's: Combit stores Addresses as separate linked records, while Nutshell embeds address fields on the People and Company objects; Combit Projects map to Nutshell Deals with a custom field carrying the original project name; Combit Activities map to Nutshell's Activity timeline. We do not migrate Combit workflows or process automations as code—these require a written rebuild inventory delivered to the customer's admin. Custom fields and user-defined pipelines transfer as configuration or mapped data depending on the target field type.

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

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Combit CRM objects map to Nutshell

Each row shows how a Combit CRM object lands in Nutshell, 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 (Kontakte)

maps to

Nutshell

Person

1:1
Fully supported

Combit Contacts migrate to Nutshell People records with standard fields (name, email, phone, title) preserved. The Combit contact's link to its parent Address (Anschrift) record is resolved during transform: the primary address fields (street, city, postal code, country) are embedded into Nutshell's address fields on the Person record, and any secondary addresses are stored in a custom text field for manual reconciliation.

Combit CRM

Address (Anschrift)

maps to

Nutshell

Address (embedded on Person and Company)

1:1
Fully supported

Combit Addresses are separate records that can link to multiple Contacts, unlike Nutshell where address is embedded. We resolve the primary address for each Contact by following the Combit address relationship, embed those fields into the Nutshell Person record, and flag any Contact with multiple linked Combit Addresses for manual review at the destination because Nutshell does not support multiple address records per Person.

Combit CRM

Company (Firma)

maps to

Nutshell

Company

1:1
Fully supported

Combit Company records map directly to Nutshell Company records. Company name, domain (if present), phone, and industry classification migrate as standard fields. The Company record is created before any linked Person import so that the Person-to-Company relationship is satisfied at insert time. Any Combit custom fields on Company are mapped to Nutshell custom fields or stored as text notes.

Combit CRM

Project (Projekt)

maps to

Nutshell

Deal

1:1
Fully supported

Combit Projects migrate to Nutshell Deals with a custom field project_name__c carrying the original Combit project name for audit. Project status maps to the closest Nutshell pipeline stage (Open, Won, Lost), and project budget or value maps to Deal value. Projects spanning multiple contacts transfer as a single Deal with the primary contact linked; secondary contacts are added to a custom text field for manual relationship rebuild.

Combit CRM

Deal (Verkauf/Geschäft)

maps to

Nutshell

Deal

1:1
Fully supported

Combit Deals map to Nutshell Deals with pipeline stage, value, owner, and expected close date preserved. Combit's configurable deal pipelines map to Nutshell pipeline stages that we configure in the target account before migration. Any deal-specific custom fields map to Nutshell custom fields on Deal.

Combit CRM

Activity (Aktivität)

maps to

Nutshell

Activity (on Person, Company, Deal)

1:1
Fully supported

Combit Activities (calls, meetings, tasks, notes) migrate to Nutshell Activity records on the relevant Person, Company, or Deal. Activity type, date, duration, and description are preserved. Calls map to Nutshell call entries, meetings map to meeting entries, and standalone notes map to note entries. The parent record reference is resolved during transform using the Combit activity-to-contact and activity-to-project relationships.

Combit CRM

Custom Fields (Benutzerdefinierte Felder)

maps to

Nutshell

Custom Fields

lossy
Mapping required

Combit allows user-defined fields across Contacts, Companies, Deals, Projects, and Activities. We identify all custom field definitions during discovery, translate German field labels, map data types to Nutshell field types (text, number, date, picklist), and pre-create the custom fields in Nutshell before data load begins. Any Combit field types without a direct Nutshell equivalent (for example, complex multi-select hierarchies) are stored as text fields with a migration note for the customer.

Combit CRM

User (Benutzer/Vertriebspartner)

maps to

Nutshell

User

1:1
Fully supported

Combit users map to Nutshell users by email address. Owner assignments on Contacts, Deals, and Activities are resolved by matching Combit owner email to Nutshell user email. Any Combit user without a matching Nutshell account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Combit users are mapped to inactive Nutshell users to preserve historical assignment.

Combit CRM

Attachment and Document

maps to

Nutshell

Attachment (on Person, Company, Deal)

1:1
Fully supported

Combit file attachments are extracted to a file store, assigned original filenames, and uploaded to Nutshell's file attachment support on the relevant Person, Company, or Deal record. We map the attachment by record type and Combit record ID to the target Nutshell record during load. Large attachments (over the Nutshell file size limit) are flagged for manual re-upload post-migration.

Combit CRM

Tag and Category (Kategorie)

maps to

Nutshell

Tag

1:1
Fully supported

Combit categorical tags on records migrate to Nutshell tags. Multi-value tag fields from Combit are split and applied as individual Nutshell tags on the mapped record. If the Combit taxonomy uses hierarchical categories (parent-category/sub-category), the full path is preserved as a tag string and can be reorganized in Nutshell post-migration.

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • No Combit REST API requires non-standard extraction

    Combit CRM has no publicly documented REST API in either German or English, which means we cannot run API-based migration jobs against it. For on-premise deployments we negotiate read-only database credentials and extract directly from the Combit database schema. For cloud-hosted Combit instances we use the application's built-in CSV or Excel export functionality. If the application export is limited in scope (for example, exports are capped or do not include custom fields), we negotiate a custom export specification with the customer and validate row counts and field completeness before writing any transform logic.

  • German-language interface and data requires bilingual scoping

    Combit CRM is available in German only. During discovery, scoping, and field mapping we work with bilingual contacts or engage a German-speaking analyst to navigate the admin panel, identify custom field definitions, review pipeline stage names, and confirm export options. All Combit field labels, picklist values, and workflow names must be translated to English during the mapping phase. Misinterpreting a German field label during mapping results in data populating the wrong Nutshell field, so we cross-validate field definitions with the customer's Combit admin before writing the transform.

  • Address relationship resolution between Combit and Nutshell

    Combit stores Addresses as separate records that can link to multiple Contacts (one-to-many), while Nutshell embeds address fields directly on Person and Company records with no separate address object. If a Combit Contact has multiple linked Address records, we map the primary address to Nutshell and flag the secondary addresses for manual reconciliation because Nutshell does not support multiple address records per Person. This is a structural mismatch that must be communicated during scoping so the customer can decide how to handle multi-address contacts.

  • Combit custom fields may lack direct Nutshell equivalents

    Combit supports extensive user-defined fields with data types that may not map one-to-one to Nutshell's field type options. Complex picklist hierarchies, date-range fields, or multi-select fields from Combit may need to be stored as text fields in Nutshell with a migration note. We identify all custom field definitions during discovery, map their types during transform design, and pre-create custom fields in Nutshell before load. Fields that cannot be migrated structurally are documented with their Combit field name, record count, and content sample so the customer admin can manually re-enter them in Nutshell post-migration.

Migration approach

Six steps for a successful Combit CRM to Nutshell data migration

  1. Discovery and extraction method determination

    We audit the Combit CRM instance to determine the deployment model (cloud or on-premise), identify all record types in use (Contacts, Companies, Deals, Projects, Activities, custom fields), and agree on the extraction method. For on-premise deployments we negotiate read-only database credentials and document the table schema, primary keys, and foreign key relationships. For cloud deployments we use the application's export functionality. We also confirm the Nutshell target account plan, verify custom field limits per plan tier, and identify any Nutshell API access credentials for load operations.

  2. Bilingual field mapping and transform design

    We map every Combit field (standard and custom) to a Nutshell field using a bilingual glossary assembled with the customer's Combit admin. All German field labels and picklist values are translated to English. We resolve the address relationship (Combit Address linked to multiple Contacts maps to Nutshell Person with primary address embedded; secondary addresses flagged for manual review). Pipeline stages from Combit Deals and Projects are mapped to Nutshell pipeline stages that we configure in the target account before migration begins.

  3. Data extraction and validation

    For on-premise Combit we run extraction queries against the database, exporting Contacts, Companies, Deals, Projects, Activities, and attachments in dependency order. For cloud Combit we run structured CSV exports from the application. We validate row counts against Combit's reported totals and flag any discrepancy before writing transform logic. Attachments are extracted to a file store with original filenames preserved and mapped to their parent record via Combit record ID.

  4. Schema creation in Nutshell

    We create any required custom fields in Nutshell before data load begins, matching Combit data types to Nutshell field types. We configure Nutshell pipeline stages to align with the Combit pipeline structure. The schema is validated against the mapping document and approved by the customer before the first load phase runs.

  5. Production migration in record dependency order

    We load data into Nutshell in dependency order: Companies first (so they exist before People), People (with address fields embedded and owner resolved by email), Deals (with pipeline stage and value mapped, project name carried in a custom field), Activities (resolved against the parent Person, Company, or Deal), and attachments (linked by record type and original ID). Each phase emits a row-count reconciliation report showing imported versus expected counts, and any record rejected during load is logged with the reason for correction before re-import.

  6. Cutover, validation, and automation rebuild handoff

    We freeze Combit CRM writes during cutover, run a final delta migration of records modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of Combit workflows, process automations, and custom field definitions requiring rebuild in Nutshell, with the closest Nutshell equivalents noted. We support a post-migration validation window during which the customer spot-checks record counts, field accuracy, and activity timeline completeness. We do not rebuild Combit automations as Nutshell workflows as part of the migration scope; that is a separate engagement or an internal admin task.

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.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Combit CRM and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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 Nutshell 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 Nutshell data migrations

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

Can't find your answer?

Walk through your Combit CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Combit CRM to Nutshell migrations land between three and five weeks for accounts under 10,000 contacts with direct database access and straightforward custom field mapping. Migrations with on-premise Combit requiring custom export script development, extensive custom field coverage across all objects, large Activity histories, or complex address-to-contact relationship resolution move to six to nine weeks because of extraction scoping and transform design time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Combit CRM.
Land in Nutshell, 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