Migration snapshot
Maintenance modePlatform
an Ionic Appflow
Hard shutdown confirmed December 31, 2027. Ionic support docs state: 'All Appflow features and services will be sunset effective December 31, 2027,' with possible 'build pipeline failures and/or live update failures resulting in whitescreens' before that date. No new customers accepted; existing customers receive bug fixes only — no new features. Ionic Enterprise plugins (Identity Vault, Auth Connect, Secure Storage) discontinued alongside Appflow.
Typical timeline
2–4 weeks
Typical cost
$13K–$25K (agency, fixed)
Why teams leave an Ionic Appflow
Appflow's shutdown is not speculation — Ionic's own support documentation is explicit. The question is not whether to migrate but how soon, and whether to move before the pre-deadline build failures Ionic itself warns about.
Confirmed hard shutdown December 31, 2027
Ionic support docs are explicit and public. This is not a soft EOL or a sunset rumor — Appflow features and services are confirmed to end on December 31, 2027. No extension has been announced.
Build pipeline failures possible before the deadline
Ionic's own documentation warns of 'build pipeline failures and/or live update failures resulting in whitescreens' that may occur before December 2027. Waiting until the deadline risks production outages ahead of schedule.
No new features, permanently
Appflow is feature-frozen today. Any capability gap your team identifies now — faster build times, new Capacitor plugin support, improved OTA delivery — will never be filled. Capawesome offers Apple Silicon M4 runners claiming 3–5× faster builds available today.
Identity Vault and Auth Connect discontinued now
Enterprise security plugins Identity Vault and Auth Connect are discontinued alongside Appflow. If your app uses either, migration scope is larger than a simple pipeline swap and should start immediately — do not wait for the 2027 deadline.
Drop-in alternatives exist and are cheaper
Capawesome (from $9/mo) and Capgo (open-source, from ~$12/mo) replace Appflow's core CI/CD and live-update functions today. Both are actively maintained and purpose-built for Capacitor apps.
What can you actually take with you?
This is the best-case exportability scenario in the mobile builder category: Appflow is a CI/CD service, not an app builder. Your source code, design, and logic have always lived in your own Git repository.
| Asset | Can you export it? | How | Notes |
|---|---|---|---|
| Data | Yes | Not applicable — Appflow is a build/deploy/live-update pipeline; it does not store application data | Your app data lives in your own backend (Firebase/Supabase/custom database); Appflow has never held user data |
| Code | Yes | Your Ionic/Capacitor/Cordova source code is in your own Git repository — it has always been there | Nothing to export from Appflow itself; migration work is replacing the build pipeline that reads your existing repo |
| Design/UI | Yes | App UI source files are in your own Git repository alongside the application code | No design assets live in Appflow; your Figma files, assets, and component libraries are self-managed |
| Logic/Workflows | Yes | All business logic is in your owned repository as TypeScript/JavaScript source files | Appflow-specific workflow configurations (build configs, environment variable definitions) need to be re-created in the new provider's dashboard |
| Users & Auth | Yes | Auth is handled by your own backend (Firebase Auth / Supabase Auth / custom); Appflow does not hold user data or password hashes | Password hashes are in your own auth system; no auth migration required — only pipeline configuration changes |
| Signing Certificates | Yes | Export iOS provisioning profiles, distribution certificates, and Android keystores from the Appflow dashboard before shutdown | Critical: losing signing certificates means re-submitting with a new bundle ID, which loses app listing history; export immediately |
Swipe the table sideways to see the full breakdown.
Where each piece moves in code
Appflow's services map directly to modern Capacitor CI/CD tools — this is a pipeline replacement, not a framework or architecture change.
an Ionic Appflow
Appflow Cloud Builds
In code
Capawesome Cloud Builds (from $19/mo) or GitHub Actions + Fastlane (self-managed)
Capawesome runs Apple Silicon M4 runners for 3–5× faster builds; GitHub Actions is free for public repos and low-cost for private
an Ionic Appflow
Appflow Live Updates (OTA)
In code
Capgo Live Updates (open-source; from ~$12/mo) or Capawesome Live Updates (from $9/mo)
Both are drop-in replacements for Appflow's live update SDK; require an SDK swap and channel reconfiguration in the app
an Ionic Appflow
Appflow App Store Automation
In code
Fastlane + EAS Submit, or manual App Store Connect / Play Console submission
Fastlane is the industry-standard open-source tool for automated store submission; EAS Submit from Expo works with Capacitor apps
an Ionic Appflow
Identity Vault (discontinued)
In code
@capacitor-community/biometric-auth + secure storage alternatives
No direct drop-in replacement exists; evaluate @capacitor/preferences for basic storage or SQLCipher-backed libraries for secure storage requirements
an Ionic Appflow
Auth Connect (discontinued)
In code
@capacitor/oauth2 or platform-native OAuth flows
Standard Capacitor OAuth plugin covers most Auth Connect use cases; test your specific OAuth provider flows before committing
an Ionic Appflow
Ionic Secure Storage (discontinued)
In code
@capacitor/preferences (basic) or SQLCipher-backed storage libraries
Evaluate encryption requirements; @capacitor/preferences is unencrypted; SQLCipher provides AES-256 encryption at rest
an Ionic Appflow
Appflow Environment Variables
In code
CI/CD secrets in GitHub Actions or Capawesome dashboard
Migrate all environment variables and API keys to the new provider before deprecating Appflow credentials
The migration roadmap
The Appflow migration is uniquely scoped: you own all your source code, so this is pipeline replacement work. The roadmap is faster than any other mobile platform migration and should start this week — not at the 2027 deadline.
Backup and Audit (Do This Today)
Day 1–3- Export all signing certificates, iOS provisioning profiles, and Android keystores from the Appflow dashboard immediately
- Audit whether the app uses Identity Vault, Auth Connect, or Ionic Secure Storage — these require the most work and are discontinued now
- Document all Appflow environment variables and CI/CD configuration that must be recreated in the new provider
- List all live update channels and their version configurations
Watch out: Signing certificate loss is catastrophic — losing them means re-submitting with a new bundle ID and losing your app store listing history. Back them up before any other action.
Pipeline Evaluation and Selection
Week 1- Sign up for Capawesome or Capgo free trial and run a test build of your app
- Compare Capawesome ($9–$19/mo, M4 runners, faster builds) vs Capgo (~$12/mo, open-source, strong live-update focus) based on your use case
- Test live update delivery with a canary release to a subset of devices before cutting over production
- Migrate from Apple ID + app-specific-password to App Store Connect API key authentication in the new provider
Enterprise Plugin Replacements (If Needed)
Weeks 2–4- Replace Identity Vault with @capacitor-community/biometric-auth and evaluate secure storage alternatives
- Replace Auth Connect with @capacitor/oauth2 and test all OAuth provider flows
- Replace Ionic Secure Storage with @capacitor/preferences or a SQLCipher-backed alternative based on encryption requirements
- Run full regression testing on all auth and storage flows after plugin replacement
Watch out: Enterprise plugin replacement is the longest workstream; start it in parallel with pipeline evaluation, not sequentially after
Cutover and Monitoring
Week 3–4 (or after enterprise plugin work)- Switch production builds to the new provider; deprecate Appflow build configurations
- Migrate all live update channels to Capawesome or Capgo; send a forced update notification to deployed apps
- Set an internal calendar reminder: hard deadline December 31, 2027; internal target Q2 2027 at latest
- Document the new pipeline configuration in your team's runbook
Three ways to migrate — honestly
Every path has a real trade-off. Here is what each costs, how long it takes, and where it bites.
DIY (self with AI tools)
$9–$50/mo (new pipeline tools) + time
1–3 weeks for pipeline; 4–8 weeks if enterprise plugins need replacement
Fits
Teams with an existing DevOps or mobile engineer who understands CI/CD pipelines, certificate management, and Capacitor plugin ecosystems
Risks
Signing certificate management is unforgiving — a mistake means a new bundle ID and loss of app listing history. Enterprise plugin replacement requires native mobile testing expertise.
Freelancer
$1K–$5K
1–4 weeks
Fits
Teams without internal mobile DevOps capability; useful specifically for certificate migration, Fastlane setup, and enterprise plugin replacement
Risks
Vet the freelancer on Capacitor + Fastlane specifically, not just general mobile development. Many mobile freelancers are unfamiliar with CI/CD certificate management.
Agency (RapidDev)
Done-for-you$13K–$25K fixed
6–10 weeks
Fits
Teams that also need enterprise plugin replacement (Identity Vault, Auth Connect), want a fully documented new pipeline, or need the migration completed with a firm deadline guarantee
Risks
Higher cost is justified primarily when enterprise plugin replacement is in scope; pure pipeline swap is achievable DIY for teams with any DevOps experience
The real risks — and how to defuse them
Pre-deadline build pipeline failures
Mitigation: Ionic explicitly warns of possible build failures and whitescreens before December 2027. Migrate the build pipeline within 60 days, not at the deadline. Every production release between now and December 2027 that runs through Appflow is a reliability risk.
Signing certificate loss on migration
Mitigation: Export iOS provisioning profiles, distribution certificates, and Android keystores from Appflow immediately. Store them in a secure vault (1Password, AWS Secrets Manager). Losing these requires re-submitting with a new bundle ID — which loses your app store listing, reviews, and download count.
Identity Vault and Auth Connect replacement scope
Mitigation: These are discontinued now, not at the 2027 deadline. If your app uses either, start evaluating @capacitor-community/biometric-auth and @capacitor/oauth2 immediately. Budget a dedicated testing sprint — these involve native capabilities that require device testing.
OTA live update channel disruption
Mitigation: Existing deployed apps are configured to pull updates from Appflow's servers. Plan a forced update notification that migrates live apps to the new provider's channel before Appflow shuts down. Test this flow with a canary group first.
Deadline creep ('18 months is plenty of time')
Mitigation: Set an internal hard deadline of Q2 2027 — well before December 31, 2027 — to allow buffer for testing, edge cases, and App Store review cycles. Add it to your team roadmap calendar today.
Should you actually migrate?
Migrating is a real project. Sometimes staying is the right call — here is the honest split.
Stay if
- Your app has no Identity Vault, Auth Connect, or Ionic Secure Storage dependency and you have a simple Capacitor app — you can use Appflow's remaining months while running a low-cost Capawesome or Capgo evaluation in parallel
- Migration is already planned for Q1–Q2 2027 and your team has a documented internal deadline on the calendar — 'staying for now' with a firm plan is a legitimate posture if not a permanent one
- Your migration budget is not available until a future quarter and you have no Identity Vault/Auth Connect dependencies — acceptable only if you set a firm internal deadline today and do not start new Appflow-dependent feature work
Migrate if
- Your app uses Identity Vault, Auth Connect, or Ionic Secure Storage — these are discontinued now, not at December 2027; migration cannot wait
- Your build pipeline has already experienced reliability issues (Ionic warns these are coming before the deadline)
- You want 3–5× faster build times today using Capawesome's Apple Silicon M4 runners versus Appflow's older infrastructure
- December 31, 2027 is a hard stop regardless — there is no permanent 'stay' option; the only question is timing
Our honest verdict
This is the rare migration where you already own all your source code. Replacing Appflow is pipeline work, not a rebuild — and the December 31, 2027 deadline is firm. The only real decision is how much buffer time to give yourself before the deadline. Q2 2027 internal target is the recommended posture.
Do this today: pre-migration checklist
Whatever path you choose, protect yourself first. Work through this before you touch a line of code.
Back up all signing certificates, keystores, and provisioning profiles from Appflow today
Losing signing credentials means re-submitting with a new bundle ID, which loses app listing history and download count — irreversible
Audit whether the app uses Identity Vault, Auth Connect, or Ionic Secure Storage
These enterprise plugins are discontinued now alongside Appflow; they require replacement work that cannot be deferred to 2027
Sign up for a Capawesome or Capgo free trial and run a test build today
Validates that your app builds successfully on the new pipeline before any commitment; surfaces certificate or configuration issues early
Test Capawesome or Capgo Live Updates with a canary release before cutting over production
Live update channel migration affects all deployed app instances; a canary test catches configuration issues before they reach all users
Migrate from Apple ID + app-specific-password to App Store Connect API key authentication
Appflow used the legacy Apple ID authentication flow; the new provider requires App Store Connect API keys — a one-time migration required for continued automated store submission
Set an internal migration deadline of Q2 2027 and add it to the team roadmap calendar
Buffer for testing, edge cases, and unexpected delays; missing the December 31, 2027 deadline risks production whitescreens
Notify your team: December 31, 2027 is a hard stop with no extension announced
Everyone who deploys, releases, or maintains the app needs to know; 'I didn't know' is how teams miss confirmed deadlines
Frequently asked questions
Is Ionic Appflow really shutting down?
Yes. Ionic's own support documentation states: 'All Appflow features and services will be sunset effective December 31, 2027.' No new customers are being accepted. Existing customers receive bug fixes only — no new features are being developed. The documentation also warns that build pipeline failures and live update failures ('whitescreens') may occur before that deadline.
Do I need to export my app code from Appflow?
No — your app source code has never been inside Appflow. Appflow is a CI/CD build-and-deploy service. Your Ionic/Capacitor/Cordova source code lives in your own Git repository. What you do need to export immediately are your signing certificates, iOS provisioning profiles, and Android keystores, which Appflow manages on your behalf.
What are Capawesome and Capgo, and do they replace Appflow?
Yes, both are purpose-built drop-in replacements for Appflow's core functions. Capawesome (from $9/mo) offers cloud builds with Apple Silicon M4 runners and live updates. Capgo is open-source with a hosted option from ~$12/mo, focused specifically on Capacitor live updates. Both are actively maintained and available today. Most teams migrate to one of these two.
How long does migrating from Appflow take?
For a straightforward pipeline swap (no Identity Vault/Auth Connect/Secure Storage), typically 2–4 weeks including testing and certificate migration. If your app uses Identity Vault, Auth Connect, or Ionic Secure Storage (all discontinued), budget an additional 4–8 weeks for enterprise plugin replacement and regression testing.
What happens to my Identity Vault and Auth Connect if I stay?
Both are discontinued alongside Appflow. There is no 'stay' option for Identity Vault and Auth Connect — they are already in end-of-life status. You need to evaluate @capacitor-community/biometric-auth as an Identity Vault replacement and @capacitor/oauth2 as an Auth Connect replacement, regardless of when you migrate the build pipeline.
What happens to users and their passwords when I migrate?
Nothing changes for users. Appflow has never held user data, auth credentials, or passwords — those live in your own backend (Firebase Auth, Supabase Auth, or a custom auth system). The migration replaces your build pipeline and live-update delivery system only. From a user perspective, the app functions identically before and after.
Should I wait until 2027 to migrate?
No. Ionic explicitly warns of possible build pipeline failures and whitescreens before December 31, 2027 — not just on that date. Waiting until the deadline means production risk in the months before it. The recommended posture is to set an internal target of Q2 2027 at the latest, which gives buffer for testing and edge cases. If you use Identity Vault or Auth Connect, start now.
Can RapidDev help with the Appflow migration?
Yes. RapidDev handles Appflow pipeline migrations at a fixed price of $13K–$25K completed in 6–10 weeks. This is most cost-effective when enterprise plugin replacement (Identity Vault, Auth Connect, Ionic Secure Storage) is in scope alongside the pipeline swap. For teams that only need a pipeline swap, DIY with Capawesome or Capgo is genuinely feasible. Book a free scoping call to assess your specific situation.
We migrate no-code apps to production code
- Fixed price — $13K–$25K (agency, fixed)
- No data loss, no downtime
- You own 100% of the code
30-min call. Quote within 48 hours.
