Skio Launch Process: Important Use-Cases to Notify About Skio Launch Process: Important Use-Cases to Notify About

Skio Launch Process: Important Use-Cases to Notify About

There are some use-cases when migrating to Skio from another subscription platform that are important for you to notify your Skio Sales / Launch engineer about prior to migrating to Skio. These use-cases are listed below, please be sure to review them in the event that they pertain to your store's current Subscription configuration.

 

  1. Migrating from outside of Shopify (WooCommerce, Magento, etc)
    If migrating subscriptions into Skio from a store that is currently not a Shopify store, such as a WooCommerce or Magento store, please be sure to notify your Skio Sales representative as well as your Skio Launch Engineer so that we can request the required access to your store's data in order to review it prior to migrating.

  2. Migrating from a Custom Subscription solution (ex. Stripe Subscriptions API, custom platform)
    If you currently process subscriptions / recurring payments using a custom-built platform, please be sure to notify your Skio Sales representative as well as your Skio Launch Engineer so that we can review your existing subscription data in preparation for migrating to Skio.

  3. Migrating from Smartrr subscriptions platform

  4. Migrating Prepaid subscriptions
    In some cases, some platforms require manual data verification regarding Prepaid subscriptions in order to properly migrate into Skio. Please be sure to mention this early in your Sales / Launch process to ensure that no details are overlooked.

  5. Migrating Bundles / Boxes
    Different subscription platforms format Bundle / Box related data in different ways. If you currently sell subscriptions for a Bundle / Box style product, please be sure to mention this to the Skio team so that we can evaluate your existing configuration.

Add comment

Please sign in to leave a comment.