Migrate from Keap to Nutshell

Keap Contacts map to Nutshell Persons, which are standalone contact records without mandatory company linkage. Where a Keap Contact has an associated Company record, we create the Nutshell Company (Account) first and then link the Person to it via the companyId field during Person import. Standard fields (name, email, phone, address) map directly. Custom field values are resolved using the Keap contact model schema endpoint before writing, ensuring field IDs resolve to correct values at migration time.

Keap Company records map to Nutshell Companies. The Company-to-Person association is preserved as a Person-Company link in Nutshell. Company-level standard fields (name, website, phone, address) map cleanly. Companies without any linked Contacts are imported as standalone Company records for later association.

Keap tags serve dual roles: contact classification and automation trigger definition. We export all tags and import them into Nutshell as Tags attached to the Person record. The tag-trigger automation context cannot be carried over (automation sequences do not export), so the tag inventory is preserved as labels for segmentation purposes only. Customers choose during scoping whether tags import as Nutshell native Tags or as a comma-delimited custom property string for reporting compatibility.

Keap Opportunities map to Nutshell Deals with stage, value, owner, and expected close date. Keap's user-defined stage names map to Nutshell pipeline stages, creating new stages in Nutshell's pipeline if the source stage names do not already exist in the destination account. We preserve deal value and expected close date as native Deal fields. The pipeline name in Keap becomes the pipeline name in Nutshell.

Keap user accounts (name, email, role) map to Nutshell Users by email match. Any Keap user without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Deals, Tasks, and Notes resolves via the User mapping table created during this phase.

Keap Tasks export with subject, due date, assigned user, status, and completion date. They import to Nutshell as Tasks linked to the corresponding Person or Deal via the PersonId and relatedId fields. Keap tasks with no associated contact or deal are imported as standalone Nutshell tasks. Completion status and timestamps are preserved. Task priority maps from Keap priority values to Nutshell's task priority scale.

Keap Notes (free-text content with author and creation timestamp) map to Nutshell Notes attached to Person, Company, or Deal records. Note body content migrates as plain text. Author and creation date are preserved as metadata fields. If the author is not a resolved Nutshell User, the note is attached without an assigned owner.

Keap custom field values export via the REST API after resolving field IDs from the contact model endpoint. Nutshell stores custom fields within a customFields dictionary on Person, Company, or Deal records using the field name as the key. We create the destination custom field in Nutshell by name before writing values, handling text, number, date, and currency types as supported by Nutshell's custom field schema. Note: Keap custom fields must be created inside Keap before their IDs become available via API — we apply the same discovery-then-export pattern in reverse for the destination.

Keap Invoice records (line items, totals, status, contact) do not have a native Nutshell equivalent object. We export invoice metadata as structured notes attached to the Person record, preserving invoice number, total amount, status, and date. Line item detail migrates as note body content. The known Keap issue (#3275175) where pipeline activity history does not display invoice events means we query the invoice API endpoint directly rather than relying on deal activity logs to capture this data.

Keap Products (name, SKU, price, description) map to Nutshell Products. ProductCode from Keap maps to Nutshell Product code; price maps to unit_price. We create the Product records before any associated Order or Invoice data to satisfy referential integrity. Product images and advanced attributes not supported by Nutshell's Product object are noted for manual handling.