How to Migrate from Keap to Sparkforge

This guide walks the full Keap-to-Sparkforge migration: contacts, custom fields, pipelines, automations, landing pages, and calendars. Run both systems in parallel until everything is verified, then cancel Keap.

Before you start

Inventory what you actually use in Keap. List every active automation, pipeline, custom field, tag, form, and landing page. Pull screenshots of automation flows — Sparkforge can match the logic, but you have to rebuild it manually.

Decide what migrates first. Contacts and pipelines usually go before automations, since automations need real data to test against.

Export everything from Keap and store the files somewhere safe before you change anything live.

Migrate contacts and custom fields

Export from Keap

1. Go to Contacts > People in Keap.
2. Select the contacts to export, or use Select All.
3. Click Export and download the CSV. For exports over 1,000 contacts, Keap emails you a download link.
4. Document each custom field — types and where they live. Custom fields are recreated manually in Sparkforge.
5. Screenshot or document every automation rule, trigger, and action.

Import into Sparkforge

1. In Sparkforge, go to Contacts > Import Contacts and upload the Keap CSV.
2. Map Keap fields to Sparkforge fields during import.
3. Recreate custom fields under Settings > Custom Fields, matching field types.
4. Recreate any tags from Keap so contact segmentation still works.

Migrate pipelines and deals

List every active pipeline in Keap, including stages and the deals attached. Note deal value, stage, and the associated contact.

In Sparkforge, go to Opportunities > Pipelines and recreate each pipeline with matching stages. Sparkforge does not import Keap deals directly — recreate each deal manually, matching stage and contact.

Migrate automations

Document every active Keap automation: triggers, sequences, tags, actions. Screenshots help.

In Sparkforge, go to Automation > Workflows and rebuild each one using Sparkforge triggers, conditions, and actions. The logic is similar — branch points, waits, send-email actions, tag changes — but the UI is different.

Test every workflow with a real test contact before activating.

Migrate landing pages and forms

Use Sparkforge's funnel and website builder to rebuild each Keap landing page. Match the design and copy as closely as you need.

Recreate Keap public forms under Funnels & Websites > Forms. Set form actions so submissions trigger the right tag or workflow — the same way Keap was wired up.

Migrate appointments and calendars

List every Keap appointment type with its duration, availability, reminders, and integrations. Recreate them in Sparkforge under Calendars > Appointment Types.

Connect Google or Outlook calendars to Sparkforge so existing appointments sync and you don't double-book.

Final checks

• Cross-check contacts, pipelines, automations, and pages against the Keap exports.
• Run test contacts through every workflow to confirm triggers, emails, and tag changes fire correctly.
• Train your team on Sparkforge before they have to use it live.

Decommission Keap

Run Keap and Sparkforge in parallel for a transition window. Once Sparkforge is operational and verified, back up Keap one last time and cancel the subscription through Keap's process.