CRM migration
Field-level mapping, validation, and rollback between Combit CRM and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Combit CRM
Source
monday CRM
Destination
Compatibility
7 of 10
objects map 1:1 between Combit CRM and monday CRM.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Combit CRM to Monday.com CRM is a shift from a database-centric, German-language platform with no REST API to a multilingual board-based CRM with a documented REST API. Combit CRM organizes data around Addresses (Anschriften), Contacts (Kontakte), Companies (Firmen), Projects (Projekte), Activities (Aktivitäten), and Deals (Verkäufe). We extract via direct database access or structured CSV exports (depending on deployment type), translate all German field names and picklist values during the transform phase, and load into Monday.com CRM using the REST API with batch chunking and parent-record lookup resolution. Monday.com's board-based data model differs fundamentally from Combit's relational model—boards replace pipelines, columns replace field types, and items replace records—which requires schema redesign during scoping rather than a literal 1:1 field copy. Workflows and process automations do not migrate; we deliver a written map of every Combit workflow requiring rebuild as a Monday automation recipe.
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 monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Combit CRM
Address (Anschrift)
monday CRM
Address columns or linked Address Board
1:1Combit CRM stores addresses as separate records that can be linked to multiple contacts. We map address fields (street, city, postal code, country) to Monday.com CRM's built-in Address column type on the People board, or to a linked Address board if the address needs to be reusable across multiple Organizations. We preserve the address-to-contact relationship using Monday's Connect Boards column type with Item linking.
Combit CRM
Contact (Kontakt)
monday CRM
Person (People board item)
1:1Combit CRM Contacts map to Monday.com CRM People board items. We preserve name, email, phone, job title, and the link to the parent Address record. Monday.com CRM People board includes native email, phone, and location fields plus custom columns for any Combit custom field values. We resolve the parent Organization lookup by matching the Contact's company association to a Monday.com Organization item before insert.
Combit CRM
Company (Firma)
monday CRM
Organization (Organizations board item)
1:1Combit CRM Companies map to Monday.com CRM Organizations. The Organization is created first in the migration sequence so that Contacts can reference it via the Organization column. We preserve company name, website, industry, and any custom fields as custom columns on the Organizations board. Industry values require value mapping if Combit used German industry names.
Combit CRM
Deal (Verkauf/Geschäft)
monday CRM
Deal (CRM Deals board item)
1:1Combit CRM Deals map to Monday.com CRM Deals. We map deal name, value, stage, expected close date, owner, and associated Contact/Company links. Monday.com CRM's deal pipeline stages (New, Discovery, Proposal, Negotiation, Won, Lost by default) require stage name mapping from Combit's German stage labels. Deal value migrates as a Number or Currency column. Owner assignment uses Monday's Person column.
Combit CRM
Project (Projekt)
monday CRM
Linked Board or Group within Organization
1:manyCombit CRM Projects can span multiple contacts and activities. Monday.com does not have a native Project object in CRM—the customer's choice is to map Projects to a linked Board with Items representing project tasks, or to use Groups within the Organization board. We document both approaches during scoping and the customer selects. Project budgets, dates, and status migrate as columns on the selected structure.
Combit CRM
Activity (Aktivität)
monday CRM
Update or Activity log column
1:1Combit CRM Activities (calls, meetings, tasks, notes) map to Monday.com Updates on the relevant Person, Organization, or Deal item. We preserve activity type, date, duration, and description. Call and meeting activities with attendees map to Update mentions linking the relevant People items. Tasks with due dates map to the Due Date column on the item. Notes migrate as Updates with the note content preserved.
Combit CRM
Custom Field (Benutzerdefinierte Felder)
monday CRM
Custom Column (various types)
lossyCombit CRM allows extensive user-defined fields across all objects. We identify every custom field definition during discovery, translate the German field labels to English during the mapping phase, map the data type to the closest Monday.com column type (Text, Number, Date, Dropdown, Checkbox, etc.), and flag any multi-select or multi-reference fields that require special handling as Tags or Connect Boards columns.
Combit CRM
User (Benutzer/Vertriebspartner)
monday CRM
User
1:1Combit CRM Users map to Monday.com User accounts. We resolve by email match. Any Combit user without a matching Monday.com User account goes to a reconciliation queue for the customer to provision before record import resumes. Owner assignment on Deals and Activities uses Monday's Person column pointing to the User.
Combit CRM
Attachment (Anhang)
monday CRM
File
1:1Combit CRM file attachments extract to a file store with original filenames preserved. We upload files via Monday.com's file upload API and link them to the relevant Person, Organization, or Deal item using Monday's file upload capability. Files without a clear parent record are held in a reconciliation queue for manual assignment.
Combit CRM
Tag / Category (Kategorie)
monday CRM
Tag or Label column
lossyCombit CRM categorical tags map to Monday.com Tags on the relevant item, or to a Dropdown column if the customer prefers structured values. Multi-value tags consolidate into comma-separated values in a Text column or use Monday's Tag column type. We document the tag strategy during scoping.
| Combit CRM | monday CRM | Compatibility | |
|---|---|---|---|
| Address (Anschrift) | Address columns or linked Address Board1:1 | Fully supported | |
| Contact (Kontakt) | Person (People board item)1:1 | Fully supported | |
| Company (Firma) | Organization (Organizations board item)1:1 | Fully supported | |
| Deal (Verkauf/Geschäft) | Deal (CRM Deals board item)1:1 | Fully supported | |
| Project (Projekt) | Linked Board or Group within Organization1:many | Fully supported | |
| Activity (Aktivität) | Update or Activity log column1:1 | Fully supported | |
| Custom Field (Benutzerdefinierte Felder) | Custom Column (various types)lossy | Fully supported | |
| User (Benutzer/Vertriebspartner) | User1:1 | Fully supported | |
| Attachment (Anhang) | File1:1 | Fully supported | |
| Tag / Category (Kategorie) | Tag or Label columnlossy | 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
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and German field translation
We conduct discovery with the customer's German-speaking contacts or a bilingual analyst to inventory all Combit CRM objects (Addresses, Contacts, Companies, Projects, Activities, Deals), custom fields, picklist values, pipeline stages, and workflow definitions. All German field names and values are captured, translated to English, and added to the mapping document. We also confirm the Combit CRM deployment type (on-premise database or cloud export) and negotiate access credentials. The discovery output is a written migration scope with the full English-translated field inventory and Monday.com board and column design.
Monday.com CRM schema design
We design the Monday.com CRM structure based on the migrated scope: an Organizations board (from Combit Companies), a People board (from Combit Contacts with Address fields or a linked Address board), a Deals board (from Combit Deals with pipeline stages mapped to Monday status columns), and any linked Project boards. We create custom columns on each board to receive Combit custom field values, configure Connect Boards columns for Organization-People and Deal-Organization relationships, and set up User accounts matching the Combit user roster. Schema is configured in a Monday.com test workspace first for customer review.
Data extraction and transform
We extract data from Combit CRM via direct database access (on-premise) or structured CSV/Excel export (cloud). The extraction targets all Addresses, Contacts, Companies, Deals, Activities, Attachments, Tags, and custom field values. During transform, we apply the field mapping (with German-to-English translation), resolve the parent record lookups (Contact-to-Address, Contact-to-Company, Deal-to-Contact), and build the crosswalk table for Monday item IDs. Attachments are extracted to a file store with original filenames preserved. We run a data quality check to flag duplicates, blank required fields, and date format inconsistencies before loading.
Sandbox migration and reconciliation
We run a full migration into a Monday.com test workspace using production-like data volume. The customer reviews the resulting Organizations, People, and Deals boards, spot-checks 25-50 records against the Combit source, and validates that Connect Board links resolve correctly. We correct any mapping errors (wrong column type, missing picklist value, incorrect relationship) in the transform logic and re-run. Sign-off on the sandbox migration gates production migration.
Production migration in dependency order
We run production migration in dependency order: Users (validated against Monday accounts), Organizations (first because People and Deals reference them), People (with Organization ID resolved from the crosswalk table), Deals (with Person and Organization IDs resolved), Activity history (as Updates on the relevant People and Organization items), Attachments (uploaded and linked to items), Tags (applied to items), and custom field values (populated in custom columns). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and workflow handoff
We freeze Combit CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Monday.com CRM as the system of record. We validate record counts, spot-check relationships (Connect Board links, Person-Organization associations), and verify that Deal pipeline stage distribution matches Combit source totals. We deliver the Combit workflow and automation inventory as a written document for the customer's admin to rebuild as Monday automation recipes. We do not rebuild Combit workflows as Monday automations inside the migration scope.
Platform deep dives
Combit CRM
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Combit CRM and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Combit CRM and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Combit CRM and monday CRM.
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 monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Combit CRM to monday CRM 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 monday CRM
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.