Migrate from Teamleader to Pipedrive

Teamleader Contact records map to Pipedrive Person. We extract first_name, last_name, email, phone, mobile_phone, website, postal_address, and custom field values from the contact context. Teamleader's linked Company association maps to a Pipedrive Organization on the Person record via the org_id field. Dedupe key is email address for active contacts. Contacts without an email are imported with a generated placeholder and flagged for manual verification.

Teamleader Company records map to Pipedrive Organization. We extract company_name, vat_number, website, address fields, and custom field values from the company context. Organizations are imported before Persons so that the org_id reference is satisfied at the moment of Person insert. Companies without a linked Contact still import as standalone Organizations and are flagged for relationship assignment post-migration.

Teamleader Deal records map to Pipedrive Opportunity. The deal title becomes the Opportunity title, the Teamleader pipeline and stage map to a Pipedrive Pipeline and Stage. We resolve the linked Contact (as Person) and Company (as Organization) at migration time via email and domain lookup, then assign the resolved Person/org IDs. Custom fields on Deals use the deal context and migrate to Pipedrive custom fields on the Opportunity entity.

Each Teamleader pipeline's stages map to Pipedrive Pipeline stages. We configure the Pipedrive Pipeline structure (stage names, probabilities, and ordering) to mirror the Teamleader pipeline before importing any Opportunities. Probability percentages are rounded to Pipedrive's supported increments. Closed-Lost and Closed-Won stage flags transfer as Stage property values rather than as separate field values.

Teamleader pipelines (1 on SMART, 2 on GROW, unlimited on FLOW) map to Pipedrive Pipelines. We pre-create the Pipedrive Pipelines during schema setup so that Deals import into the correct pipeline from the first record. If the customer uses multiple Teamleader pipelines for different business lines, each maps to a separate Pipedrive Pipeline for full visual separation.

Teamleader Product catalog items map to Pipedrive Products. We extract product_code (SKU), name, description, prices, and unit. Products are imported before any Deal/Opportunity line items so that the product_id reference resolves during import. Products without a price are imported with a flag for pricing assignment before deals are imported.

Teamleader Invoices map to Pipedrive Invoices on the Professional plan and above. We preserve invoice header data (invoice number, issue date, due date, line items, tax rates, payment status) but flag that QR-code payment state, automatic reminder triggers, and overdue flags do not transfer because they are tied to Teamleader's payment processing system. Invoices on lower Pipedrive plans migrate as custom Deal fields with invoice reference numbers, and the customer sets up Xero or QuickBooks integration post-migration for billing continuity.

Teamleader Subscriptions (recurring billing relationships) have no direct Pipedrive equivalent. We import Subscription records as Deals with a custom field subscription_id__c and subscription_period__c, and a custom checkbox subscription_active__c. The customer decides whether Pipedrive's native subscription handling or an external billing tool (Stripe, Chargebee, or the Xero/QuickBooks integration) manages recurring billing post-migration.

Teamleader Projects have no native Pipedrive equivalent. Projects migrate as Deals with a custom field project_id__c, and Project Milestones migrate as Tasks linked to the Deal with a custom field milestone_id__c and due_date preserved. If the customer licenses Pipedrive's Projects add-on, we map Projects directly to Pipedrive Projects and Milestones to Project Tasks. The Projects add-on decision is made during scoping.

Teamleader Milestones under Projects migrate as Pipedrive Tasks linked to the parent Deal (if using Deal-based mapping) or Project Task (if using the Projects add-on). We preserve milestone title, due date, budget hours, and custom field values. Task type is set to milestone and the linked Deal or Project ID resolves at migration time. Budget hours do not transfer as Pipedrive-native fields and are stored in a custom number field.

Teamleader Tickets (customer support requests) have no direct Pipedrive object. We export Ticket records as a structured CSV during scoping, preserving ticket ID, subject, status, priority, linked Company/Contact, assignee, and conversation history. The customer chooses the destination: Pipedrive's native Cases (Service Cloud add-on), a ticketing tool (Zendesk, Freshdesk), or a shared Notion/Linear workspace. We do not force Tickets into Pipedrive's CRM objects as a workaround.

Teamleader Quotations (proposal objects with expiry dates and line items) migrate to Pipedrive Deals with a custom field quotation_id__c and line items preserved as Deal Product entries. If the customer is on Pipedrive's Professional plan or above, Quotations map to Pipedrive's native Products & Quotes feature. Margin calculation and expiry date logic from Teamleader GROW/FLOW tiers map to custom fields for the customer's admin to configure in Pipedrive.