How to Migrate from ConvertKit to Sparkforge

This guide covers the ConvertKit-to-Sparkforge migration: visual automations, subscribers, forms, landing pages, broadcasts, and commerce. Plan to run both platforms in parallel until everything is verified.

What needs to migrate

1. Visual Automations
2. Subscribers (contacts)
3. Forms
4. Landing pages
5. Email broadcasts
6. Commerce (digital products and subscriptions)
7. Additional data (tags, custom fields, engagement)

Migrate visual automations

ConvertKit's Visual Automations become Workflows in Sparkforge. The capabilities are similar — triggers, actions, branching — but the build is manual.

Document the flow

For each visual automation, capture the entry trigger, the actions, the events, and the conditional branches. Screenshots are the fastest way to keep the flow accurate.

Rebuild in Sparkforge

1. Go to Automation > Workflows.
2. Click Create New Workflow.
3. Set the entry point — form submission, tag added, purchase made — to match ConvertKit.
4. Add the same actions and conditions (send email, wait, if/else).
5. Run a test contact through the workflow.

Migrate subscribers

Export from ConvertKit

1. Go to Subscribers > Grow.
2. Select all subscribers (confirm via the blue bar if over 30 selected).
3. Choose Bulk Actions > Export. ConvertKit emails the file to the account owner.

Import into Sparkforge

1. Go to Contacts > Import Contacts.
2. Upload the CSV.
3. Map First Name, Last Name, Email, and Tags.
4. Recreate ConvertKit's segments using Sparkforge's tags and smart lists.

Migrate forms

Document each ConvertKit form — fields, design, redirect URL, incentive email, reCAPTCHA settings, custom fields. In Sparkforge under Sites > Forms, click Create New Form and rebuild each one. Match field set, design, post-submit redirect, confirmation email, and tag application. Wire forms to the matching workflow. Submit a test entry to verify.

Migrate landing pages

Document each ConvertKit landing page — template, content, custom images, custom domain. In Sparkforge under Sites > Funnels/Websites, create a new landing page using a template that matches the layout. Rebuild content, embed your Sparkforge forms, and configure the same custom domain or subdomain.

Migrate email broadcasts

Document subject lines, content, and recipient segments for past ConvertKit broadcasts. In Sparkforge under Marketing > Email Campaigns, click Create New Campaign, rebuild the email, target by tag or segment, and send a test before scheduling.

Migrate commerce

For ConvertKit digital products and subscriptions, document pricing, fulfilment, and any associated automations. In Sparkforge under Sites > Order Forms, set up new product pages. Match pricing models — one-time, subscription, payment plan. Configure digital fulfilment so customers receive products automatically. Link the order form to a follow-up workflow. Run a test purchase end-to-end.

Export additional data

From ConvertKit, export the subscriber list (Subscribers > Grow > Export under Bulk Actions) and verify the CSV includes all fields, tags, engagement metrics, and custom fields. If you need any of that data inside Sparkforge, import it with the contacts and map custom fields accordingly.

Final checks and ongoing

• Cross-check contacts, tags, and segments in Sparkforge against the ConvertKit export.
• Run test contacts through every workflow.
• Train the team on Sparkforge — it covers more than ConvertKit, so workflows, CRM, and multi-channel comms are new ground.
• Keep the ConvertKit export as a backup for historical reference.