Buttondown Import Subscribers Not Working
Quick answer
Imports fail or skip rows when the CSV has invalid emails, future dates or unconfirmed addresses. Export from your old tool, upload under Subscribers > Import and read the results report for rejected rows.
Most likely fix: Prepare the CSV
How to fix it
Try these in order — the most common fix is first.
1. Prepare the CSV
- Export from Substack (Subscribers > All subscribers > Export), Mailchimp or Kit
- Only an email column is required; tags and join dates are optional
- Use standard column names like email, name, tags
Did this fix it?2. Run the import
- Open the Subscribers tab and click Import
- Drag in the file
- Wait; large lists can take up to a few hours
Did this fix it?3. Review rejected rows
- Open the import results and read the reasons for bad subscribers
- Fix the rows and re-import them
Did this fix it?4. Paid Substack subscribers
- Use Buttondown's separate guide for importing paid Substack subscriptions
- Connect Stripe first
Did this fix it?
Symptoms
Import runs but subscribers are missing, counts do not match, or the import takes hours.
Why it happens
- Invalid or duplicate email addresses
- Rows with future creation dates
- Unrecognized column names
- Large lists take minutes to hours to process
- Unsubscribed or bounced contacts excluded from the old export
This guide also covers
- buttondown import subscribers
- import substack to buttondown
- buttondown csv import
Still not working?
If Buttondown keeps failing, you're not alone. See every Buttondown problem users report or the alternatives people switch to.
Done fighting Buttondown? Our small team builds your own Buttondown alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to usThe same problem in other apps
All storage, upload & download guides →
- beehiiv Import Subscribers Failed (beehiiv)
- ConvertKit (Kit) CSV Import Failed or Wrong Subscriber Count (ConvertKit (Kit))
- Mailchimp Contact Import Not Working (Mailchimp)