{"id":231,"date":"2026-08-27T08:30:00","date_gmt":"2026-08-27T08:30:00","guid":{"rendered":"https:\/\/www.jeanmariecordaro.com\/?page_id=231"},"modified":"2026-08-27T08:30:00","modified_gmt":"2026-08-27T08:30:00","slug":"migrate-gumroad-to-bonzai","status":"publish","type":"page","link":"https:\/\/www.jeanmariecordaro.com\/index.php\/migrate-gumroad-to-bonzai\/","title":{"rendered":"How to Move from Gumroad to Bonzai: Migration Checklist"},"content":{"rendered":"

How to Move from Gumroad to Bonzai: Migration Checklist<\/h1>\n

Last verified:<\/strong> August 12, 2026<\/p>\n

A Gumroad-to-Bonzai migration is currently a controlled rebuild, not a documented one-click transfer.<\/strong> Gumroad provides CSV exports for sales, customers and subscribers. Bonzai publicly documents product creation, built-in payments and downloadable email lists, but its public pages do not describe an automated Gumroad importer. Export first, ask Bonzai support what can be imported, then rebuild and test before sending buyers to the new checkout.<\/p>\n

Affiliate disclosure:<\/strong> some Bonzai links on this page are tracked affiliate links. A commission may be earned at no extra cost to you.<\/p>\n

Check migration support before moving live customers<\/h3>

Create the destination account, inventory the catalogue and ask Bonzai which customer or subscriber imports are supported today. Do not cancel working infrastructure before the answer is documented.<\/p>

Open Bonzai<\/a><\/div><\/div><\/div>\n

What can be moved, rebuilt or left behind<\/h2>\n
Asset<\/th>Likely path<\/th>Risk to check<\/th><\/tr><\/thead>
Product copy and media<\/td>Recreate product and sales pages in Bonzai<\/td>Formatting, embedded media and old URLs will differ<\/td><\/tr>
Download files<\/td>Upload current master files or connect the supported delivery method<\/td>File size, versioning and buyer access<\/td><\/tr>
Sales history<\/td>Retain Gumroad CSV exports as business records<\/td>Historical transactions may not appear in Bonzai analytics<\/td><\/tr>
Customer and subscriber data<\/td>Export from Gumroad; confirm lawful import and Bonzai support<\/td>Consent, suppression lists, geography and data minimization<\/td><\/tr>
Active subscriptions<\/td>Treat as a separate payment migration project<\/td>Payment credentials and recurring mandates usually cannot be copied<\/td><\/tr>
Affiliates and attribution<\/td>Export available records, then recreate eligible relationships<\/td>Old tracking links and commission history may not transfer<\/td><\/tr>
Licences or integrations<\/td>Map the existing entitlement logic before cutover<\/td>APIs, licence keys and automations may require redevelopment<\/td><\/tr><\/tbody><\/table><\/figure>\n

Step 1: freeze the current-state inventory<\/h2>\n

Record every live product, variant, price, currency, checkout URL, file, licence rule, discount, affiliate arrangement, refund promise and automation. Separate active products from experiments that no longer deserve migration work.<\/p>\n

For each offer, write down what the buyer receives immediately, what remains available later and which system checks access. A migration fails when the visible sales page is copied but the invisible entitlement logic is forgotten.<\/p>\n

Step 2: export Gumroad data before changing anything<\/h2>\n

Gumroad\u2019s sales dashboard documentation<\/a> says creators can download a CSV of customers and purchases for a selected date range. Gumroad\u2019s audience documentation<\/a> also describes subscriber CSV export. Keep dated copies of both, along with product files and the reports required for accounting or support.<\/p>\n

Do not move card numbers, passwords or private data that is unnecessary for the new service. An exported email address is not automatic permission for every future marketing use. Preserve opt-out and suppression information, and apply the rules relevant to the customers and business jurisdictions involved.<\/p>\n

Step 3: ask Bonzai four migration questions<\/h2>\n
  1. Can existing subscribers or customers be imported, and in which format?<\/li>
  2. Can imported users receive access to a product without a new charge?<\/li>
  3. How are active recurring subscriptions handled, if they can be handled at all?<\/li>
  4. What email consent, suppression and verification fields are preserved during import?<\/li><\/ol>\n

    Use the current support route published by Bonzai or email contact@bonzai.pro<\/a>. Keep the written answer with the migration plan because platform capability can change.<\/p>\n

    Step 4: rebuild the catalogue in the right order<\/h2>\n
    1. Identity:<\/strong> creator profile, business information and payout onboarding.<\/li>
    2. Core products:<\/strong> current files, course structure, coaching instructions or community access.<\/li>
    3. Offers:<\/strong> prices, currencies, billing cadence, instalments and access duration.<\/li>
    4. Sales pages:<\/strong> result, contents, terms, proof and support path.<\/li>
    5. Communication:<\/strong> receipt, welcome sequence, access instructions and buyer support.<\/li>
    6. Affiliation:<\/strong> recreate only the programmes that remain commercially relevant.<\/li><\/ol>\n

      Bonzai\u2019s product documentation<\/a> describes multiple offers, built-in product sales pages and its payment system. Its affiliation page<\/a> describes native tracking and commission handling. Test the exact configuration available in the account rather than treating marketing copy as implementation documentation.<\/p>\n

      Step 5: separate customers from subscribers<\/h2>\n

      A buyer entitled to a file or course is different from a newsletter subscriber. A recurring customer is different again. Build a mapping table with the old product, old status, intended Bonzai product, intended access and required communication.<\/p>\n

      Historical buyers may need continued access without repurchasing. If Bonzai cannot grant imported entitlement, keep the old delivery path available for those buyers or design a controlled claim process. Do not silently remove access to a product that was sold with continuing availability.<\/p>\n

      Step 6: treat subscriptions as a payment migration<\/h2>\n

      Recurring billing is the highest-risk part of the move. Payment credentials and mandates are not ordinary CSV fields. Unless both platforms explicitly support a compliant transfer, assume customers must authorise a new subscription.<\/p>\n