An enterprise CMS migration moves pages, files, versions and settings to a new platform, and it stalls on database caps. The main limits are tight row widths, 16 MiB documents, packet ceilings and AEM Cloud ingestion ceilings. Marketing, development and content teams meet these caps during export, transfer and import. Wide landing pages break row rules, large videos break document rules, and full archives break destination quotas.
Official resources:
- Check Adobe Content Transfer Tool size prerequisites — Confirm whether your AEM repository size qualifies for automated cloud migration.
- Verify SQL Server maximum row and database sizes — Verify in-row byte and row-overflow limits before mapping CMS content to SQL Server.
Table of Contents
- Do wide content rows survive export?
- Will large pages break in transit?
- Where should large files live?
- What stops an AEM Cloud content move?
- How do teams plan around the caps?
Do wide content rows survive export?
Oracle's MySQL 5.7 manual caps any table's internal row at 65,535 bytes, with BLOB and TEXT counting only 9-12 bytes because contents sit off-row MySQL row-size limits. CMS tables with many text fields, flags and metadata can hit that ceiling even when disk space remains. Moving long body copy to TEXT or BLOB keeps the counted row narrow. Oracle also describes an InnoDB limit of slightly less than half a database page, about 8KB on the default 16KB page and about 16KB on 64KB pages.
Extra variable-length data moves off-page automatically. Microsoft Learn describes a similar SQL Server pattern with an 8,060-byte in-row cap and row-overflow storage that leaves only a 24-byte root in the main record. For migration, the risk is schema mismatch. A wide Drupal field collection or WordPress meta row that runs on large pages in MySQL may fail on SQL Server, or bloat after off-page storage changes. Audit row width before export and split overly wide content types.
Will large pages break in transit?
Oracle's MySQL 8.4 manual rejects any single statement, row or replication event larger than max_allowed_packet, with an absolute 1GB cap and defaults of 64MB on the server and 16MB for the mysql client MySQL packet limits. The connection closes on breach. A single page revision with embedded images, base64 files or long revision history can trigger that failure during dump or load. PostgreSQL Global Development Group v18 docs store rows in fixed commonly 8KB pages that tuples cannot span.
Rows wider than normally 2KB trigger TOAST compression and splitting into roughly 2,000-byte out-of-line chunks. That design saves normal reads but adds work during bulk copy. Test with production-size revisions, not sample pages. Raise packet settings within allowed bounds, export large blobs separately, and keep transaction batches small enough to stay under transfer limits.
Where should large files live?
MongoDB Inc. v7.0 manual caps every BSON document at 16 MiB, so larger CMS files must use GridFS chunking, by default 255 KiB chunks MongoDB GridFS limits. A CMS that stores PDFs, video or image variants inside single documents will fail at that boundary. GridFS avoids the cap by storing each file across many small chunk documents.
PostgreSQL Global Development Group v14 docs allow a single TOASTed field up to 1GB, while the separate large-object facility supports values up to 4TB with efficient partial reads and writes. Large objects suit video, archives and high-resolution asset libraries that need range access. TOAST suits long text that is usually read whole. Decide storage by access pattern before migration. Keep article text inline, move binaries to file storage, object storage or the database large-object path, and rewrite references during import.
What stops an AEM Cloud content move?
Adobe Experience League states the Content Transfer Tool supports under 750 million JCR nodes, up to 500GB compacted Author segment store plus 50GB Publish, 20TB file datastore and 25GB Lucene indexes AEM transfer prerequisites. JCR nodes are the content tree units for pages, components, versions and assets. Exceeding those totals blocks ingestion even when the source database runs well. Adobe also states MongoDB node properties over 16MB fail ingestion.
Oversize properties often come from inline binaries, huge JSON configs or runaway version histories. Those nodes must shrink before transfer. Scope the source repository against all five numbers early. Purge stale versions, cold assets and orphaned indexes, then remeasure Author, Publish, datastore and index size before scheduling cutover.
How do teams plan around the caps?
Limits interact, so one oversize field can fail row checks, packet checks and destination checks in turn. A pre-migration inventory finds the worst offenders while rollback remains cheap.
Front-end, SEO and ads teams should join that review because templates and tracking fields add width. Clean the repository first, then migrate the smaller active set and archive the remainder separately.
- Export row widths, largest revisions, largest assets and total node counts.
- Move binaries out of rows and documents into file or object storage.
- Split wide content types and trim version history.
- Test import with the largest real pages and files, not fixtures.
- Size Author, Publish, datastore and index totals against AEM Cloud quotas.




