How do I bulk-export Skio subscriber and consent data before switching to a different subscription app?
Skio exports subscriber data three ways: self-serve CSV files for subscriptions, orders and audit logs; a GraphQL API capped at 2,000 requests per minute per token; and a REST bulk export interface added 27 January 2026 (all verified September 2026). Those exports document no consent fields. Marketing consent lives on the Shopify customer record, which you already own.
The three export paths, in the order you should use them
- Self-serve CSV, from Tools then Data Export in the Skio dashboard. Three exports: active and inactive subscriptions with line detail, recurring and new subscription orders for a chosen period, and audit logs by event type. Filters cover created-at and next-billing-date ranges, defaulting to the past month, so widen them or you will export a month and think it is the book (per Skio's exports guide, September 2026).
- The GraphQL API, for anything the CSV shape does not fit. Token auth generated in the dashboard, and three limits worth designing around: 4 levels of query depth, 100 nodes per request, and 2,000 requests per minute per token (per Skio's API reference, September 2026).
- The REST bulk export interface, added 27 January 2026. Cursor-based endpoints for orders, subscriptions, storefront users and products, filterable by date range or ID. Skio positions it as the path for merchants hitting query limits, timeouts or pagination problems on GraphQL exports (per Skio's changelog, 27 January 2026).
The trap in the subscriptions CSV
Each row is one subscription line, not one subscription (per Skio's exports guide, September 2026). A subscriber on a three-product box produces three rows. Every count built on a naive row count of that file will be wrong, and it will be wrong in the direction that makes your subscriber base look larger than it is, which is exactly the direction nobody audits.
Consent is not Skio's to export, and that is good news
Email and SMS marketing consent state lives on the Shopify customer record and is written through Shopify's own consent mutations, customerEmailMarketingConsentUpdate and customerSmsMarketingConsentUpdate (per shopify.dev, September 2026). Shopify's customer export carries it. So the consent half of this question is answered by a platform you are not leaving.
What is genuinely app-side is consent captured inside the Skio experience: SMS interactions appear in the audit log event types, and any consent your portal or checkout widget collected that was never written back to the Shopify customer record exists only in Skio. Export the audit log for the SMS and consent event types specifically, and reconcile it against the Shopify customer list before you cancel the app. If a subscriber's consent exists only in the app, it leaves with the app.
What no export will give you
Payment methods. Skio's documented exports do not carry them, and they could not: the token belongs to a vault, not to a CSV. Portal customizations, churn-save rules and dunning configuration are also not export artifacts. Screenshot them, or re-specify them, because they are the part of the rebuild nobody quotes.
Do the export before you give notice, not after. Export access ends with the subscription.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Run the export on day one of the contract, not on the way out. An export you have never tested is an assumption, and the moment you need it is the moment you are least able to wait three business days for support.
- What we’ve seen: The line-versus-subscription row count is the single most common reporting error we find in migration planning decks. The second is treating the audit log as optional, when it is the only place the consent and SMS event history lives.
- Where we disagree: The category treats data portability as a procurement checkbox, satisfied by the words "full data export" in a sales deck. Portability is a property of the specific fields you need on the day you leave. Payment tokens are the ones that matter, and no subscription app can export those.
- What this page adds: the three concrete export paths, their documented limits, and the fact that consent is a Shopify-side asset rather than a Skio-side one.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Our decision records