Migrate your Android app to use the BlackBerry Dynamics SDK

After you prepare your migration environment, you will use your AI agent to run prepackaged prompts in a specific order. The agent will execute prompts from dynamics-migration-tool/prompts/, record progress in bootstrap.json, and will stop at different stages to allow you to 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 the first prepackaged prompt.
  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, confirm agent permissions and provide the entitlement ID and version. Verify that output/bootstrap.json exists and sdkProbe.dynamicsSdkResolvedVersion is populated.
  4. When prompt 00 runs, review and confirm the migration plan, then allow the agent to run each applicable prompt, including 11 and 03c, up to prompt 10. Accept, reject, or question changes as necessary at each step.
    If the agent tries to invent APIs, instruct it to use only APIs that are documented in the steering files.
  5. Run prompt 10 to generate the migration report and complete validation.
    If prompt 10 aborts with an execution plan gate failure, run the listed prompts again, or add a signed-off entry to deferredDomains[] in bootstrap.json, then run prompt 10 again.
Validate the migration to review validation results and migration reports, and to perform final cleanup. For troubleshooting guidance, see Troubleshooting the migration.