Migrate your iOS app to use the BlackBerry Dynamics SDK for iOS

After you prepare your migration environment, you use your AI agent to run prepackaged prompts in a specific order. The agent executes prompts from dynamics-migration-tool/prompts/, records progress in bootstrap.json, and stops at different stages so you can review what has been done. For more information about each prepackaged prompt, see Prepackaged migration prompts.
  • Prepare your migration environment. Copy the migration prompt from migrate.sh.
  • Verify that you have defined the entitlement ID (GDApplicationID) and entitlement version (GDApplicationVersion) for your app. You will need to provide these values when your agent runs prompt 02-configure-info-plist.md.
  1. Open your project in a new workspace with the required AI agent permissions and start a new chat session.
  2. Paste and run the migration prompt that was printed by migrate.sh.
  3. When prompt 00pre runs, if you are prompted for Git baseline initialization, give your consent. Verify that dynamics-migration-tool/output/bootstrap.json and dynamics-migration-tool/output/target-map.json exist, are valid JSON, and share the same runId.
  4. When prompt 00 runs, review and confirm the migration plan before the agent makes application code changes.
  5. When prompt 02 runs, provide your GDApplicationID, GDApplicationVersion, and app setup type. Confirm that the agent registers BlackBerry Dynamics URL schemes with the native bundle identifier, not GDApplicationID.
  6. Allow the agent to run each applicable prompt through prompt 11, then prompt 10. Accept, reject, or question changes as necessary at each step.
    After each applicable prompt, the agent runs prompt-scoped validation when required, then record-prompt-execution.sh. Do not edit bootstrap.json.executedPrompts[] or migration-plan-state.json manually. If the agent tries to invent APIs, instruct it to use only APIs that are documented in the steering files and API catalog.
  7. Run prompt 10 to generate migration-report.json (schema v2.1.0), complete full validation, and record prompt 10 completion.
    After prompt 10, generate the toolkit beta-feedback artifact with dynamics-migration-tool/tooling/generate-tool-analysis-report.sh. Optionally, run prompt 12 to generate a migration retrospective.
Validate the migration to review validation results and migration reports, and to perform final cleanup. For troubleshooting guidance, see Troubleshooting the migration.