Migrate from Workbooks to Pipedrive

Workbooks Organisation records map directly to Pipedrive Organization. The Organisation Name maps to Organization name, and the Organisation's primary address fields map to address line 1, line 2, city, state, postal code, and country fields in Pipedrive. Industry classification, website, and annual revenue map to equivalent Organization fields. Any Organisation-level custom fields migrate as Organization custom fields created in Pipedrive before import. The Organisation-to-Person linkage is preserved as a Pipedrive Organization-Person relationship.

Workbooks Person records map to Pipedrive Person. The Person-Organisation link is preserved by resolving the Organisation lookup and creating a Pipedrive Person-Organization relationship during import. Name, email, phone, title, and address map directly. Marketing opt-in status from Workbooks Person maps to Pipedrive's email_status_cf or a custom field. Any Person-level custom fields require pre-creation in Pipedrive before migration.

Workbooks Opportunities map to Pipedrive Deals with the pipeline and stage assignment resolved during scoping. The Workbooks pipeline name becomes a Pipedrive pipeline, and each Workbooks stage maps to a Pipedrive stage in the same sequence. Stage probabilities migrate as percentage values against the corresponding Pipedrive stage. Expected Close Date and Opportunity value migrate as close_date and value fields. Owner assignment resolves by email match against Pipedrive Users.

Each Workbooks pipeline becomes a Pipedrive pipeline. Stage names and probabilities migrate to corresponding Pipedrive stage entries within the pipeline. If the customer has multiple pipelines in Workbooks (available on Business tier), each pipeline becomes a separate Pipedrive pipeline with its own stage set. The pipeline order and default flag are set during Pipedrive configuration before deals are imported.

Workbooks Quotations contain a header (related Organisation, owner, validity date) and line items (product, quantity, unit price, discount). The quotation header migrates as a Pipedrive Deal with a validity date stored in a custom field. Quotation line items migrate as Deal Products linked to the Deal. If the customer uses Pipedrive's Products feature, we create Product2 records and link them via Deal Product entries. Quotation status (Draft, Sent, Accepted, Lost) maps to a custom field or deal label. Note: Quotation and Invoice objects exist only on Workbooks CRM Business and Business Pro tiers; we confirm the source tier during scoping.

Workbooks Invoices (Business tier and above) contain header data, line items, payment status, and optional credit note associations. Pipedrive has no native Invoice object. We migrate invoice data as a Note attached to the related Organization or Deal, with invoice number, date, amount, status, and line item summary stored in structured fields within the Note body. PDF invoices stored as attachments against the Workbooks Invoice are downloaded separately and reattached to the Pipedrive Note as file attachments. Payment status is preserved in a custom field on the Note.

Workbooks Sales Orders and Purchase Orders are tied to an Organisation and quotation. Pipedrive has no native order object. We extract order header data (order number, date, status, related Organisation) and line items as a structured Note attached to the relevant Organisation. Any attached documents are downloaded and reattached to the Pipedrive Note. Order-to-invoice linkage is preserved as a text reference within the Note body. Customers requiring full order management in Pipedrive should consider the Pipedrive Invoices add-on or a third-party integration post-migration.

Workbooks Cases do not have a direct Pipedrive equivalent. Pipedrive has no native Cases object on any standard tier. We evaluate two migration paths during scoping: (1) Cases map to Pipedrive Activities (task type with subject, description, and due date) linked to the Organisation or Person, with case status and priority stored in custom fields; (2) Cases map to Notes attached to the Organisation with a structured template for case number, status, priority, and description. The customer's Pipedrive tier and use case determine which path applies. Pipedrive's Projects object is also available on Premium tier and can serve as a case tracking container if the customer licenses that tier.

Workbooks Lead records hold pre-conversion prospect data with lead source, status, rating, and assigned owner. We map Leads to Pipedrive's Lead inbox or directly to Person records depending on whether the customer intends to use Pipedrive's Lead qualification flow. If Pipedrive's Lead feature is active, Leads import as Pipedrive Leads with source and status preserved. If Leads are fully qualified in Workbooks before migration, they map to Person records with Organisation linkage. The original Workbooks Lead status is preserved in a custom field for audit.

Workbooks Activities (calls, emails, meetings, tasks) linked to an Organisation or Person migrate to Pipedrive Activities. Activity type maps to Pipedrive activity_type (call, email, meeting, task). Date, duration, subject, and description migrate directly. Owner assignment resolves by email against Pipedrive Users. Activity association links to the migrated Organisation or Person ID. Call disposition and duration are stored in custom fields if the customer requires that metadata in Pipedrive.

Workbooks Campaigns track marketing initiatives with associated leads and persons. Pipedrive has no native Campaign object. Campaign name, status, and start/end dates migrate as a Label on the associated Person records, or as a Note on the Organisation. Campaign membership data (which persons and leads were in which campaign) is preserved by applying the campaign name as a label to the relevant Person records. Marketing attribution data is preserved in a custom field on each Person.

Workbooks custom fields of types text, number, date, dropdown, and checkbox map to equivalent Pipedrive custom field types. We request a read-only Workbooks login and enumerate every custom field per object type before writing the migration spec, since Workbooks deployments vary significantly in which custom fields exist and what they are called. iFrame fields export as URL strings and map to Pipedrive text fields. File-upload fields require a separate binary extraction step with files reattached to the destination record. Multi-select checkbox fields in Workbooks map to Pipedrive multi-checkbox custom fields.