CRM migration
Field-level mapping, validation, and rollback between Combit CRM and Pipedrive. We move data and schema; workflows are rebuilt natively in Pipedrive.
Combit CRM
Source
Pipedrive
Destination
Compatibility
7 of 10
objects map 1:1 between Combit CRM and Pipedrive.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Combit CRM to Pipedrive is a cross-platform migration from a German-language, no-API, workflow-heavy system to a cloud-native, API-first, pipeline-centric CRM. Combit CRM has no publicly documented REST API, so we extract via direct database queries against on-premise deployments or via structured CSV exports from the cloud application, then transform German field names and picklist values to Pipedrive equivalents before loading through Pipedrive's REST API or CSV import. Pipedrive organizes data around Deals (Opportunities) linked to Persons and Organizations, with Activities as the primary history object. We map Combit's Address-to-Contact relationship to Pipedrive's address fields on Person, map Combit Deals to Pipedrive Deals with pipeline stage reconstruction, and map Projects to Pipedrive Projects (available on Advanced and higher tiers). Workflows, automations, and report definitions do not migrate; we deliver a written inventory of Combit workflows requiring rebuild in Pipedrive's Automation and Smart Campaigns tools.
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 Pipedrive, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Combit CRM
Addresses (Anschriften)
Pipedrive
Address fields on Person
1:manyCombit CRM stores addresses as separate records that can be linked to multiple contacts, supporting multiple locations per entity. Pipedrive stores addresses as fields on the Person object (address, address_subtext, address_lat, address_lng). We extract each Combit Address record with its type (billing, shipping, registered office), then write address values into the corresponding Pipedrive Person address fields. If a Combit contact has multiple addresses, we write the primary billing address to the Person fields and store secondary addresses as custom fields or notes.
Combit CRM
Contacts (Kontakte)
Pipedrive
Person
1:1Combit Contacts map directly to Pipedrive Persons. We preserve the contact's name fields (first_name, last_name), email (primary email field), phone, and any linked address reference. The original Combit contact ID migrates as a custom field for audit and cross-reference. Owner assignment resolves by matching the Combit Benutzer (user) email to a Pipedrive User.
Combit CRM
Companies (Firmen)
Pipedrive
Organization
1:1Combit Company records map to Pipedrive Organizations. Company name becomes the Organization name; address data from the linked Combit address migrates to the Organization's address fields. Organization is created before Person import so that the org_id lookup relationship is satisfied at Person insert time.
Combit CRM
Deals (Verkäufe/Geschäfte)
Pipedrive
Deal
1:1Combit Deals map to Pipedrive Deals with stage, value, expected close date, owner, and associated contact and company preserved. The Combit deal stage name translates to a Pipedrive pipeline stage. If Combit has multiple deal pipelines, we create corresponding Pipedrive pipelines (Advanced and higher) and map deal records to the appropriate pipeline by a pipeline identifier field in Combit. Custom fields on Combit Deals migrate to custom fields on Pipedrive Deals.
Combit CRM
Activities (Aktivitäten)
Pipedrive
Activity (call, email, meeting, task)
1:1Combit Activities (calls, meetings, tasks, notes) attached to contacts or projects map to Pipedrive Activities. We map the activity type, date, duration, and description. Call dispositions and outcomes from Combit migrate as custom fields on the Pipedrive Activity. Meeting location migrates to the Pipedrive Activity location field. Activities are linked to the target Person and Deal via activity_id resolution at load time.
Combit CRM
Projects (Projekte)
Pipedrive
Project
1:1Combit Projects map to Pipedrive Projects if the destination Pipedrive account is on Advanced plan or higher. Projects include associated dates, budgets, line items, and linked contacts. Pipedrive Projects support tasks, milestones, and deal associations. If the destination Pipedrive account is on Essential or Professional plan (which lacks native Projects), we map project records as custom Deal fields or as linked Notes with a project identifier tag, and flag this as a configuration constraint requiring plan upgrade or alternative handling.
Combit CRM
Custom Fields (Benutzerdefinierte Felder)
Pipedrive
Custom Fields
lossyCombit CRM allows user-defined fields across all objects with flexible data types. During discovery, we enumerate every custom field definition with its Combit label, data type, and picklist values (in German). We map each to an equivalent Pipedrive custom field: text fields to Pipedrive text, date fields to Pipedrive date, picklist fields to Pipedrive options (translating German labels to English). Multi-select picklists map to Pipedrive multi-select options. Custom fields are created in Pipedrive before any data import begins.
Combit CRM
Users (Benutzer/Vertriebspartner)
Pipedrive
User
1:1Combit user records (Benutzer and Vertriebspartner) define deal owners, contact owners, and activity owners. We extract all distinct user emails and names from Combit and match by email to Pipedrive User records. Owners without a matching Pipedrive User go to a reconciliation queue for the customer to provision before record import. Historical assignment is preserved as a custom field on migrated records.
Combit CRM
Attachments and Documents
Pipedrive
File attachments on Person, Organization, Deal
1:1Combit CRM can store file attachments on records. We extract attachments to a file store, preserve original filenames and record association, and create attachment links at the destination using Pipedrive's file attachment API. Attachments link to the migrated Person, Organization, or Deal record by ID.
Combit CRM
Tags and Categories (Kategorien)
Pipedrive
Custom Fields or Person/Org Tags
lossyCombit CRM categorical tags and classifications on records migrate to Pipedrive custom fields (if structured picklists) or to Pipedrive's native Person and Organization tagging feature. Multi-value tags from Combit consolidate into a compatible format. We agree on the strategy during scoping based on how Combit categories are used in reporting.
| Combit CRM | Pipedrive | Compatibility | |
|---|---|---|---|
| Addresses (Anschriften) | Address fields on Person1:many | Mapping required | |
| Contacts (Kontakte) | Person1:1 | Fully supported | |
| Companies (Firmen) | Organization1:1 | Fully supported | |
| Deals (Verkäufe/Geschäfte) | Deal1:1 | Mapping required | |
| Activities (Aktivitäten) | Activity (call, email, meeting, task)1:1 | Mapping required | |
| Projects (Projekte) | Project1:1 | Mapping required | |
| Custom Fields (Benutzerdefinierte Felder) | Custom Fieldslossy | Mapping required | |
| Users (Benutzer/Vertriebspartner) | User1:1 | Fully supported | |
| Attachments and Documents | File attachments on Person, Organization, Deal1:1 | Mapping required | |
| Tags and Categories (Kategorien) | Custom Fields or Person/Org Tagslossy | Mapping required |
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
Pipedrive gotchas
Custom field hash keys differ per account
Export access gated by visibility groups
Token-based API rate limits since December 2024
Sequences and Automations not exposed via REST API
Cost escalates via workflow caps and add-ons
Pair-specific challenges
Migration approach
Discovery and extraction method selection
We audit the Combit CRM environment to determine whether it is on-premise (requiring database extraction) or cloud (requiring CSV/Excel export), and to enumerate all objects, custom fields, picklist values, pipelines, and user accounts. We pair this with a bilingual review of the Combit admin panel to produce a complete English-German field glossary. We also confirm the target Pipedrive plan and identify any plan-gated features (notably Projects) that affect the migration scope. The discovery output is a written extraction specification and migration scope document.
Extraction via database or CSV
For on-premise Combit CRM, we negotiate read-only database credentials and run extraction queries directly against the Combit schema, documenting primary keys and foreign key relationships before writing transform logic. We validate row counts against Combit's reported record totals. For cloud Combit CRM, we use the application's built-in export functionality to generate structured CSV files covering Contacts, Companies, Deals, Activities, and Projects. If the built-in export has row or column limits, we negotiate additional export scope. All extracted files are stored in an encrypted staging environment and validated for completeness before transformation begins.
Schema design and German-to-English field mapping
We create the destination Pipedrive schema: custom fields on Person, Organization, and Deal (matching Combit custom field types); pipeline and stages (reconstructing Combit pipeline stages in Pipedrive); and user records (matched by email). The German field glossary produced during discovery guides every field mapping decision. Pipedrive schema is created via the API or manually before any data import. We validate with the customer's admin that field names, types, and picklist values are correct before proceeding.
Transform and relationship resolution
We run the transform layer against the extracted Combit data: translating German picklist values to English, mapping Combit object relationships to Pipedrive lookup IDs (resolving Person IDs for Activities, Organization IDs for Deals), applying the dedupe strategy (dedupe keys agreed in scoping), and assigning Pipedrive User IDs from the owner mapping. The transform layer emits a reconciliation report comparing record counts by object to the Combit source totals before any load call is made.
Production load in dependency order
We load records into Pipedrive in dependency order: Users (validated), Organizations (from Combit Companies), Persons (with org_id resolved), Deals (with person_id and org_id resolved), Activities (with person_id and deal_id resolved), Projects (if Advanced plan is confirmed), and attachments (linked by record ID after load). Each phase completes with a row-count reconciliation report before the next phase begins. We use Pipedrive's batch API endpoints for bulk inserts and apply exponential backoff on rate limit responses.
Cutover, validation, and workflow handoff
We freeze Combit CRM writes during cutover, run a final delta migration of records modified during the migration window, then mark Pipedrive as the system of record. We deliver a written inventory of all Combit workflow definitions and automation rules for the customer's admin to rebuild in Pipedrive Automation or Smart Campaigns. We support a one-week hypercare window for reconciliation issues. We do not rebuild Combit workflows as Pipedrive automations as part of the migration scope.
Platform deep dives
Combit CRM
Source
Strengths
Weaknesses
Pipedrive
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Pipedrive.
Object compatibility
3 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 Pipedrive migration scoping. Not seeing yours? Book a call.
Walk through your Combit CRM to Pipedrive 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 Pipedrive
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.