CRM migration
Field-level mapping, validation, and rollback between Combit CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Combit CRM
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Combit CRM and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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.
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 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)
Nutshell
Person
1:1Combit 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)
Nutshell
Address (embedded on Person and Company)
1:1Combit 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)
Nutshell
Company
1:1Combit 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)
Nutshell
Deal
1:1Combit 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)
Nutshell
Deal
1:1Combit 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)
Nutshell
Activity (on Person, Company, Deal)
1:1Combit 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)
Nutshell
Custom Fields
lossyCombit 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)
Nutshell
User
1:1Combit 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
Nutshell
Attachment (on Person, Company, Deal)
1:1Combit 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)
Nutshell
Tag
1:1Combit 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.
| Combit CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Kontakte) | Person1:1 | Fully supported | |
| Address (Anschrift) | Address (embedded on Person and Company)1:1 | Fully supported | |
| Company (Firma) | Company1:1 | Fully supported | |
| Project (Projekt) | Deal1:1 | Fully supported | |
| Deal (Verkauf/Geschäft) | Deal1:1 | Fully supported | |
| Activity (Aktivität) | Activity (on Person, Company, Deal)1:1 | Fully supported | |
| Custom Fields (Benutzerdefinierte Felder) | Custom Fieldslossy | Mapping required | |
| User (Benutzer/Vertriebspartner) | User1:1 | Fully supported | |
| Attachment and Document | Attachment (on Person, Company, Deal)1:1 | Fully supported | |
| Tag and Category (Kategorie) | Tag1: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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Combit CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Combit CRM and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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 Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Combit CRM
Other ways to arrive at Nutshell
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.