ConvertKit to Stack

Welcome to your comprehensive guide for migrating from ConvertKit to Stack. This guide will assist you in transferring your email marketing, subscriber management, and automation workflows smoothly, while taking advantage of Stack’s integrated CRM and advanced automation features.

Important Components to Migrate

Ensure you migrate all the following components when switching from ConvertKit to Stack:

1. Visual Automations
2. Subscribers (Contacts)
3. Forms
4. Landing Pages
5. Email Broadcasts
6. Commerce
7. Additional Data

Migrate Visual Automations

ConvertKit’s Visual Automations can be recreated in Stack using the Workflows feature.

Step 1: Document Visual Automations

• List Automations: Document each automation, including triggers, actions, events, and conditions.
• Capture Automation Flow: Take screenshots or notes of each automation’s flow for accuracy when recreating in Stack.

Step 2: Recreate Automations in Stack

• Access Workflows: Navigate to Automation > Workflows in Stack.
• Create New Workflow: Click on “Create New Workflow” and set up the workflow to replicate your ConvertKit automation.
• Set Entry Points (Triggers): Use Stack’s triggers to match ConvertKit’s entry points, such as form submissions or tag additions.
• Add Actions and Conditions: Recreate actions and conditions like sending emails or using if/else branches.
• Test the Workflow: Ensure all triggers, actions, and conditions work as expected.

Step 3: Post-Migration Check

• Run a Test: Use a test contact to verify that all workflow steps function correctly.

Migrate Subscribers (Contacts)

Subscribers in ConvertKit are equivalent to contacts in Stack.

Step 1: Export Subscribers from ConvertKit

• Navigate to Subscribers: Go to Subscribers > Grow in ConvertKit.
• Select All Subscribers: Click the checkbox to select all subscribers.
• Export Subscribers: Choose Bulk Actions > Export to initiate the export.

Step 2: Import Subscribers into Stack

• Navigate to Contacts: Go to Contacts > Import Contacts in Stack.
• Upload CSV File: Upload the CSV file exported from ConvertKit.
• Map Fields: Map the CSV fields to the appropriate fields in Stack.
• Segment and Tag Contacts: Recreate segments and tags using ConvertKit’s tagging information.

Step 3: Post-Migration Check

• Verify Import: Ensure all data has been correctly mapped and segmented in Stack.

Migrate Forms

ConvertKit forms can be recreated using Stack’s form builder.

Step 1: Document Form Details

• List Forms: Document forms, including fields, design, and settings like redirect URLs.

Step 2: Recreate Forms in Stack

• Access Form Builder: Navigate to Sites > Forms in Stack.
• Create New Form: Add fields used in your ConvertKit forms.
• Customize Design: Match design elements to your original forms.
• Set Form Actions: Configure actions like redirects and confirmation emails.
• Integrate with Workflows: Ensure forms trigger the appropriate Stack workflows.

Step 3: Post-Migration Check

• Test Form Submissions: Verify data capture and workflow triggers with test entries.

Migrate Landing Pages

Recreate ConvertKit landing pages in Stack for enhanced integration.

Step 1: Document Landing Page Details

• List Landing Pages: Document each page, including templates and content.

Step 2: Recreate Landing Pages in Stack

• Access Landing Page Builder: Go to Sites > Funnels/Websites and create new landing pages.
• Select Template: Choose a template matching your ConvertKit layout.
• Rebuild Content: Recreate content and design elements.
• Set Up Forms: Embed Stack forms and ensure proper workflow links.

Step 3: Post-Migration Check

• Preview and Test: Ensure all elements work, including form submissions.

Migrate Email Broadcasts

Recreate ConvertKit email broadcasts in Stack.

Step 1: Document Email Broadcasts

• List Broadcasts: Document broadcasts, including subject lines and content.

Step 2: Recreate Email Broadcasts in Stack

• Access Email Campaigns: Navigate to Marketing > Email Campaigns.
• Create New Campaign: Set up the email broadcast, replicating content and design.
• Segment Recipients: Define recipient lists using imported tags.
• Schedule or Send: Choose to send immediately or schedule for later.

Step 3: Post-Migration Check

• Send Test Email: Verify design and content across email clients.

Migrate Commerce Features

ConvertKit’s commerce tools can be mirrored in Stack using payment integrations.

Step 1: Document Commerce Products

• List Products: Document digital products or subscriptions, including pricing and fulfillment methods.

Step 2: Recreate Commerce Products in Stack

• Access Payments & Order Forms: Navigate to Sites > Order Forms to set up product pages.
• Set Product Pricing: Recreate pricing models.
• Configure Fulfillment: Ensure product delivery upon purchase.
• Integrate with Workflows: Link purchases to follow-up workflows.

Step 3: Post-Migration Check

• Test Purchase Flow: Confirm payment processing and product delivery.

Export Data from ConvertKit

Export essential data from ConvertKit for reference or import into Stack.

Step 1: Export Subscriber List

• Navigate to Export: Go to Subscribers > Grow and select Export.

Step 2: Review Exported Data

• Verify Data Integrity: Ensure all necessary information is captured accurately.

Step 3: Import Data into Stack (Optional)

• Import Additional Data: Import tags, engagement scores, or custom field data if necessary.

Step 4: Post-Migration Check

• Cross-Check Data: Verify all subscriber information and tags are accurately imported.

Additional Considerations

Training and Support

• Internal Training: Familiarize your team with Stack’s features, especially those differing from ConvertKit.
• Access Support: Ensure your team knows how to access Stack’s support resources.

Ongoing Monitoring

• Monitor Performance: Regularly check the performance of your campaigns and automations.
• Optimize Settings: Use Stack’s analytics to identify areas for improvement.

Backup and Data Retention

• Keep Backups: Retain backups of your ConvertKit data for historical reference.
• Data Retention Policies: Ensure Stack’s data retention aligns with your business needs.

Frequently Asked Questions

How do I migrate my Visual Automations from ConvertKit to Stack?

Document each automation, including triggers and conditions. In Stack, create new workflows to replicate these automations, set up matching triggers, and test to ensure all steps function correctly.

How do I export subscribers from ConvertKit?

In ConvertKit, navigate to Subscribers > Grow, select all subscribers, and choose Bulk Actions > Export. The file will be emailed to you or can be downloaded directly.

How do I import ConvertKit subscribers into Stack?

In Stack, go to Contacts > Import Contacts, upload your CSV file, map the fields, and verify that all data is correctly imported and segmented.

How do I recreate my ConvertKit forms in Stack?

Document your forms, including fields and design. In Stack, create new forms, customize design, configure actions, and integrate with workflows. Test each form to ensure proper functionality.

How do I migrate landing pages from ConvertKit to Stack?

Document each landing page’s details. In Stack, create new landing pages, rebuild content, embed forms, and configure domain settings. Test to ensure all elements work correctly.

How do I recreate my email broadcasts in Stack?

Document your broadcasts and replicate them in Stack’s email campaigns, using imported tags for recipient lists. Send test emails to verify rendering.

How do I migrate my digital products and commerce features?

Document your products and recreate them in Stack’s order forms, ensuring pricing and fulfillment are set up correctly. Test the purchase flow for accuracy.

What data should I export from ConvertKit before completing the migration?

Export your full subscriber list and verify the CSV includes all necessary information. Consider exporting other relevant data for historical reference.

What post-migration checks should I perform to ensure everything is working properly?

Test workflows, verify imported contacts, submit test entries through forms, preview landing pages, send test emails, and check product purchases.

What ongoing considerations should I keep in mind after migrating to Stack?

Provide training, monitor performance, use analytics for improvement, retain backups, and review data retention policies.