Teachable to AWeber: the migration guide

Why you cannot just export once

Teachable's own Users help article lists the export columns as User ID, Full name, Email, Phone number, Last login, Joined at,Course count, SRC, Country, Sign-in count, Unsubscribe from marketing emails, Affiliate code, Billing and delivery address, and Tags.Source

Course count is a number, how many courses someone is enrolled in. There is no column that names which one. Export your whole school in one go and you get a list of buyers with no way to tell who owns what.

The workaround is the one Teachable's own filters make possible: filter the Users list to a single course first, then export. The resulting file is that course's buyer list, because the filter produced it, not because the file says so. Do this once per course, plus once with no filter at all to catch people on your list who have not bought anything.

What Teachable's Emails tool can and cannot already do

It is worth being precise here, because it changes how much of a gap you are actually closing. Teachable's Users list can be filtered by Has Tag(s), Does Not Have Tag(s), and by course, and an Email Studentsbutton on that filtered list opens a compose screen with the filtered people already selected.Source

So a one-off, filtered broadcast to one course's buyers is something Teachable can already do, by hand, every time you want to send one. What it does not do, in its own documentation's words, is run a multi-email sequence that starts automatically when someone buys. Teachable's own support content puts it this way: it lets you "send emails to users in your school, view the history of emails sent from your school, edit the templates of automated emails, and set notification preferences." The "automated emails" there are transactional templates, receipts and confirmations, not a sequence you write.Source

That is the real reason to move: not that Teachable cannot segment at all, but that every send is you, manually, filtering a list and clicking a button. AWeber is where that becomes a workflow that runs once you build it.

What actually moves, and what does not

Say the last row out loud before you start. You are not leaving Teachable. It keeps hosting the courses and taking the money. On the pricing snapshot read 5 September 2026, that is $59/mo on Starter ($39/mo billed yearly, plus a 7.5% transaction fee), $119/mo on Builder ($89/mo yearly, 0% fee), or $239/mo on Growth ($189/mo yearly, 0% fee), and none of it changes because your marketing email moved.Source

Step 1: decide your tags before you export anything

One tag per course, named the same way every time:bought-intro-course, bought-flagship. One tag for people who never bought, lead-no-purchase. Renaming a tag later is annoying once it is wired into a workflow, so get the names right before you touch Teachable.

Step 2: export from Teachable, once per course

On the Users page, filter to one course, then clickExport CSV in the top right. The file arrives by email rather than downloading in the browser, and Teachable's article gives the download link a short expiry, roughly 24 minutes in the text we read. That is an unusual figure worth reading directly off the live article before you rely on it, rather than stepping away while an export is in flight.Source

Rename each file the moment it lands, flagship.csv,intro.csv. Then do one more export with no course filter, so you can find people on your list who have bought nothing.

Step 3: shape each CSV for AWeber's import

Open each file and add a column called exactly Tag. AWeber's own import article is specific about the shape: add a field called Tag as a new column, and if a subscriber gets more than one tag, separate them with commas in that one cell.Source

Delete every row where Teachable's Unsubscribe from marketing emails column reads TRUE before you import. Those people opted out inside Teachable, and carrying them into AWeber re-subscribes someone who already said no.

AWeber accepts XLS, XLSX, TSV, CSV or TXT, and maps your columns to its own fields on a screen after upload rather than requiring exact header names.Source

Step 4: import, one file at a time

On the import screen, AWeber lets you choose whether to add only new subscribers or update people who already exist in your list. That is what lets you import a second course's file without duplicating someone who bought twice: pick update, and their second file's tag lands on the same record as the first.Source

Not confirmed: AWeber's import articles do not state a maximum file size or row count. Start with your smallest course file and confirm it lands correctly before you run the rest.

Step 5: check it actually worked

Search two or three people by hand: someone who bought one course, someone who bought several, and someone who bought nothing. Open each subscriber record in AWeber and read the tags on it. That five-minute check catches the kind of mistake a row count alone hides, like an entire file landing with the wrong tag.

Step 6: keep new buyers tagged automatically

The import is a photograph of today. Teachable's App Hub has an AWeber integration you turn on from your school admin: install it, log into AWeber, and allow access. From there it can create or update a contact in a specific AWeber list whenever one of five things happens in Teachable: a new sign-up, a new sale, a new enrollment (including one you add by hand), a course completion, or a subscription cancellation.Source

Two things worth knowing before you rely on it. First, it moves data one way only: Teachable's own article states plainly that "AWeber triggers and actions are not available at this time," so nothing you do in AWeber can trigger anything back in Teachable. Second, you can scope a workflow to the whole school or to one course, which is what lets you route each course's buyers into their own AWeber list without touching Zapier at all.Source

Not confirmed: Teachable's article says Builder-plan schools get one workflow and Growth and up get unlimited workflows, but does not say whether the app is available on Starter at all. Check this in your own school before you plan around it.

The exact click path for setting this up, plus the tag-by-course recipe that gets a distinct tag onto each buyer rather than just a list membership, isits own page.

What breaks, and what you rebuild by hand

• Two suppression lists exist now. Someone who unsubscribes in AWeber is still marked subscribed in Teachable. Decide AWeber is the source of truth for marketing consent, and stop sending marketing broadcasts from Teachable's Emails tab.
• Teachable's transactional email stays, and should.Receipts, enrollment confirmations, password resets, those are Teachable's job and depend on Teachable's data.
• Your list starts cold. Send to your most recent, most engaged buyers first, and build up from there rather than mailing everyone on day one. A brand new sending reputation gets judged on how those early sends behave.
• Teachable's built-in cart recovery needs a decision, not a rebuild. Teachable already has one, bundled into every paid plan. Whether to keep using it or route the signal into AWeber instead isits own page.

What this takes

These are estimates from the documented steps, not a stopwatch reading. Time your own run and trust that over the table.

When not to do this

• You send one broadcast a month to everyone and that is fine.
• You have one course. There is nothing to tell apart yet.
• You are mid-launch. Never migrate a list while a cart is open.