Financial TimesAmericas' Fastest-Growing 2025
Certified PartnerOdoo Gold · Adobe Gold Solution · Shopify Premier partnershipsOdoo Gold · Adobe Gold · Shopify Premier partnerSee all
One business dayA senior architect replies to every inquiry · +1 (631) 897-7276Architect reply within one business dayLet's talkCall us
Inc. Regionals 2025Fastest-growing private companies in AmericaInc. Regionals 2025 honoreeSee awards
Americas' Fastest-Growing Companies 2025Recognized by the Financial TimesFT Fastest-Growing Companies 2025See the rankingRanking
4.8 / 5 on Clutch265 verified client reviews4.8/5 on Clutch · 265 reviewsRead the reviews
4.8 · 265 Clutch reviews
US United States
October 30, 202512 min readUpdated on October 8, 2026

AEM implementation goes wrong in the content, not the code

· Vice President, eCommerce and ERP
AEM implementation goes wrong in the content, not the code

Most AEM RFPs run long. They list components, integrations and a security appendix in careful detail. Picture a program with 80,000 pages and 300 authors. The same RFP rarely says who will move those pages, or who will teach those authors to publish on the Monday after launch.

That gap is where an AEM implementation usually stalls. The code tends to ship. The content arrives late and messy, and the authors keep emailing IT to change a banner. So the argument of this guide is simple: plan the content and the people with the same rigor as the build, starting in the RFP. The roadmap below follows that order, from version choice to the first year after go-live.

A caveat before the detail. If you run one site, in one language, with a few hundred pages and a small team, AEM may be more platform than you need. A lighter CMS will cost less to license and run. Everything that follows assumes multiple sites, multiple markets or both.

Settle the version before you write the RFP

Your deployment model shapes every later decision, and Adobe's calendar has forced the question for anyone still on classic AEM 6.5.

Deployment model Status in October 2026 What it means for a new implementation
AEM as a Cloud Service Adobe calls it "the latest offering of the AEM product line". Monthly feature releases; 2026.10.0 is targeted for October 29, 2026. The default for new programs. Adobe runs the infrastructure and updates.
AEM 6.5 LTS (on-premise or Adobe Managed Services) Service Pack 3 shipped August 20, 2026; SP4 is targeted for February 18, 2027. For teams that must self-host. Core support follows the 6.5 dates below.
Classic AEM 6.5 AMS support "ends by August 31, 2026"; 6.5.26.0, targeted November 19, 2026, is the last supported service pack. Not a target for new work. Plan an upgrade or a move to the cloud.

Adobe's support article puts on-premise core support for AEM 6.5 at February 28, 2027, with critical-fix extended support to February 28, 2028. AEM 6.5 LTS follows the same dates. If you're on classic 6.5, your implementation plan is your upgrade plan.

That deadline tempts teams into a full re-platform on a rushed timeline. Often the safer first move is smaller. Moving to 6.5 LTS buys time, and the cloud migration can then be planned properly rather than squeezed into a support window.

For a new program with no hosting constraint, choose Cloud Service. You get automatic scaling, a built-in CDN and "automated updates up to several times a month". In return, your code must keep up with a baseline that changes often, and Cloud Manager controls all updates. AEM 6.5 LTS suits teams with hard hosting or regulatory limits, but they own the upgrade calendar.

The AEM roadmap has six phases, and the build is one of them

Vendors price the build in detail because it's what they know best. The other five phases get a line each, or none.

Phase What happens What you should have at the end
1. RFP and selection Define outcomes, constraints and integrations; choose an implementer A signed scope with measurable goals
2. Architecture Deployment model, delivery approach, component library, site structure An architecture decision record and a component inventory
3. Build Templates, components, integrations, Cloud Manager pipelines A working stage environment that passes the pipeline gates
4. Content migration Audit, prune, transfer and validate content Content in production with a final top-up plan
5. Go-live Freeze, final top-up, DNS and CDN cutover, monitoring A live site with nobody deploying on launch day
6. Adoption Role-based training, governance, measurement Authors publishing without tickets to IT

The order can flex. What can't flex is that each phase has a named owner and its own budget line. When migration and training share a row in a project plan, both get shortchanged.

What the RFP should ask for

A feature list invites every vendor to say "yes" to everything. An outcome list forces them to explain how they'd get there. "Cut time to publish a regional campaign page from 10 days to 2" tells a vendor far more than "support multi-site management", especially with a baseline and acceptance criteria attached.

Vendors also need the facts that drive effort. Give them the number of sites, languages, pages and assets, because nobody can estimate migration without that inventory. Name the systems AEM must talk to, such as CRM, commerce, ERP, search, analytics and your identity provider. Note any technical constraints, and say which flows are real-time and which can run in batches.

Then come the non-functional requirements: peak traffic, uptime target and an accessibility standard such as WCAG 2.2 AA. Add privacy or security obligations like SOC 2, CCPA or HIPAA where they apply. Finish with the operating model after launch. Who runs the platform, and what must the vendor hand over?

If your enterprise architecture standards say "cloud-first", put that in the RFP plainly. Ask each vendor to propose AEM as a Cloud Service and justify any deviation. Ask how they'd split traffic between classic AEM publishing and Edge Delivery Services, and why.

Ask for licensing assumptions in writing, too. Adobe doesn't publish AEM list prices, so every proposal guesses differently. This AEM pricing breakdown explains the license metrics and the cost lines vendors tend to leave out.

Four architecture calls that set your running costs

Decisions made in the first few months fix your running costs for years. Tie each one to a business need rather than a vendor's habit.

The first is how pages get delivered. Adobe says Edge Delivery Services replaces the classic Publish and Dispatcher tier, along with the traditional way of building pages with Core Components. Authors can work in the Universal Editor or in Word and Google Docs. Edge Delivery and AEM Sites can share a domain. In practice, that lets you move high-traffic marketing pages first and leave complex, logged-in areas on classic publishing.

The second is headful versus headless, and Adobe's own docs say it "does not need to be a binary choice". Visual page authoring suits the marketing site. Content Fragments and the GraphQL API can feed mobile apps, kiosks and partner portals from the same content.

The third is the editor. The Universal Editor is meant to "eventually supersede the Page Editor", and it runs on Cloud Service, 6.5 LTS and 6.5. New component work should assume it.

The fourth is the size of your component library, and it matters more than it looks. Every custom component is code you'll retest against every monthly release. Start from AEM Core Components and extend only where there's a real business case. Use Experience Fragments for reusable sections such as headers and promos, and Content Fragments for structured content. Keep a register of everything you build. A short list of well-made components is easier to test, document and teach than dozens of one-offs.

Global rollouts: design live copy and translation before templates

With more than a handful of country or brand sites, this is the part of an AEM implementation that either saves years of work or creates it.

Multi Site Manager (MSM) lets you author content once in a blueprint and reuse it across many sites. Each live copy stays linked to its source, and a rollout configuration decides which properties sync, how and when. Regional teams can suspend the link on a page, or cancel inheritance on a single component, to localize it.

Two actions need a written policy before regional authors get access. Detach is permanent; Adobe's docs call it "permanent and non-reversible". Reset wipes local changes and returns the page to the source state. One well-meant reset can erase a market's quarter of local edits. Adobe publishes MSM best practices, and they're worth reading before you design the blueprint.

MSM doesn't translate anything. AEM's translation framework handles language copies through translation projects. It supports human translation through a provider connector, machine translation and, more recently, LLM-based translation with per-locale style guides.

A common pattern is one language master per language, translation projects to fill each, then live copies from those masters to country sites. Settle that structure before anyone builds templates. Changing it after launch means restructuring content trees.

Content migration needs its own owner

Content migration is the line item teams underestimate most. Give it a named owner, a separate plan and at least two test runs.

Start by auditing the content repository. Pages with no traffic in a year, duplicate PDFs and retired campaigns shouldn't make the trip. A lift-and-shift copies old problems onto a new platform, where they're harder to find.

For a move from AEM 6.x to Cloud Service, Adobe's tooling covers most of the mechanics. The Best Practices Analyzer flags code to refactor, repository items in unsupported locations, legacy UI and features Cloud Service doesn't have. Cloud Acceleration Manager turns that into an initial assessment and links each finding to the right tools and docs. The Content Transfer Tool extracts content from your source AEM instance into a migration set and ingests it into Cloud Service. Differential top-ups then move only what changed since the last run.

Plan the content freeze around measured timings, not hopeful ones. Adobe's migration go-live guidance is specific:

  1. Time a full extraction and ingestion on a production clone, and use that number to plan top-ups.
  2. Size each top-up so extraction and ingestion take no more than 48 hours, which fits a weekend.
  3. Run the real production migration from production, not from a clone.

The same page lists two hard limits. An ingestion fails outright if any node name runs past 150 characters or any node is bigger than 16 MB. Scan for both before the first run rather than finding out at 2 a.m.

Pipelines and go-live day

On Cloud Service, everything ships through Cloud Manager pipelines, so plan the team's workflow around them early. Full-stack pipelines deploy back-end code, front-end code and web-tier configuration together, and only one is allowed per environment. Front-end pipelines deploy themes much faster, which keeps front-end developers from waiting on Java builds. Config pipelines push settings such as CDN rules and log forwarding, usually in minutes.

Production pipelines run code quality, functional and experience audit testing, and the experience audit "cannot be skipped". Adobe expects an end-to-end run to take 20 to 50 minutes, depending on the application. That suits a sprint cadence and hurts during a hotfix, so test locally before you push.

Put one more date in the plan. Adobe's 2026.9.0 release notes say all Cloud Service environments, production included, move to the Java 25 runtime in June 2027. Customers can opt in from November 2026. Budget a test cycle for it.

For cutover itself, work from Adobe's go-live checklist rather than a date on a slide. Freeze code and content, then run the final top-up. Validate the AEM Dispatcher configuration locally and check your virtual host aliases. Run AEM performance and security tests on stage, because stage matches production sizing and other AEM environments, such as development, don't.

Lower your DNS TTL ahead of time and test with a subdomain first. On the day, ship no new deployment and no content update. Set up notification profiles in the Admin Console and consider traffic filter rules; WAF rules need a separate license. US retail and ecommerce teams can add a rule of their own: no cutover inside the Black Friday and Cyber Monday code freeze.

AEM user training and adoption

A site nobody can update is a very expensive brochure. This is the phase that most often gets squeezed when the build runs late, and it's the one authors remember.

Train by role, not by feature. Authors, approvers, regional managers, developers and administrators need different things. Content authoring training for a regional marketer looks nothing like a developer's onboarding. Give each group short sessions on the tasks they'll do weekly, inside your own templates, rather than a tour of every menu. Record the sessions, because new authors keep arriving long after the vendor has left.

Someone also has to own the platform once the project team disbands. A small center of excellence works: a platform owner, a lead author and a technical lead who own components, templates and governance. Their job is to say no to one-off components and yes to reuse. Without that group, component sprawl tends to start within a year.

The technical lead should be certified. Adobe runs Professional and Expert certifications for AEM, with exams at $125 for Professional and $225 for Expert, and most renewals are free. Next to the license, that's a small line item.

AI now belongs in the training plan as well. Adobe's 2026.9.0 release notes say AEM agentic capabilities have been generally available in Adobe CX Enterprise Coworker since early September 2026, with access enabled automatically. Decide what agents may draft or change before your authors discover it on their own, and write those rules into training.

How to measure AEM implementation success

Go-live is a milestone, not the result. Agree on success measures in the RFP and report against them for at least a year.

Measure Why it matters Where it comes from
Time to publish a page or campaign Often the headline goal in the business case Workflow history and team reporting
Share of content changes made without IT Shows authoring adoption Ticketing system
Reuse rate of components and live copies Shows the global model is working Component register, MSM reports
Page performance and Core Web Vitals Affects search visibility and conversion Cloud Manager experience audit, analytics
Release currency Cloud Service versions more than six months behind need scheduled updates with Adobe Cloud Manager

Start tracking active authors per week, draft-to-publish time and IT tickets for content changes from month one. Pair them with site metrics from Adobe Analytics, and bring in Adobe Target once you're ready to test variations. If authors still email IT to change a banner after three months, the training or the templates need work.

The last row of the table is easy to miss. Adobe's release roadmap says versions "more than six months older than the current release require scheduled updates with Adobe assistance". Keep custom code current, or every upgrade turns back into a project.

Which agency implements AEM Sites for global rollouts?

Adobe's partner program offers a useful filter. To earn a new AEM specialization, a partner needs certified people and customer references from three companies. Those projects must be in the region being pursued and active within the last 12 months. Specializations are earned per region: Americas, EMEA, APAC and Japan. A partner holding one product specialization in at least three of the four regions gets a global designation, and each lasts two years.

Borrow that logic for your own shortlist. Ask for references in your regions, with live sites you can open and authors you can call. Ask who will actually staff your project and which AEM certifications each person holds. Ask how they've handled MSM and translation at your scale, including what went wrong. Make documentation, runbooks and training contract deliverables. Then cross-check each firm's claimed specializations and regions against Adobe's partner directory.

Want the content inventory and the MSM model pressure-tested before the RFP goes out? Our Adobe Experience Manager services team can start there. Send us your site count and content volume, and we'll map the migration and adoption work alongside the build.

FAQ

How long does an AEM implementation take?

It depends mostly on content volume, the number of sites and the integrations. A single site with a modest component set moves much faster than a global, multi-language rollout with commerce and CRM connections. Ask vendors to break their timeline down by the six phases, and be wary of any plan where migration and training share a single line.

What is live copy in AEM?

A live copy is a copy of source content that stays linked to that source through Multi Site Manager. Changes to the source, called the blueprint, roll out to live copies based on rollout configurations. Regional authors can suspend the link or cancel inheritance on a component to localize it, while detach breaks the link permanently.

What are the biggest risks in an AEM implementation?

Underestimating content migration, building too many custom components and skipping author training are the big three. A weak global site model, meaning MSM and translation, comes close behind for multi-country brands. All of them surface after launch, which is why success should be measured for at least a year.

ShareLinkedInXEmail

Related reading

Moving to AEM from another CMS in Southeast Asia? See Brainvire's Sitecore to AEM migration in Singapore and Sitecore to AEM migration for Thailand.

Building on Adobe Commerce or Magento?

Explore Adobe Commerce services