Migration - Analyze

Migration - Analyze
Migration Environment

Depending on your architecture, different setups for the migration environment might make sense, for example:

  • Dedicating an existing test/QA-environment for the migration
  • Deploying a new environment specifically for the migration
  • Local environment using a separate database for the migration
The main requirements are that the environment is dedicated without other simultaneous users and it's possible to deploy a custom version for the migration. You can consult the AI agent about the options and ask it to document the choice for future reference.

Connect the database

Connect the test environment database to OINO.cloud and create a MCP-server for it. Leave Allow Schema Manage and Allow Data Manage off. The existing tables don't have OINO.cloud APIs yet, so the agent first runs provision_database to create read-only tokens for them.

Analyze source code

Start an AI agent project where you add the MCP-server and OINO.cloud app migration skill and the app source code. Then just tell the agent you want to migrate the application and what are the new architecture and requirements. The agent will then analyze the source code and create user stories and test specifications for the application.

Review user stories and test specifications

You should review the user stories and test specifications generated by the agent to ensure nothing important is missing or misunderstood. Ask the agent to document a test plan with order and dependencies of the test specifications.

Before
  • OINO.cloud account
  • application test environment that can be dedicated to the migration
  • SQL user and password with read-only access to the test environment database
  • firewall rule allowing access to the test environment database from OINO.cloud API
  • access to the application's source code
  • an AI agent where you can add skills
  • migration architecture documentation

After
  • user story documentation with test specifications
  • test plan documentation with order and dependencies

Nothing is written to your database in this phase — a read-only connection is enough.

Next: Instrument the app so each of those actions reports when it runs.