CRM migration

Migrate from Combit CRM to Pipedrive

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

Combit CRM logo

Combit CRM

Source

Pipedrive

Destination

Pipedrive logo

Compatibility

70%

7 of 10

objects map 1:1 between Combit CRM and Pipedrive.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Pipedrive logo

Pipedrive

What's pulling them in

  • Clean drag-and-drop pipeline interface with minimal learning curve, making it approachable for small sales teams without dedicated CRM admins.
  • Visual deal tracking keeps reps focused on next actions — activities, calls, and follow-up tasks surface directly in the pipeline view.
  • Strong integrations via Zapier and native marketplace apps let teams wire Pipedrive into Calendly, ActiveCampaign, and similar sales-stack tools.
  • Mobile apps for iOS and Android keep field reps connected to deals, contacts, and tasks without a desktop session.
  • Reputation and review volume — over 3,000 verified reviews across G2 and Capterra — signal reliability for teams evaluating CRM options.

Object mapping

How Combit CRM objects map to Pipedrive

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)

maps to

Pipedrive

Address fields on Person

1:many
Mapping required

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

maps to

Pipedrive

Person

1:1
Fully supported

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

maps to

Pipedrive

Organization

1:1
Fully supported

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

maps to

Pipedrive

Deal

1:1
Mapping required

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

maps to

Pipedrive

Activity (call, email, meeting, task)

1:1
Mapping required

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

maps to

Pipedrive

Project

1:1
Mapping required

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

maps to

Pipedrive

Custom Fields

lossy
Mapping required

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

maps to

Pipedrive

User

1:1
Fully supported

Combit 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

maps to

Pipedrive

File attachments on Person, Organization, Deal

1:1
Mapping required

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

maps to

Pipedrive

Custom Fields or Person/Org Tags

lossy
Mapping required

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

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

Pipedrive logo

Pipedrive gotchas

High

Custom field hash keys differ per account

High

Export access gated by visibility groups

Medium

Token-based API rate limits since December 2024

Medium

Sequences and Automations not exposed via REST API

Low

Cost escalates via workflow caps and add-ons

Pair-specific challenges

  • No REST API means extraction is database or CSV only

    Combit CRM has no publicly documented REST API. We cannot run API-based migration jobs against it. We extract via direct database access for on-premise deployments (negotiating read-only database credentials during scoping) or via structured CSV/Excel exports from the cloud application. If database access is unavailable and the application export is limited in scope, we negotiate a custom export specification with the customer, validate row counts against Combit's reported totals, and handle any partial exports as a risk item. This extraction constraint adds preparation time compared to migrations from API-first platforms.

  • German field names and picklist values require translation

    Combit CRM's entire admin panel, field labels, and picklist values are in German. All custom field definitions, workflow names, stage names, and picklist values must be translated during the mapping phase before any Pipedrive schema is created. We engage a bilingual analyst during discovery to walk the Combit admin panel and produce an English glossary of every field and option. Any mis-translation during mapping results in incorrect Pipedrive fields or rejected import rows, so we validate the translated glossary with the customer's admin before writing transform logic.

  • Projects require Pipedrive Advanced plan or higher

    Combit CRM has a native Project object that can span multiple contacts and activities. Pipedrive's Projects feature is only available on Advanced plan ($29/user/month) and higher. If the customer's destination Pipedrive account is on Essential ($12/user/month) or Professional ($19/user/month), we cannot create native Pipedrive Projects. We flag this during scoping and recommend either upgrading the Pipedrive plan or mapping Combit Projects to a custom Deal field with project metadata stored as linked notes. The customer decides before migration begins.

  • Duplicate records require dedupe strategy at load time

    Pipedrive's import tools and API can create duplicate Persons, Organizations, or Deals if the same record appears in Combit data multiple times. We define dedupe keys during scoping (typically email for Persons, domain for Organizations, deal name plus close date for Deals) and run dedupe logic before insert. Pipedrive's native duplicate detection is limited to manual import review; we implement server-side dedupe as part of the transform layer to ensure clean load without relying on post-import manual review.

  • Activity timelines are linked by relationship, not by flat import

    Combit Activities are attached to contacts, addresses, or projects with their own IDs. Pipedrive Activities must be linked to a Person or Deal by ID at insert time. If the parent Person or Deal does not yet exist in Pipedrive at the time of activity import, the activity link breaks. We sequence migrations to ensure all Persons and Organizations are loaded before Activities, with parent-record ID resolution happening during the transform phase before any activity insert call is made.

Migration approach

Six steps for a successful Combit CRM to Pipedrive data migration

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

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

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

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

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

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

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

Pipedrive

Destination

Strengths

  • Intuitive drag-and-drop pipeline that sales reps actually use without resistance or training overhead.
  • Per-seat unlimited-deals model on all tiers — reps cannot be blocked from logging activity.
  • Active marketplace with 400+ integrations and a documented REST API with OpenAPI 3 specs.
  • Mobile apps with offline access, call logging, and calendar sync keep field teams operational.
  • Strong focus on sales activity tracking — next-action reminders and follow-up scheduling are first-class features.

Weaknesses

  • No custom objects — teams needing non-standard data structures must work around the four standard entity types.
  • Workflow automation limits by tier (30, 60, 90 active workflows) force upgrades as processes grow.
  • No free permanent plan — teams evaluating fit must commit to a trial without a freemium option.
  • Limited advanced reporting and custom dashboard capabilities compared to HubSpot or Salesforce.
  • Export permissions are gated by visibility groups, meaning data scoping must account for who can see what before migration.

Complexity grading

How hard is this migration?

Standard CRM migration. 3 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 Pipedrive.

  • Object compatibility

    B

    3 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 Pipedrive 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 Pipedrive data migrations

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

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 10,000 contacts and 2,000 deals with database access and a clean field mapping. Migrations requiring CSV-only extraction (when database access is unavailable), large project records, extensive custom field sets, or multiple address-to-contact relationship resolution move to seven to ten weeks because of extraction preparation and validation rounds.

Adjacent paths

Related migrations to explore

Ready when you are

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