Prepare your migration environment

  1. Create a working copy of your app so that you can preserve the original project:
    cp -r /path/to/your-app /path/to/your-app-dynamics
cd /path/to/your-app-dynamics
  2. Verify that the working copy builds successfully:
    ./gradlew clean build

    Resolve any issues with the project before you continue. The migration toolkit requires a working Gradle build.

  3. Copy the migration toolkit (dynamics-migration-tool) into the root of your working copy:
    cp -r /path/to/dynamics-migration-tool ./dynamics-migration-tool
  4. Run the setup script for your AI agent:
    chmod +x dynamics-migration-tool/tooling/*.sh
./dynamics-migration-tool/tooling/migrate.sh --agent <agent_name>

    For <agent_name>, type cursor, kiro, or codex. If you are using another agent (for example, GitHub Copilot or Cody), type generic. If you want to list individual prompt files for manual execution, add --list-prompts.

    If you specify --agent generic, note that you must do the following for each prompt that you will run in the migration process:
    1. Paste steering/00-context.md as initial context.
    2. Paste the relevant steering file for the prompt.
    3. Paste the prompt file.
    4. Review and accept changes.
    The script verifies the project structure, installs steering or rules for the agent, and prints a ready-to-paste migration prompt. Copy the migration prompt for use in the next task (Migrate your Android app to use the BlackBerry Dynamics SDK). Steering or rule files are installed in these locations:
    • Cursor: .cursor/rules/
    • Kiro: .kiro/steering/
    • Codex: AGENTS.md project instructions
Migrate your Android app to use the BlackBerry Dynamics SDK.