Migrate from Keap to HighLevel

Keap Contacts map to GoHighLevel Contacts with all standard fields (name, email, phone, address) transferring directly. Custom field values require pre-creation of Contact custom fields in GHL Settings > Custom Fields before import. Keap's tag associations export separately and must be applied as tag labels in GHL after the contact record exists. We batch contacts in groups of 500 per import cycle to stay within GoHighLevel's import throttling.

Keap Company records map to GoHighLevel Companies with business name, domain, phone, and address fields transferring directly. The Company-to-Contact association is preserved by linking the GHL Contact to the parent GHL Company record via the Contact's Company field. If a Contact in Keap is associated with a Company, we create the Company record first so the lookup relationship is satisfied at Contact import time.

Keap tags require reconstruction in GoHighLevel because they carry business logic (segmentation, automation triggers) that is architecture-dependent. We export all tag names and tag-to-contact associations from Keap, then create the equivalent tags in GHL before importing contacts. Contact tag associations import via GHL's bulk import with tag assignment. The customer reviews the final tag taxonomy post-migration to ensure the rebuilt tag set reflects the original segmentation logic.

Keap Opportunities (pipeline deals) map to GoHighLevel Opportunities with stage, monetary value, owner, expected close date, and associated contact transferring directly. Keap stage names are user-defined and map to GHL pipeline stage names that we create during pipeline setup. The opportunity-contact association resolves via email match against the imported contact records.

Each Keap pipeline becomes a GHL Pipeline with stages recreated in the same order. Stage probability percentages from Keap transfer to GHL stage probability values. GHL allows multiple pipelines per workspace, which matches Keap's multi-pipeline capability for businesses using separate pipelines for different service lines.

Keap invoice records (with line items, totals, status, and associated contact) map to GoHighLevel Invoices. Keap's known issue (knownissues.keap.com #3275175) where pipeline activity history does not display invoice events does not affect our export — we query the invoice API endpoint directly. Invoice PDFs are not migratable via API and require manual upload or re-creation in GHL's document storage.

Keap product catalog items (name, SKU, price, description) map to GoHighLevel Products. Product images and advanced catalog metadata are not accessible via Keap API and require manual re-entry in GHL. SKU values serve as the dedupe key during import to prevent duplicate products on re-run.

Keap order records (header, line items, payment status, order date, linked contact) map to GoHighLevel Orders. Order-to-product linkage resolves via SKU match against imported products. Order notes and internal annotations migrate as order-level notes in GHL.

Keap tasks (subject, due date, assigned user, status, completion date) map to GoHighLevel Tasks linked to the corresponding Contact record. Task assignment resolves by matching the Keap owner's email address against GHL user accounts. Completed tasks preserve their completion timestamp in GHL's status and date fields.

Keap notes associated with contacts or companies migrate to GHL Notes attached to the parent Contact or Company record. Note content, author, and creation timestamp transfer directly. Notes linked to opportunities attach to the corresponding GHL Opportunity.

Keap user accounts (name, email, role, permissions) map to GHL user accounts. We match by email address during migration. If a Keap user has no corresponding GHL user account, they enter a reconciliation queue for the customer's admin to provision before activity and task imports proceed.