Ionic Enterprise Sdk Migration

Ionic Enterprise SDK Migration

Migrate Capacitor apps from discontinued Ionic Enterprise SDK plugins to Capawesome alternatives.

Plugin Mapping

All Capawesome replacement plugins require a Capawesome Insiders license.

Prerequisites

1. Capacitor 6, 7, or 8 app.
2. Node.js and npm installed.
3. A Capawesome Insiders license key.

Agent Behavior

• Auto-detect dependencies. Scan package.json for Ionic Enterprise packages before asking the user which plugins to migrate.
• One plugin at a time. Complete the full migration for one plugin before starting the next.
• Use the capacitor-plugins skill for installation. Delegate plugin installation and platform configuration to the capacitor-plugins skill. Only handle migration-specific steps (uninstall, code replacement) in this skill.
• Preserve existing behavior. When replacing API calls, maintain the same functional behavior (e.g., same scopes, same stored keys, same database schema).

MCP Server

The Capawesome MCP server serves the current Capawesome documentation, so it is always ahead of the guidance bundled with this skill.

• If the Capawesome MCP tools are available, call search_docs for the topic and read the matching page with get_doc_page before applying the guidance below. Where the two disagree, follow the documentation.
• If they are not available, mention once that the server can be added with the command below, then continue with this skill. Never block on it.

claude mcp add --transport http capawesome "https://mcp.capawesome.io/mcp"

The documentation tools need no account and no token. See the capawesome-mcp skill for full setup, including the Capawesome Cloud tools.

Procedures

Step 1: Detect Ionic Enterprise Dependencies

Read package.json and check for these packages:

• @ionic-enterprise/auth → Auth Connect
• @ionic-enterprise/identity-vault → Identity Vault
• @ionic-enterprise/secure-storage → Secure Storage

If none are found, inform the user that no Ionic Enterprise plugins were detected.

If multiple are found, list them and ask the user which to migrate first, or migrate all sequentially.

Step 2: Set Up the Capawesome npm Registry

Check if the @capawesome-team npm registry is already configured:

npm config get @capawesome-team:registry

If not configured, guide the user through setup:

npm config set @capawesome-team:registry https://npm.registry.capawesome.io
npm config set //npm.registry.capawesome.io/:_authToken <YOUR_LICENSE_KEY>

Ask the user for their license key if needed. Wait for confirmation before continuing.

Step 3: Migrate Each Plugin

For each detected Ionic Enterprise plugin, read the corresponding reference file and follow the migration steps:

• Auth Connect → Read references/auth-connect-migration.md
• Identity Vault → Read references/identity-vault-migration.md. Before changing code, ask the user whether they want to preserve existing stored data (keep both plugins installed for a transition period and migrate data at runtime) or make a hard cutover (drop the old data and switch immediately). The chosen strategy changes which steps run — see the strategy section in the reference file.
• Secure Storage → Read references/secure-storage-migration.md

Each reference file contains:

1. Feature mapping table (Ionic API → Capawesome API)
2. Key differences to be aware of
3. Step-by-step code replacement with before/after examples

For plugin installation and platform-specific configuration (Android permissions, iOS plist entries, Proguard rules, etc.), use the capacitor-plugins skill.

Step 4: Search for Remaining Ionic Enterprise Imports

After completing all migrations, search the codebase for any remaining Ionic Enterprise imports:

grep -r "@ionic-enterprise" --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx"

If any are found, replace them with the corresponding Capawesome imports.

Step 5: Clean Up and Verify

1. Remove all Ionic Enterprise packages from package.json:

npm uninstall @ionic-enterprise/auth @ionic-enterprise/identity-vault @ionic-enterprise/secure-storage

Only uninstall packages that were actually installed.

Identity Vault exception (preserve-data strategy): If the user chose to preserve existing data, do not uninstall @ionic-enterprise/identity-vault here. It can only export the old data while both plugins are installed, so it stays until the runtime data migration has shipped and run on devices, then is removed in a later release (see steps 2 and 9 in references/identity-vault-migration.md). For a hard cutover, Identity Vault was already uninstalled during its migration.

2. Sync the project:

npx cap sync

3. Verify the project builds successfully on all platforms.

Error Handling

• Capawesome registry not configured: If npm install fails with a 404 or authentication error for @capawesome-team/* packages, verify the npm registry is configured correctly (Step 2).
• Missing Capawesome Insiders license: All replacement plugins require a Capawesome Insiders license. Direct the user to capawesome.io/insiders to obtain one.
• Identity Vault session management: The Capawesome Vault plugin natively supports auto-lock via the lockAfterBackgrounded option and lock/unlock event listeners, which map closely to Identity Vault's lockAfterBackgrounded, onLock, and onUnlock. Custom-passcode vaults have no direct equivalent and must be rebuilt with application logic. See references/identity-vault-migration.md.
• Secure Storage encryption: Ionic Secure Storage has built-in encryption. Capawesome SQLite encryption requires additional platform configuration (SQLCipher). If the user needs database encryption, guide them through the SQLite encryption setup in the capacitor-plugins skill reference.
• Web platform limitations: Capawesome Secure Preferences stores values unencrypted in localStorage on the web. This is for development only and should not be used in production.

Related Skills

• capacitor-plugins — Referenced throughout this skill for plugin installation and platform configuration.
• ionic-appflow-migration — If the project also uses Ionic Appflow (Live Updates, Native Builds, App Store Publishing), use this skill to migrate to Capawesome Cloud.
• capawesome-mcp — Connect an MCP client to the hosted Capawesome MCP server for always-current documentation and Capawesome Cloud management.