Ionic Appflow is available to existing customers only until December 31, 2027 — roughly sixteen months from the date of this post — and new sales ended in February 2025. Sixteen months is comfortable if you start now and uncomfortable if you start next summer, because every Ionic team in the same position will be looking for the same help at the same time. Here is the calendar we are putting in front of our clients.
Q3 2026 (now): know your exposure
- Inventory every app, channel, build configuration, and environment in your
Appflow dashboard, and every
cordova-plugin-ionic/@ionic/appflowreference in code - Record who holds the signing certificates, provisioning profiles, and API tokens that currently live in Appflow
- Decide your target stack: live updates via Capgo or Capawesome Cloud; native builds via GitHub Actions, Codemagic, or Bitrise; submission via fastlane
- Check your Capacitor major. Capacitor 8 is current; if you are on 5 or earlier, an upgrade belongs in the plan before the live-update swap
- Budget and owner assigned
We do the inventory step for free as an Appflow-exposure audit.
Q4 2026: live updates first
Live updates are the piece that fails most visibly (a white screen) and the piece with the most moving parts (channels, signing, rollback), so they go first.
- Install the new updater alongside the Appflow plugin behind a feature flag
- Recreate channels one-for-one; bake the channel into each native build
- Generate and store the update signing/encryption key in CI
- Ship a native release containing both updaters; push the first staging update through the new provider
Our tutorial Migrating Live Updates off Ionic Appflow walks through each step.
Q1 2027: native builds and store submission
- Stand up fastlane
match(iOS) and a keystore-in-secrets flow (Android) - Get one green signed build of each platform from CI, uploaded to TestFlight and the Play internal track
- Wire PR preview builds so QA stops depending on Appflow's build queue
- Document the pipeline in the repo
The pipeline we set up is in CI/CD for Capacitor apps with GitHub Actions + fastlane.
Q2 2027: parallel run and cutover
- Ship two consecutive releases through both pipelines
- Move production live updates to the new provider at 10%, then 50%, then 100%
- Run one real hotfix end to end through the new path — a live update and a native build — before you declare victory
Q3 2027: decommission
- Remove the Appflow plugin and config; ship the native release without it
- Delete Appflow CI steps; revoke Appflow tokens; rotate any credentials that were stored there
- Export build logs or artifacts you are required to retain
- Update the runbook: provider, channel map, key rotation owner
Finishing in Q3 leaves a full quarter of margin. We recommend using it rather than planning to need it.
Q4 2027: margin
If you are reading this in Q4 2027 with Appflow still in production, the order changes: live updates get switched first (that is what can strand users), native builds second, and the clean-up happens in 2028. It is still doable, but it is a project with a hard deadline rather than a managed migration.
What this costs
For a single app on a current Capacitor with one or two channels, the whole programme is typically two to six weeks of engineering spread across the quarters above. Apps that also need a Capacitor upgrade, or that carry a lot of Cordova plugins, take longer — the Cordova → Capacitor checklist is usually the extra work.
Print this
Put the quarter headings in your roadmap now. The Appflow shutdown is the rare platform deadline with a fixed date and a known fix; the only way to get it wrong is to schedule it for next year.