Migrate from Classic to Contextual Commerce
At FastSpring, your success is our mission. Migrating from Classic to Contextual Commerce is a significant decision — and a strategic one. This guide walks you through what to expect, key differences, and every step required to complete the transition.
Before you migrate
Classic and Contextual Commerce are distinct platforms, not versions of the same product. Read the following carefully before initiating your migration.
Read this before you begin
- Distinct applications: Classic and Contextual are two separate applications that operate independently of each other.
- Not a version upgrade: Contextual has been redesigned from the ground up. It is not a second version of Classic.
- Differences in functionality: Some features available in Classic may not be available in Contextual.
- Integration changes required: You will need to adapt your FastSpring integration to align with the Contextual platform.
Benefits of Contextual Commerce
Upgrading to a Contextual Store gives you access to a modern commerce platform built for SaaS businesses.
Popup Storefronts increase conversion rates by up to 30%. Buyers check out directly on your page without being redirected to a FastSpring-hosted store.
Use the Store Builder Library to display dynamic product details and localized pricing — including applicable taxes — directly on your website.
Buyers access order history, retrieve fulfillments, and manage subscriptions on a secure portal hosted by FastSpring and branded by you.
Filter and break down sales and consumer data with in-depth analytics for informed decisions.
Connect your store to marketing analytics tools, CRMs, DRMs, BI tools, and more via the FastSpring API.
A modernized app experience with new features and functionality for streamlined order and account management.
Overview of the upgrade
FastSpring features two ecommerce solutions: Classic, the original product, and Contextual, the modern solution. Both contain Stores — each a separate collection of products, promotions, styling, consumer-facing email content, and checkout experiences.
When FastSpring Support creates your new Contextual Store, you can access it at app.fastspring.com. Your Classic Store(s) remain accessible through Springboard.
Expand the sections below to understand what data carries over and where the two platforms differ.
Data that cannot be migrated
Your new Contextual Store is separate from your Classic Store. Historical transaction data remains in the original Classic Store.
| Data type | Where to manage it |
|---|---|
| Active Classic subscriptions | Continue managing via Springboard. Consumers cannot manage Classic subscriptions through the Contextual Account Management portal. |
| Order history | Look up orders and process returns for pre-migration orders in Springboard. New orders placed in Contextual are accessible in the FastSpring app. |
| Historical reporting | Run sales reports for existing order history in Springboard. The FastSpring app covers transactions and subscriptions processed in Contextual. |
Differences between Classic and Contextual
Migrated subscriptions may return different payloads
If you migrated subscriptions from Classic to Contextual Commerce (C2C), both webhook payloads and API response payloads for those subscriptions may differ from subscriptions created natively in Contextual Commerce.
Before updating your integration to rely on Contextual payload structures, verify the behavior of your migrated subscriptions. If you need guidance on how C2C migration affects your existing webhooks or API integration, submit a support ticket.
| Feature | Notes |
|---|---|
| GET API | Classic: GET /company/{company}/order/{reference}. Contextual: GET /orders/{order id}. The Contextual API cannot return order records by consumer-facing reference. Obtain order IDs via webhook events such as order.completed or by calling GET /accounts. |
| Reseller stores | Contextual does not have reseller store capabilities. Continue using Classic reseller stores. |
| Coupons | Contextual does not have a built-in coupon code generator. Use a third-party solution to generate batch unique codes. See Coupons. |
| Checkout | Use the Store Builder Library to enable persistent sessions. The optional data-continuous attribute writes cart contents to local storage. Web Storefronts do not have persistent sessions. |
| Backup CDs/DVDs/Flash Media | Set up an account with a third-party fulfillment partner and create a Physical Shipment product. Configure the order.completed webhook to notify your partner. Contextual does not offer a backup media solution. |
| Store styles | Web Storefronts do not have a direct equivalent to Classic Styles. Control store page content with the Store Builder Library. |
| Store-wide promotions | Create a coupon for a time-limited discount across all products, or apply product-specific discounts with date ranges. Contextual does not support a single automatic store-wide discount. |
| URL parameters | Use custom JavaScript with the Store Builder Library to replicate URL parameter behavior. Web Storefronts cannot read URL parameters to adjust checkout flow automatically. |
| Custom fields | Use form fields with the Store Builder Library or the /sessions endpoint to collect custom data. Pass it to the order using order tags and product attributes. Web Storefronts do not support custom fields. |
| Split payees | Contextual supports split payouts by product, store, or source. It does not support splitting by coupon. |
Platform comparison
The table below summarizes the key capability differences between Classic and Contextual Commerce to help you plan your integration updates.
| Feature | Contextual Platform | Classic Platform |
|---|---|---|
| Same-page checkouts | Three checkout types: Web, Popup, and Embedded. Popup Storefronts boost conversion rates by up to 30%. | Redirects buyers to a FastSpring-hosted store page. Limited customizability. |
| Customizable experience | Extensive customization via Store Builder Library; dynamic product details and localized pricing. | Limited customization; may result in a generic user experience. |
| Storefronts and checkouts | Three highly customizable checkout types. Store Builder Library for custom cart experiences. | Basic web-checkout with limited customizability. |
| Subscription features | 1ClickPay, Trial Hopping Prevention, API access, Free/Paid Trials, Subscription pausing, and renewal options. | Limited subscription capabilities. |
| Account Management Portal | Buyers access order history, fulfillments, and subscriptions via a branded portal hosted by FastSpring. | Buyers manage orders and subscriptions through FastSpring's portal without branded customization. |
| Reporting | In-depth sales analysis with detailed filters and breakdowns. | Limited reporting; may hinder data-driven decisions. |
| FastSpring API | Extensive integrations with third-party systems. See API Reference. | Limited API capabilities. |
| Coupons | Robust coupon functionality without a built-in code generator. | Built-in coupon code generator. |
Migration steps
Follow the steps below in order. Steps 1 through 6 are required; steps 7 through 10 are optional depending on your integration needs.
Step 1 — Request a Contextual Store
FastSpring can migrate your existing Classic subscriptions to your new Contextual Store at no additional cost.
Submit a support case at community.fastspring.com and include:
| Field | Details |
|---|---|
| Base URL | The shared subdomain for your Contextual Storefronts (e.g., yourexamplestore in yourexamplestore.onfastspring.com). This cannot be changed after it is set. |
| Support name | What to call your support team when directing consumers to you. |
| Support address | The contact address to provide consumers for support. |
| Pricing mode | Gross (FastSpring deducts applicable taxes from non-USD prices) or Net (FastSpring adds applicable taxes). See Gross and Net Pricing Modes. |
Step 2 — Update user permission access
Your Contextual Store is separate from your Classic Store, so you may need to grant team members access.
- Users with the Administrator or Accountant role automatically receive the same level of access to the new Contextual Store.
- All other team members must be granted access through the FastSpring app.
Team members can log in at app.fastspring.com. For full instructions, see Users, Roles, and Types of Access.
Step 3 — Set up your storefronts
Your Contextual Store includes a Web Storefront and a Popup Storefront. Customize them to fit your brand, and create additional Storefronts as needed.
| Guide | Description |
|---|---|
| Storefronts overview | Understand the difference between a Store and a Storefront. |
| Popup Storefronts | Learn the basics of Popup Storefronts. |
| Embedded Storefronts | Learn about Embedded Storefronts. |
| Feature comparison | Compare Web, Popup, and Embedded Storefront capabilities. |
| Customize your Web Storefront | Control the look and feel of your Web Storefront. |
| Account Management portal | Style the customer portal via your store's default Web Storefront. |
Step 4 — Set up your products
Create a product record for each item you sell through FastSpring. The core concept is the same as in Springboard.
- Managing Your Products — covers key changes to how you interact with products in Contextual.
- Fulfillments — covers license key generation and download hosting.
Step 5 — Customize consumer-facing email messages
FastSpring automatically sends consumers notifications for events like purchases and cancellations. In Contextual, all messages use a unified templating system — you can brand them all at once with just a few tweaks.
- Customer Notifications — overview of all automated messages.
- Email Template Elements — reference for template customization.
- Add your logo — brand your email notifications.
Step 6 — Place test orders
Verify that your Storefront's products and fulfillments are working before going live.
- Navigate to your Storefront and place a test order using your own email address.
- Confirm you received the receipt and any fulfillment items (license keys, downloads, etc.).
See Placing Test Orders for detailed instructions and failure scenarios.
Step 7 — Set up promotions (optional)
- Coupons — offer discount codes for specific products or purchases.
- Product Discounts — apply automatic discounts without requiring a code.
- Product Offers — suggest related items and upgrades during checkout.
Step 8 — Set up webhooks (optional)
Webhooks replace the Vendor Notifications feature from Classic. Subscribe to HTTP notifications when specific events occur in your store.
Recommended events to start with:
| Event | Sent when |
|---|---|
| order.completed | An order succeeds |
| subscription.activated | A new subscription is created |
| return.created | A refund or return is processed |
| subscription.canceled | A subscription is canceled |
| subscription.deactivated | A subscription is deactivated |
| account.created | A new customer account is created |
See Webhooks Overview for full setup instructions.
If you prefer email-only notifications, Seller Notifications lets you manage the notifications you previously configured in Classic.
Step 9 — Set up API integrations (optional)
The FastSpring API for Contextual Stores has been redesigned. Key differences from the Classic API:
- A single set of credentials is associated with each Store (no dedicated API users).
- All requests go to
https://api.fastspring.com/{endpoint}.
Use the API to create integrations with your back-end systems or third-party services. All API interactions occur on the server side for security.
See FastSpring API Reference for full documentation.
Step 10 — Configure third-party integrations (optional)
To integrate your Contextual Store with third-party solutions such as Google Ads or Mailchimp, go to the Extensions tab in the FastSpring app.
See Extensions for a full list of available out-of-the-box integrations.
Frequently asked questions
Common questions from sellers migrating from Classic to Contextual Commerce.
Why move to Contextual?
Classic remains a legacy product that FastSpring no longer actively develops. At some point in the future, there may be changes to the platform lineup, including a potential transition away from Classic. The Contextual platform offers a wide array of features and functionality designed to help sellers scale their businesses.
Can I still access my historical data after migration?
Yes. Your historic data remains accessible via the Classic API or Springboard. Active subscriptions will generate data within the Contextual platform going forward.
How do I start the migration?
Submit a support ticket to request a Contextual Store. Our technical team will guide you through the rest of the process. See Step 1 above.
Will there be any downtime during migration?
No. The migration process is offline and will not impact your business operations.
What data is migrated?
Your product catalogs and subscriptions are migrated. Historical transaction data remains in the Classic Store and is not migrated to Contextual.
Does the migration cost anything?
No. Upgrading to Contextual Commerce is entirely free of charge.
Will my subscribers be notified about the migration?
No. Subscribers are not notified of the migration, and they do not need to resubmit payment details.
Can I keep using my Classic third-party integrations?
The Contextual platform integrates seamlessly with third-party solutions. Review the Extensions tab in the FastSpring app to see available integrations and configure them for your Contextual Store.