Migrate your Keap data

Contacts are the primary record in Keap. Standard fields (name, email, phone, address) map cleanly. We retrieve custom field IDs via the REST /retrieveContactModel endpoint and write values using the underscore-prefixed field names documented in Keap's API.

Keap's Company records store business-level data separate from Contact records. Standard fields map to the destination's Account/Company object. We preserve the Company-to-Contact association by creating the company first, then linking contacts at import time.

Tags in Keap are both a segmentation tool and an automation trigger. We export all tags and apply them as labels or custom properties in the destination. Where the destination uses a separate tagging object, we replicate the tag string values faithfully but flag that tag-based automation triggers will require re-implementation in the destination.

Opportunities represent pipeline deals with stage, value, owner, and expected close date. Keap's stage names are user-defined. We map stages to the destination's pipeline stages, creating new stages where the destination's schema requires them. Open invoices tied to an opportunity are preserved as line items in the imported deal record.

Keap's automation sequences — time-delayed, tag-triggered email and task sequences — cannot be exported in structured form via the API. We export the sequence names, step counts, and trigger conditions as documentation. Customers must rebuild sequences in the destination platform using its native automation builder.

Invoices are exportable via API. We pull invoice records with line items, totals, status (draft, sent, paid), and the associated contact. The known Keap issue (knownissues.keap.com #3275175) where pipeline activity does not show invoice activity lines means we retrieve invoices directly rather than inferring them from deal activity logs.

Keap's product catalog stores items with name, SKU, price, and description. We export products as items or products in the destination, mapping pricing and SKU fields directly. Product images and advanced pricing tiers may require manual re-upload.

Order records in Keap capture completed transactions linked to a contact and product. We export order headers, line items, payment status, and order dates. Order-level notes and internal annotations are included as comments or notes in the destination.

Tasks are exportable via API with subject, due date, assigned user, status, and completion date. Keap tasks linked to contacts or opportunities are imported as tasks or activities tied to the corresponding destination records.

Notes are associated with contacts or companies and contain free-text content plus author and timestamp. We import notes as notes or activity log entries, preserving the author and creation date. Notes attached to deleted contacts are imported with a placeholder reference.

Keap landing pages and web forms cannot be exported via API. We document the URLs and form field structures for manual re-creation in the destination. Forms built inside Keap that feed contacts into automations will need their tag-trigger logic rebuilt.

Keap user accounts include name, email, role, and permissions level. We export users as users or members in the destination, mapping role names to the nearest equivalent. API-level access credentials and OAuth tokens cannot be migrated.

Custom fields must first be created inside Keap before their API IDs become available. We discover custom field IDs via the REST contact model endpoint, then export field names, types, and values. Custom field definitions (not just values) require manual setup in the destination platform with matching field names and types.

Campaign records include name, status, and recipient tag or list. We export campaign metadata as a reference. Email body content can be exported via API, but HTML assets, images hosted on Keap's CDN, and tracking data require additional extraction steps and manual re-upload in the destination.