Migration
Migrate subscription contracts from other apps to Easto seamlessly using a structured CSV import - no customer disruption, no lost billing cycles.
1. Introduction:
If you’re switching from another subscription app to Easto, you don’t have to start from scratch. Our import feature allows you to migrate existing subscription contracts using a CSV file, so you can keep your customers, billing schedules, and delivery settings intact — without asking customers to re-subscribe.
This guide will walk you through how to prepare your data, how to import it step by step, and best practices to avoid common issues.
2. How to use:
Prepare your store
Before importing subscription contracts, make sure that:
Customers already exist in your Shopify store
Product variants included in subscriptions are available
Selling plans are created in Easto
Customer payment methods are available (if applicable)
This ensures imported contracts can continue billing and delivering smoothly.
Download and review the sample file
Download the sample CSV file provided by Easto. Each row in the file represents one subscription contract.
The file includes key information such as:
Subscription status and billing schedule
Customer and payment details
Delivery method and address
Product variants and selling plans
Use this sample as a template to format your own data correctly.
Fill in your subscription data
Carefully map data from your old subscription app into the CSV file.
Some important fields to double-check:
Subscription status (ACTIVE, PAUSED, CANCELLED, etc.)
Upcoming billing date (must be more than 24 hours after import)
Billing cadence (interval and interval count)
Customer ID and payment method ID
Variant ID and selling plan ID
Make sure all required fields are filled and formatted correctly.
3. Tips:
💡 Test with a small batch first Start by importing a few subscriptions before migrating all data. This helps catch formatting or mapping issues early.
💡 Use ISO date format
All date fields should follow ISO 8601 format (for example: 2026-01-25T03:20:00Z) to avoid import errors.
💡 Match selling plans carefully Selling plan IDs in the CSV must already exist in Easto. A mismatch will cause the row to fail.
💡 Don’t rush the migration Keep your old subscription app active until you’ve confirmed that imported subscriptions are billing and delivering correctly in Easto.
If you need help, feel free to reach out to us via in-app Live chat, Book a call or at [email protected].
Last updated