Migrate from Keap to Twenty CRM

Keap Contacts map directly to Twenty Persons. Standard fields (name, email, phone, address) migrate as typed fields on the Person object. The Keap contact's associated Company ID maps to the Twenty Person's companyId field, which references a Company record created first during migration. We resolve the Company lookup at migration time to avoid orphaned Persons.

Keap Company records map to Twenty Company objects. Company name becomes displayName, domain becomes websiteUrl. We import Companies before Persons so that the Person-to-Company relationship is satisfied at insert time. Keap Company records with no linked contacts are preserved as standalone Companies in Twenty.

Keap tags serve dual purposes: contact segmentation and automation triggers. We export all tags and map them as Labels on the Person record in Twenty, which provides visibility into the original tag assignments. For tags carrying business-critical classification (such as customer tier, lead source, or product interest), we recommend creating a multi-select picklist custom field on the Person object and mapping tags to that field. The customer decides during scoping which tag strategy applies. Automation-trigger tags do not migrate as triggers; they are preserved as data for manual workflow reconstruction.

Keap Opportunities map to Twenty Opportunities with stage, value, owner, and expected close date. Keap stage names are user-defined; we map each to a Twenty Opportunity stage, creating new stages in Twenty's pipeline settings as needed. Opportunity value maps to the amount field, and the linked Contact and Company map to the Twenty Person and Company lookups.

Each Keap pipeline becomes a Twenty pipeline. Keap stage names, probabilities, and ordering migrate as stage definitions in Twenty's pipeline configuration. The customer reviews and approves stage mapping during the discovery phase before any data moves.

Keap invoices map to a Twenty Custom Object named Invoice, created in Settings > Data Model before migration. Invoice fields (number, date, total, status) map to custom fields on the object. We use the Keap invoice API endpoint directly rather than relying on pipeline activity logs due to the known Keap issue where invoice events do not appear in deal activity history (knownissues.keap.com #3275175). Line items migrate as JSON in a custom field or as related records if the customer prefers a separate line-item object.

Keap product catalog items (name, SKU, price, description) map to a Twenty Custom Object named Product. We create the object and all fields via Twenty's /metadata GraphQL API before import. Product images and advanced catalog attributes are not included in the standard export; we document these for manual re-entry.

Keap order records map to a Twenty Custom Object named Order, linked to the Person (customer) and Product records. Order headers, line items, payment status, and order dates migrate to custom fields. Order-level notes and internal annotations migrate as Note records linked to the Order. We pull orders via the Keap order API endpoint.

Keap tasks (subject, due date, assigned user, status, completion date) map to Twenty Tasks linked to the corresponding Person or Opportunity. We resolve the assigned user by email match against the Twenty workspace members provisioned before migration.

Keap notes associated with contacts or companies migrate as Twenty Notes linked to the Person or Company record. Note body, author, and creation timestamp preserve. We set the createdAt timestamp to match the original Keap creation date.

Keap user accounts (name, email, role) map to Twenty Workspace Members. We resolve by email match. Any Keap user without a matching Twenty account goes to a reconciliation queue for the customer to provision before record import resumes.

Keap automation sequences cannot be exported via API. We export sequence names and step counts as a written inventory delivered to the customer. The customer rebuilds sequences in Twenty's workflow builder using the inventory as a reference. This is the highest-effort rebuild item in any Keap migration.