Limits & requirements
Find file, row, field and batch limits before starting a workflow.
On this page
Supported sizes and requirements
- 100 field groups, 200 fields per group and 1 MB schema JSON.
- Three composite levels, 20 children per container, 100 rows and shared rendering/value limits.
- 50 objects per migration, five-object batches and a 2 MB journal; options are reviewed as a single destination.
- 20 controls per authored block; 50 block and 50 listing definitions; 40 listing items per page.
- CSV reviews: up to 500 rows, 32 columns and a 2 MiB file. Up to 10 supported fields per saved mapping. A missing or renamed required column needs a corrected file or mapping.
- Pro replacement jobs: 2,000 posts, 25 per chunk, five retained jobs and 32 MB of snapshots per job. Undo requires unchanged recorded values.
- Content transfer: 50 posts, 100 attachments, 8 MB per file and 32 MB of media. PHP ZIP/fileinfo and private temporary storage required. Unsupported blocks, reciprocal graphs and object-specific locations need separate handling.
- Optional custom storage retains a metadata mirror. Protected transactional workflows require MySQL or MariaDB with InnoDB tables; migrations also require advisory-lock support. SQLite is not supported for these operations.
- These are bounded workflows, not a full-site clone or whole-site health certificate. Test your host, theme and other plugins on staging.