# Migrate an application

Validate schema, data, client behavior and recovery before migrating to ParticleDB.

Source: https://particledb.ai/operations/migration/

## Inventory the application

List tables, constraints, indexes, functions, extensions, triggers and migration tools. Record how clients handle transactions, parameters, errors and returned types.

## Test compatibility

A compatible driver does not imply complete compatibility with another database. Run representative SQL and schema changes against the release you plan to deploy. Check [feature limits](/reference/limits/) and [schema transactions](/sql/transactional-ddl/).

## Move a sample first

Create the destination schema explicitly. Load a small sample, verify types and values, and test the application's reads and writes. [Import and export](/guides/import-export/).

## Plan cutover

Choose a maintenance or synchronization strategy appropriate to the application. Verify counts, reconcile writes that occurred during the move, and preserve a rollback path. Do not assume cross-database atomic commits.

## Verify after cutover

Check errors, latency, permissions, background jobs and recovery. Keep the previous environment available according to your rollback plan until the migration is accepted.

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)
