Migration limits
Miglify applies plan limits, resource limits, and workflow-specific requirements to keep migrations predictable and verifiable.
Where current limits are published
Current numeric allowances for each plan — database rows, auth users, storage files, total storage size, and per-file size — are listed on the Pricing page, which is the source of truth for commercial limits.
Why limits exist
Limits keep a migration inside a range that can be validated, verified, and recovered predictably. They also make progress reporting and rollback coverage meaningful.
How limits affect a migration
- Preflight analysis reports detected resource counts before execution.
- If a detected value exceeds the applicable limit, Miglify surfaces the exact value.
- Blocking conditions must be resolved or approved before the migration can continue.
Workflow-specific requirements
Beyond plan limits, each workflow has its own requirements — such as available source code, destination authorization, or required Secrets. Those requirements are shown in the migration flow before you confirm.
Larger or complex migrations
Contact the Miglify team to review capacity and requirements for larger or more complex migrations.
Recommended first migration size
Keeping your first migration comfortably inside the applicable limits makes validation, verification, and rollback review faster.