> ## Documentation Index
> Fetch the complete documentation index at: https://subscriptions-docs.getappfox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Import & migration

> Migrate subscriptions from other platforms

If you're switching to Appfox Subscriptions from another app, you can import your existing subscription contracts. The import process preserves customer subscriptions, billing schedules, and order history.

## Supported platforms

Appfox Subscriptions can import data from:

* **Appstle**: CSV export files from Appstle Subscriptions
* **Recharge**: CSV export files from Recharge Subscriptions
* **Shopify native contracts**: Sync existing Shopify subscription contracts created by other apps

## Import from CSV

<Steps>
  <Step title="Export from your current app">
    In your existing subscription app, export your subscription data to CSV format. Follow that app's export instructions to get a complete data file.
  </Step>

  <Step title="Go to Import settings">
    In Appfox Subscriptions, click **Settings**, then click **Import & migration**.
  </Step>

  <Step title="Upload the CSV">
    Click **Choose file** and select the CSV export from your previous app.
  </Step>

  <Step title="Map fields">
    Review the field mapping to ensure customer data, products, billing schedules, and payment information align correctly.
  </Step>

  <Step title="Start the import">
    Click **Import** to begin. The import runs in the background and may take several minutes depending on the number of subscriptions.
  </Step>

  <Step title="Review imported subscriptions">
    Once complete, check the **Subscriptions** page to verify that all contracts imported correctly.
  </Step>
</Steps>

## Sync Shopify contracts

**Important:** Shopify subscription contracts are app-owned. You cannot transfer contracts between apps — only the app that created a contract can manage it.

"Migration" between subscription apps means:

1. Export data from the old app
2. Create new contracts in the new app (Appfox)
3. Cancel or delete the old contracts
4. Customers update payment methods

The import process creates new Appfox contracts that replicate the settings from your old app, but they are technically new subscriptions in Shopify's system.

If you have existing Shopify subscription contracts created by another app:

<Steps>
  <Step title="Go to Import settings">
    Click **Settings**, then click **Import & migration**.
  </Step>

  <Step title="Click Sync Shopify contracts">
    Select the option to sync existing contracts from Shopify.
  </Step>

  <Step title="Review contracts">
    The app will discover active Shopify subscription contracts and list them for review.
  </Step>

  <Step title="Complete the sync">
    Click **Sync** to import the contracts into Appfox Subscriptions. Billing schedules and customer information are preserved.
  </Step>
</Steps>

## What gets imported

The import process brings over:

* Customer information (name, email, addresses)
* Active subscription contracts
* Billing schedules and frequencies
* Product line items and quantities
* Subscription status (active, paused, cancelled)
* Order history where available

## What doesn't transfer

Some data cannot be imported automatically:

* **Payment tokens and methods** — Payment gateway tokens (e.g., WooPayments, Stripe Express) cannot be imported due to PCI compliance and security requirements. Customers must update their payment methods after migration through the Shopify customer portal.
* **Custom integrations or webhooks** — Integration configurations from the previous app don't transfer
* **App-specific features** — Features unique to the previous app that don't have equivalents in Appfox
* **Historical analytics and reports** — Past reporting data stays in the source system

You'll need to reconfigure integrations and custom features after the import completes.

### Payment method migration

After importing subscription contracts, you must send customers secure links to update their payment methods. The app provides a bulk email tool to notify all migrated customers at once.

This is a standard part of subscription app migration — payment tokens are gateway-specific and cannot be transferred between different payment providers or apps.

<Warning>
  Plan your migration communication carefully. Send payment update emails immediately after the import completes, and monitor completion rates. Subscriptions without valid payment methods will fail at the next billing attempt.
</Warning>

<Note>
  Test the import process with a small batch of subscriptions before importing your entire customer base. This lets you verify field mappings and catch any issues early.
</Note>

<Tip>
  Schedule the migration during a low-traffic period. While imports run in the background, it's best to complete the switch when you have time to monitor the process.
</Tip>