Migrate from Keap to Pipedrive

Keap Contact records map directly to Pipedrive Person. Standard fields (name, email, phone, address) map cleanly. Custom field values require that we first retrieve the contact model schema via Keap's REST /retrieveContactModel endpoint to resolve field IDs to labels, then write values to Pipedrive custom fields that the customer pre-creates in Pipedrive's UI or that we provision via Pipedrive API before the contact write phase. Keap contact tags become Pipedrive activity labels or custom multi-checkbox fields depending on the tag usage pattern identified during scoping.

Keap Company records map to Pipedrive Organization. The Company-to-Contact association is preserved by creating Organizations before People in migration order, then writing the Organization ID into the Person's org_id field during Person import. Company-level custom fields migrate to Organization custom fields using the same schema-discovery-then-write approach as Contacts.

Keap tags are both a segmentation tool and an automation trigger, and they organize into categories. We export all tags and map them based on usage context: tags used for contact classification become Pipedrive custom fields (multi-checkbox or single-select); tags used for activity-level notes become Pipedrive activity labels. Tag categories in Keap that represent groupings of related tags map to a custom field that we create in Pipedrive. The customer chooses the tag strategy during scoping based on how they use tags in Keap.

Keap Opportunities represent pipeline deals with stage, value, owner, expected close date, and associated Contact and Company. We map Opportunity stages to Pipedrive pipeline stages, creating new stages in Pipedrive's pipeline configuration before Deals import. The deal value (Weighted Value in Keap) maps to Pipedrive's weighted_value field. Expected close date maps to Pipedrive's close_date. Owner mapping resolves by email match against Pipedrive users. Note that Keap's known issue #3275175 means deal activity history does not display invoice events in the pipeline UI, so we query the invoice API endpoint directly rather than relying on deal activity logs.

Keap Invoices are invoice records with line items, totals, and payment status tied to a Contact. Pipedrive does not have a native invoice object on core plans. We have two options: map Keap invoice data to Pipedrive Products (for invoicing-as-product use cases) or export invoice records as a separate CSV deliverable for the customer to manage in a dedicated invoicing tool post-migration. The customer selects the strategy during scoping. Invoice status (draft, sent, paid) migrates as a custom field on the associated Person or Deal.

Keap Products (name, SKU, price, description) map directly to Pipedrive Products. Product images and advanced catalog features do not transfer. We export products before Deals so that Deal line items can reference valid Product IDs during import.

Keap Order records capture completed transactions with headers, line items, payment status, and order dates. Pipedrive does not have a native order object. We map order data to Pipedrive Activity notes attached to the associated Person, capturing order date, total amount, and payment status as structured note content. Order line items become a bulleted list within the Activity note.

Keap Tasks (subject, due date, assigned user, status, completion date) map to Pipedrive Activities of type Task. We resolve the assigned user by email match against Pipedrive users. Activity due dates and status values migrate directly. Keap tasks linked to Opportunities map to Pipedrive Activities attached to the corresponding Deal.

Keap Notes (free-text content, author, timestamp, associated Contact or Company) map to Pipedrive Notes attached to the corresponding Person or Organization. Author attribution and creation timestamp are preserved as note metadata.

Keap user accounts (name, email, role, permissions) map to Pipedrive Users. We resolve by email match. Users without a Pipedrive match go to a reconciliation queue for the customer's admin to provision before record import. Role mapping is documented for admin reference; Pipedrive role permissions are applied post-migration.

Keap automation sequences (time-delayed, tag-triggered email and task sequences) cannot be exported in structured form via API. We export the sequence names, step counts, and trigger conditions as a written inventory document for the customer to reference during manual rebuild in Pipedrive Workflows. Keap's tag-trigger logic maps loosely to Pipedrive's trigger-on-activity workflows, but the rebuild is custom work outside migration scope.