
Tray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
From Adobe Experience Manager to Contentful
Last verified:
The process
First we check the existing Adobe Experience Manager and see whether the data is clean enough to move straight over to Contentful, and plan around any auth walls or bot protection in the way.
Then we work out how Adobe Experience Manager renders its pages and pull the content out, even without CMS access.
Everything extracted runs through our sanitization pipeline, which flags slop, normalizes structure, and leaves us clean content to work with.
Before anything moves, we agree the Contentful content model with you, shaped around how your editors actually work.
We transform the content to the agreed schema and run a full dry run, so mappings and edge cases prove out before production.
Once the dry run is clean, everything moves into Contentful in one controlled cutover.
Every old URL gets mapped to its new home with the right redirect, so rankings and link equity survive the move.
Finally, automated browsers sweep the new site for data issues, design regressions, and missing SEO signals.
Adobe Experience Manager to Contentful
A content-only move from Adobe Experience Manager to Contentful takes at least six weeks. A move that comes with a redesign takes longer, because the design and frontend build sit on top of the content work. Cost follows how customized the AEM instance is, more than how many pages it serves: how many component types sit on your pages, how much already lives in content fragments, and how many language copies and live copies have to fit into Contentful's locales and content types.
AEM stores everything in the JCR, a tree of nodes and properties. A page is a node under /content with its components nested beneath it, and assets sit in the DAM under /content/dam. Contentful wants a flat set of content types, entries that link to each other, and body copy as rich text stored as JSON rather than HTML. So most of the work happens before anything moves. We go through the component types and content fragment models, decide which carry real content and which were only ever layout, and agree the content model with your editors first.
That content-type budget shapes the model more than anything else in this move. Contentful plans cap how many content types a space can hold, and AEM sites often have dozens of component types. We merge components that differ only in layout into one content type with a variant field, and keep layout decisions in the frontend. On Tray.ai's Contentful space we scrapped the bloated models and built a fresh page builder with live preview, so marketing ships pages without engineering.
Then we export the repository, script the transform and run it as a full dry run into a separate Contentful environment. Content fragments map closely, because a content fragment model is already a typed schema. HTML from text components converts to Contentful rich text, and anything it can't map gets flagged rather than dropped. We build the redirect map from the URLs the AEM site serves before cutover, and keep the old site live until the new one is verified.
Content mapping
| In Adobe Experience Manager | In Contentful | What to know |
|---|---|---|
| Pages and page templates | Page content types | A page entry holds its fields and a references field listing the section entries that make up the layout. |
| Page components | Section content types | Components that differ only in layout share one content type, to stay inside the content-type limit. |
| Text and rich text components | Rich text fields | Paragraphs, headings, lists and links convert directly. Embedded components become embedded entries. |
| Content fragment models and content fragments | Content types and entries | Fragment references become reference fields. Enumerations become short text fields restricted to set values. |
| Experience fragments | Shared entries that pages reference | |
| DAM assets | Contentful assets | Renditions are dropped, because Contentful's Images API resizes and converts on request. |
| Tags | Contentful tags or a referenced taxonomy content type | |
| Language copies | Locales on the same entry | Contentful localizes field by field, with a fallback locale for fields left untranslated. |
| SEO page properties | An SEO content type referenced from each page |
Watch for these
Every AEM component that becomes its own content type uses up part of the plan's allowance, and each content type can hold at most 50 fields. We consolidate components before modeling, rather than discovering the limit halfway through the import.
Contentful locales assume every language has the same entry with translated fields. AEM language copies and live copies often drift, with sections that exist in one market and not another. We either model those as separate entries per market or bring the structures back in line, and decide which with your editors before cutover.
Adobe Target audiences and offers live outside the JCR, and Multi Site Manager rollouts have no Contentful equivalent. Personalized slots get rebuilt in whatever tool you pick, not migrated, so we list every one during the audit.
A Contentful rich text field holds up to 200,000 characters and an entry can link to at most 1,000 other entries and assets. Long AEM pages with many embedded components can hit either limit, so the transform splits them into sections instead of failing the import.
Key pain points
AEM’s biggest flaw is simple: everything about it is expensive. The license, the hosting, the maintenance, the consultants, the upgrades, and the people required to even use it. The learning curve is a cliff, implementation cycles move at glacial speed, and the UI feels like punishment for asking to edit content. Performance tanks the moment you customize anything, and collaboration is basically "email the PDF and pray." If you ever see the word specialized in an AEM context, just assume the invoice comes with an extra zero.
It’s the definition of a heavyweight DXP built for organizations with more bureaucracy than sense. For everyone else, it becomes a slow-moving, over-engineered system that requires Adobe-certified babysitters just to stay alive. If you’re considering scrapping it for something faster, saner, and built this decade, we can help you migrate without dragging the AEM baggage along for the ride.

High complexity and cost
AEM is one of the most expensive CMS/DEXP platforms on the market, with licensing, hosting, and maintenance costs that only make sense for very large enterprises.

Steep learning curve
The platform is dense and requires specialized training just to perform routine tasks. Most teams can’t operate it without dedicated experts.

Prolonged implementation periods
Even simple projects take months. Rollouts, upgrades, and workflow changes move slowly and require careful planning to avoid breaking things.

Challenging navigation of capabilities
AEM packs in a huge feature set, but finding and configuring what you actually need can feel like wading through molasses.

Necessary reliance on Adobe partners
You’re essentially forced into using Adobe-certified agencies or consultants for setup, maintenance, and troubleshooting and they don’t come cheap.

Not ideal for smaller companies
The cost, complexity, and operational overhead make AEM a poor fit for startups or mid-sized teams. Most will drown in it long before they benefit from it.
Key advantages
Contentful is one of the most established headless CMS choices, and we still see plenty of customers land on it after a shortlist.
It's built around structured content, so you model fields once and pull them into any front end you like. That means no copy-pasted components scattered across pages. It also has first-party support for A/B testing and personalization through its Studio add-on, which most competitors don't match natively. The app ecosystem covers SEO, translation, validation, and asset management, and editors get live side-by-side preview for content they're working on.
If your team has the budget and the developer resources to model content properly, it's a solid pick.

API-first design
Contentful was built for APIs from day one, which means your content plugs cleanly into apps, websites, and mobile.

Developer-friendly flexibility
Schemas, content models, and references can be tuned however you like. If your stack is anything beyond "cookie-cutter," Contentful won’t get in your way.

User-friendly interface
Editors enjoy using it. Clean UI, quick search, structured fields, and no "where does this go again?" confusion.

Extensive integration capabilities
Plug in analytics, eCommerce, automation, and translation. Contentful plays nicely with almost anything. And if something isn’t supported yet, you can wire it up yourself without hacking the platform apart.

Scales under traffic
Contentful's global CDN holds up under heavy load. We've run it on sites pushing millions of monthly requests without needing bespoke infrastructure to handle spikes.

Cloud-based architecture
You don't have to install, patch, or maintain anything. It’s fast, globally distributed, and always up to date. Your content team can ship from anywhere without a DevOps babysitter.
The migration is step one. Our Contentful team handles what comes after: builds, integrations and the content model work that keeps the new platform clean.
Contentful development agencyTell us what you're building. We reply within one working day. Jono or someone on the team picks up every message personally.
You can also book a call.
Functional, beautiful, websites that you actually want to edit