Migrating from Drip to Kit

Complete Guide: Migrating from Drip to Kit (ConvertKit)

Why Migrate from Drip to Kit?

Common reasons for migrating from Drip to Kit (ConvertKit):

• Creator-Focused Platform: Kit is designed specifically for creators, bloggers, and course creators (vs. Drip’s e-commerce focus)
• Simpler Interface: Kit has a cleaner, easier-to-use interface with less feature bloat
• Newsletter Management: Kit excels at newsletter management with subscriber-friendly features
• Landing Page Builder: Kit includes built-in landing pages and lead magnets (Drip requires third-party tools)
• Cost Optimization: For creator businesses not using Drip’s e-commerce features, Kit may be more cost-effective
• Visual Automation: Kit’s visual automation builder is intuitive for simple sequences

Drip vs Kit: Key Feature Comparison

Understanding what changes during this migration:

What You’ll Need Before Starting

✅ Required Access & Accounts

• WordPress admin access to your AccessAlly site
• Drip account access (for data export)
• Kit (ConvertKit) account (must be set up and configured first)
• AccessAlly license that supports CRM switching
• Access to your payment gateway (Stripe or PayPal)

📋 Complete the Pre-Migration Checklist

Before proceeding, work through the complete Pre-Migration Checklist. Key items include:

• Full backup of WordPress site and database
• Export of all Drip contact data
• Audit of custom fields (which can become Kit tags?)
• Data mapping spreadsheet (contacts, tags, custom fields → tags)
• Staging site setup for testing (MANDATORY for CRM switches)
• Request 2-site exception from AccessAlly support
• Downtime plan and member communication

Phase 1: Pre-Migration Setup (2-3 hours)

Step 1: Set Up Your Kit Account

1. Sign up for Kit (ConvertKit) at convertkit.com
2. Choose appropriate pricing tier for your subscriber count
3. Complete basic account setup (name, timezone, sender email)
4. Configure email deliverability (SPF, DKIM records)
5. Create a test form and sequence
6. Send yourself a test email to verify deliverability

Step 2: Export Your Data from Drip

1. Log into your Drip account
2. Go to Settings → Account
3. Click “Export All Subscribers”
4. Drip will email you a CSV file (may take 15-30 minutes for large lists)
5. Download and open the CSV file

What’s included in the Drip export:

• Email addresses
• First and last names
• Custom fields (all stored as text in Drip)
• Tags (flat structure)
• Subscription status (active/unsubscribed)
• Opt-in timestamps

What’s NOT included:

• Workflow automations (must be rebuilt in Kit as sequences)
• Email campaign history
• Form designs
• E-commerce tracking data (revenue, products)

Step 3: Plan Your Custom Field → Tag Conversion Strategy

This is the most critical planning step for Drip → Kit migrations.

Evaluate each Drip custom field:

Create a conversion mapping document:

1. List every Drip custom field you use
2. Decide: Convert to Kit tag, or store in WordPress only?
3. For fields converted to tags, create tag naming convention (e.g., “Field: Value”)
4. Document which fields affect AccessAlly access rules

Step 4: Map Your Drip Data to Kit

Create a complete data mapping spreadsheet. Use the Data Mapping Reference Guide.

Step 5: Recreate Tags in Kit

1. Make a complete list of all tags from your Drip export
2. Add any new tags for converted custom fields
3. Go to Kit → Subscribers → Tags
4. Create each tag in Kit
5. Use exact same names as Drip for easier mapping

Step 6: Prepare Your CSV for Import

Transform your Drip export to match AccessAlly Migration Wizard format.

Required columns:

• email – Email address (required)
• first_name – First name
• tags – Comma-separated list of Kit tag names (including converted custom fields)

CSV transformation steps:

1. Open your Drip export in Excel or Google Sheets
2. Rename columns:
   • Drip “Email” → email
   • Drip “First Name” → first_name
   • Drip “Tags” → tags
3. CRITICAL: For each custom field being converted to a tag:
   • Create a new column with tag values (e.g., if field “Member Level” = “Gold”, add “Gold Member” to tags)
   • Merge all tag columns into one comma-separated tags column
4. Remove unsubscribed contacts (Kit will handle unsubscribes separately)
5. Save as new CSV: “drip-to-kit-import.csv”

Step 7: Connect Kit to AccessAlly (Staging Site First)

1. On your STAGING site, go to AccessAlly → Settings → General
2. Under “CRM Integration,” change from Drip to ConvertKit
3. Enter your Kit API credentials:
   • API Key (found in Kit → Settings → Advanced → API)
   • API Secret (same location)
4. Click Save and Test Connection
5. Verify connection is successful

Phase 2: Migration Execution (2-3 hours)

Step 8: Download and Activate Migration Wizard Plugin

1. Go to AccessAlly → Utilities
2. Find “Migration Wizard Plugin”
3. Click Download to get the plugin ZIP file
4. Go to WordPress → Plugins → Add New → Upload Plugin
5. Upload the Migration Wizard ZIP file
6. Click Activate Plugin

Full instructions: Using the AccessAlly Migration Wizard Plugin

Step 9: Import Contacts via Migration Wizard

1. On your STAGING site, go to AccessAlly → Migration Wizard
2. Click “Import from CSV”
3. Upload your prepared CSV file
4. Map CSV columns to Kit fields
5. Choose import options:
   • Update existing users: Check if some members may already exist
   • Create users in CRM: Check (creates contacts in Kit)
   • Add tags: Check (applies tags from CSV)
   • Send welcome email: UNCHECK (email members separately later)
6. Click “Start Import”

What happens during import:

• WordPress user accounts created (if they don’t exist)
• Contacts created in Kit
• Tags applied in Kit (including converted custom field tags)
• Contact ID from Kit stored in WordPress user meta (CRITICAL)
• This Contact ID linking is essential for access control

Step 10: Verify Contact ID Linking

This is the MOST CRITICAL test for CRM switches.

1. Pick 3-5 random WordPress users
2. In WordPress, go to Users and edit each user
3. Scroll to user meta and look for convertkit_subscriber_id or kit_subscriber_id
4. Note the ID (e.g., “12345678”)
5. Go to Kit and search for that subscriber ID
6. Verify it’s the correct contact
7. Test: Add a tag to the contact in Kit, then check if AccessAlly recognizes it

Step 11: Update AccessAlly Access Rules

If you converted custom fields to tags, you need to update AccessAlly to use the new tag-based access rules.

1. Go through each AccessAlly Module
2. Check “Who Can Access” settings
3. If access was previously based on custom fields, update to use new tags
4. Example: If “Member Level” custom field was “Gold”, change access rule to require “Gold Member” tag
5. Repeat for all protected pages
6. Update order form tag assignments
7. Update email wizard tag triggers

Step 12: Link Payment Gateway Subscriptions

If you have paid members with active subscriptions:

1. Export active subscriptions from Stripe or PayPal
2. Match subscription IDs to member email addresses
3. Use Migration Wizard’s “Link Subscriptions” feature OR
4. Manually update each member’s subscription ID in AccessAlly

Detailed guide: How to Migrate Subscription Payments

Step 13: Rebuild Automations in Kit

Drip workflows must be rebuilt as Kit sequences.

Drip → Kit automation mapping:

Common automations to rebuild:

• Welcome sequences: Use Kit visual automations
• Tag-based sequences: Use Kit event triggers
• Purchase follow-ups: Use Kit purchase automations (if using Kit Commerce) or AccessAlly automations
• Re-engagement campaigns: Use Kit automation sequences

Step 14: Migrate Forms

Replace Drip forms with Kit or AccessAlly forms.

Option 1: Use Kit Forms (Good for landing pages)

1. Create forms in Kit → Grow → Landing Pages & Forms
2. Embed Kit form code on your WordPress pages
3. Style forms using Kit’s builder
4. Set up tag assignments

Option 2: Use AccessAlly Forms (Recommended for membership site)

1. Create forms in AccessAlly → Opt-in Forms
2. Configure to submit to Kit
3. Better integration with AccessAlly features
4. More control over styling and behavior

Phase 3: Go-Live and Verification (2-3 hours)

Step 15: Extensive Staging Testing

Before touching your live site, thoroughly test on staging:

• ✅ Member login works for different membership levels
• ✅ Content access rules work correctly (especially new tag-based rules)
• ✅ Tags control access properly
• ✅ Forms submit to Kit and apply correct tags
• ✅ Purchase flow works end-to-end
• ✅ Subscription linking works
• ✅ Failed payment handling tested
• ✅ Automations trigger correctly
• ✅ Email sequences work

Step 16: Switch Live Site to Kit

Only after all staging tests pass:

1. Schedule downtime window (3-4 hours recommended)
2. Communicate with members (announce scheduled maintenance)
3. Put site in maintenance mode
4. Create fresh WordPress backup
5. Export final Drip data (capture any new contacts since staging)
6. Switch AccessAlly to Kit (same steps as staging)
7. Import any new contacts from final export
8. Verify access rules
9. Test login for 3-5 members (different membership levels)
10. Take site out of maintenance mode
11. Monitor closely for 1-2 hours

Step 17: Complete Post-Migration Verification

Work through the complete Post-Migration Verification Checklist. Key items for Drip → Kit:

✅ Contact Data Integrity

• Verify total contact count matches Drip export
• Check 10 random contacts in Kit for complete data
• Verify Contact IDs properly stored in WordPress
• Check for duplicate contacts
• Verify tags (including converted custom field tags) applied correctly

✅ Access & Permissions

• Test login as multiple member types
• Verify access to protected content for each membership level
• Check tag-based access rules work (especially new tag-based rules)
• Test content unlocking based on tags

✅ Tags & Converted Custom Fields

• Verify original Drip tags migrated correctly
• Verify custom field → tag conversions worked
• Test that tag-based access rules work for converted fields
• Check 10 random contacts have correct tags

✅ Forms & Automations

• Test each opt-in form submission
• Verify form data reaches Kit
• Test order form purchases (use Stripe test mode)
• Confirm post-purchase automations fire in Kit or AccessAlly
• Test auto-login after purchase (if enabled)

✅ Subscriptions & Payments

• Verify active subscriptions linked correctly
• Test new purchase flow end-to-end
• Test subscription cancellation
• 🚨 CRITICAL: Test failed payment handling
• Verify member access aligns with payment status

Step 18: Monitor for 7 Days

Don’t cancel Drip immediately. Monitor for issues during the first week:

• Day 1-2: Watch for immediate issues (login problems, access errors)
• Day 3-5: Monitor form submissions and automation triggers
• Day 6-7: Check subscription/payment handling

What to monitor:

• Member support tickets (migration-related confusion?)
• Login errors or access issues
• Payment failures or subscription problems
• Form submission success rates
• Email deliverability (Kit vs. Drip rates)

Step 19: Clean Up

Once migration is stable (7+ days):

1. Disconnect Drip from AccessAlly (remove API keys)
2. Deactivate Migration Wizard plugin
3. Export final Drip data for records
4. Downgrade or cancel Drip (after 30-day safety period)
5. Remove staging site’s 2-site exception (contact AccessAlly support)
6. Update member documentation if needed

Troubleshooting Common Issues

Issue 1: Contact IDs Not Linking (MOST COMMON)

Symptoms: Members have correct tags in Kit but can’t access content

Causes:

• Contact ID not stored in WordPress user meta during import
• Contact ID stored under wrong meta key
• WordPress user exists but Kit contact doesn’t

Solution:

1. Check WordPress user meta for “kit_subscriber_id” or “convertkit_subscriber_id”
2. If missing, re-import the user via Migration Wizard with “Update existing users” checked
3. Verify the Contact ID in Kit matches the stored ID
4. Test access after fixing Contact ID

Issue 2: Converted Custom Field Tags Not Granting Access

Symptoms: Members who had custom field values in Drip can’t access content that should be controlled by those values

Causes:

• Custom field wasn’t properly converted to tag during CSV transformation
• Tag name in AccessAlly doesn’t match converted tag name in Kit
• Tag wasn’t applied during import

Solution:

1. Check the member’s tags in Kit (look for converted custom field tags)
2. If tag is missing, manually add it in Kit
3. Go to AccessAlly module/page access settings
4. Verify tag name EXACTLY matches Kit (case-sensitive)
5. Test access again

Issue 3: Members Missing Last Names

Symptoms: Members’ last names didn’t transfer to Kit

Causes:

• Kit doesn’t have a native “last name” field
• Last name stored in WordPress only

Solution:

1. This is expected behavior (Kit limitation)
2. Last names are stored in WordPress user meta
3. They won’t sync to Kit, but AccessAlly can still access them
4. Use WordPress merge tags for last name in AccessAlly emails

Issue 4: Kit Sequences Not Triggering

Symptoms: Kit automations not firing when tags are applied

Causes:

• Sequence trigger misconfigured
• Tag name in trigger doesn’t match exactly
• Subscriber already in sequence

Solution:

1. Go to Kit → Automate → Visual Automations
2. Check trigger settings (exact tag name)
3. Verify subscriber isn’t already in sequence
4. Test with a new test subscriber

Issue 5: Forms Not Submitting to Kit

Symptoms: Form submissions not creating/updating contacts in Kit

Causes:

• AccessAlly not properly connected to Kit
• Form configured for old Drip connection
• Kit API rate limit reached

Solution:

1. Verify AccessAlly → Kit connection still active
2. Edit form settings in AccessAlly
3. Ensure form is set to submit to Kit (not Drip)
4. Test form submission and verify in Kit

Issue 6: Missing Drip E-commerce Data

Symptoms: Purchase history and revenue data from Drip not in Kit

Causes:

• Kit has limited e-commerce tracking compared to Drip
• E-commerce data doesn’t migrate automatically

Solution:

1. Accept this is a Kit limitation
2. Use AccessAlly’s purchase tracking instead
3. Convert purchase history to tags if needed for segmentation
4. Consider using Kit Commerce for future purchases

Migration Timeline & Downtime

Total Time Estimate: 5-7 hours (custom field conversion adds time)

Recommended Downtime Window: 2-3 hours on a weekend or low-traffic period for the live site switch

Need Help?

Consider professional migration assistance if:

• You have 10+ custom fields that need conversion to tags
• You have 1,000+ active members
• You have complex tag-based access rules
• You can’t afford downtime or access issues
• You’re not comfortable with CSV transformations

Migration Support:

• Review the Migration Support Policy
• For migration assistance: Contact AccessAlly support

Related Guides:

• Pre-Migration Checklist
• Post-Migration Verification
• Data Mapping Reference
• Drip → AccessAlly Managed (similar source CRM)
• How to Migrate CRMs and Keep Same Site
• Preserving Subscriptions During Migration