Migrate from Keap to Zoho CRM

Keap Contacts map directly to Zoho CRM Contacts. Standard fields (First Name, Last Name, Email, Phone, Address) map to Zoho's corresponding Contact fields. We retrieve custom field IDs from Keap's /retrieveContactModel endpoint and write values only after those fields are created in Zoho's UI. The Contact-to-Company link migrates as a Lookup relationship resolved after the Account import phase.

Keap Company records map to Zoho CRM Accounts. Company Name becomes Account Name, and the domain field maps to Website. We preserve the Company-to-Contact association by creating Accounts first and then resolving the Account Lookup during Contact import. Zoho's mandatory Account Name field is satisfied for every migrated Company record.

Keap tags serve as both segmentation labels and automation triggers. We export the full tag list and apply it in Zoho as either native Tags (visible in the Tags module and filterable across modules) or as a multi-select custom field on Contact, depending on whether your Zoho edition supports the Tags module. Tag counts per contact are preserved. Automation trigger tags are flagged in the export for your admin to use as a reference when rebuilding Keap sequences in Zoho Workflows.

Keap Opportunities map to Zoho CRM Deals. The Opportunity stage maps to a Zoho Deal Stage that we configure as a Sales Process before migration. Deal value, expected close date, owner, and associated Contact or Company migrate as Deal fields. We create new Deal stages in Zoho to match Keap stage names rather than forcing a rename on existing Zoho pipelines.

Keap automation sequences store conditional logic, time delays, tag assignments, and email content in a proprietary format inaccessible via API. We cannot migrate them as functional records. We export the sequence names, step counts, trigger conditions (tag-based, date-based, or field-change), and step descriptions as a structured inventory document. Your admin uses this document to rebuild sequences in Zoho Workflows and Zoho Campaigns. The migration itself proceeds without automation logic; rebuild is a post-migration activity.

Keap invoice records migrate to Zoho CRM Invoices with line items, totals, status (draft, sent, paid), and associated Contact. Due to Keap known issue #3275175 where pipeline activity history does not display invoice events, we query the invoice API endpoint directly rather than relying on pipeline activity logs. Invoice attachments migrate as file uploads in Zoho within the standard attachment limits.

Keap product catalog items (name, SKU, price, description) map to Zoho CRM Products. We map price from Keap's unit_price field to Zoho's List Price. Advanced fields such as product images and cost-basis data require a custom field in Zoho and must be pre-created before migration.

Keap order records (completed transactions linked to a Contact and Product) migrate to Zoho CRM Quotes or Purchase Orders depending on the order direction (incoming payment vs. outgoing vendor record). Order status and line items migrate as-is. Order-level notes and internal annotations require a custom text field in Zoho if preservation is required.

Keap tasks with subject, due date, assigned user, status, and completion date migrate as Zoho CRM Tasks linked to the parent Contact, Account, or Deal. Task ownership migrates by resolving the Keap user email to a Zoho User; any unresolved owners go to a reconciliation queue for your admin to provision before migration resumes.

Keap notes associated with Contacts or Companies migrate as Zoho CRM Notes with content, author, and creation timestamp preserved. Notes attached to multiple records in Keap generate separate Note records in Zoho linked individually. Note body content migrates as-is; HTML formatting inside notes is flattened to plain text.

Keap custom fields require creation in the application before their ID numbers are available via API. During discovery we retrieve the contact model schema from Keap's REST API to map field IDs to labels. Before migrating data into Zoho, we confirm that corresponding custom fields exist in Zoho's module layout. If a custom field does not exist in Zoho, we flag it for pre-creation and resume data migration after the schema is updated. Custom fields not pre-created will fail on import with a field-not-found error.