Migrate from Keap to Salesforce Sales Cloud

Keap Contacts with email activity but no closed Opportunity map to Salesforce Lead. Keap Contacts linked to a closed Invoice or a paid Order map to Salesforce Contact tied to an Account. We compute the split during migration using Keap's contact stage, tag membership, and order history. The original Keap contact record is preserved in a custom field keap_contact_id__c on both Lead and Contact for reconciliation.

Keap Company records map to Salesforce Account. The company name becomes Account Name, and the company phone becomes Account Phone. Keap allows a contact to have no company, but Salesforce requires a Contact to be attached to an Account. We create a default Account named 'Individual Contacts' for unassociated contacts during migration and flag them for the customer's admin to merge or re-parent post-migration.

Keap tags serve dual purposes: contact segmentation and automation triggers. We export all tags and map them based on usage. Tags that represent marketing segments or audience lists migrate to Salesforce Campaign membership (CampaignMember Status). Tags that represent contact attributes or sales territory flags migrate to a multi-select picklist custom field contacts_tag__c. The customer selects the strategy during scoping. Tags used as automation triggers are documented separately because Salesforce Flow handles automation logic natively.

Keap Opportunities map to Salesforce Opportunity. Stage names migrate from Keap to Salesforce StageName. We create a Salesforce Sales Process that matches the Keap pipeline stage order and probability percentages. Opportunity owner resolves by email match to Salesforce User. Any Opportunity with no owner email match goes to a reconciliation queue for the admin to assign.

Each Keap pipeline stage becomes a Salesforce StageName entry in the Sales Process. Stage probability percentages migrate from Keap to Salesforce StageProbability, rounded to the nearest integer. Closed-Won and Closed-Lost stages migrate with the corresponding status. Stage names are preserved as-is by default unless duplicates exist, in which case we prefix with the pipeline name.

Keap Invoice records (with line items, totals, status: draft/sent/paid/overdue) map to Salesforce Order if the destination org has Order Management enabled, or to a custom Invoice__c object with equivalent fields if not. Keap Invoice status maps to Order Status or a custom picklist field. The known Keap issue (knownissues.keap.com #3275175) where pipeline activity logs do not display invoice events means we query the invoice API endpoint directly rather than relying on deal activity logs to infer invoice records.

Keap product catalog items map to Salesforce Product2 records with Standard Price Book entries created during import. ProductCode maps from Keap SKU, and Name maps from Keap product name. Product images and advanced catalog metadata not available via Keap API are not migrated.

Keap Order records map to Salesforce Order when Order Management is enabled. Order headers, line items, payment status, and order dates migrate directly. If Order Management is not enabled in the destination org, we document the Order records as a separate import task post-migration or map them to a custom Order__c object.

Keap Tasks migrate to Salesforce Task with Subject, Status, Priority, Due Date, and Completion Date preserved. Keap task assignment migrates by resolving the Keap user ID to Salesforce OwnerId via email match. Tasks linked to contacts resolve the WhoId; tasks linked to opportunities resolve the WhatId.

Keap Notes associated with contacts or companies migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Lead, or Account. Note body content migrates as plain text. Note attachments migrate as separate ContentDocument records attached to the same parent.

Keap user accounts (name, email, role) map to Salesforce User records. We resolve users by email match. Any Keap user without a matching Salesforce User goes to a reconciliation queue for the admin to provision before record import resumes. Inactive Keap users map to inactive Salesforce Users to preserve assignment history.

Keap custom fields must first be discovered via the REST API /retrieveContactModel endpoint to retrieve field IDs. We then export field names, types, and values. Before writing to Salesforce, we pre-create matching custom fields on the Contact, Account, or Opportunity object using the appropriate Salesforce field type (Text, Number, Date, Picklist, Checkbox). Customer must pre-create any Salesforce custom fields they want populated if they require a specific field-level security configuration not achievable via API.

Keap campaign records with name, status, and recipient tag map to Salesforce Campaign. Recipient tag membership translates to CampaignMember records with Member Status. Email body content migrates as Campaign Description or HTML content in a ContentNote attached to the Campaign. Keap-hosted images and CDN assets are not migrated; we document the image URLs for manual re-hosting.

Keap Automation Sequences cannot be exported in structured form via API. The conditional logic, time delays, tag assignments, and email content are stored in a proprietary format. We export sequence names, step counts, and trigger conditions as a written inventory document. The customer's admin uses this document to rebuild sequences in Salesforce Flow, which is a separate rebuild engagement or internal admin task.

Keap landing pages and web forms cannot be exported via API. We document the URLs and form field structures for manual re-creation in Salesforce Web-to-Lead, Experience Cloud forms, or a third-party form tool. Any form submissions stored as contact records in Keap migrate as Contacts with a custom field capturing the original form source.