AEM migration completed, but content is missing from search: an indexing cutover check

The migration dashboard reports success. Authors can open the pages. Search returns only a fraction of them. That is a business failure even though the content transfer job passed.

Adobe's content migration guidance treats indexing as a distinct part of the journey. The practical lesson is to put search readiness beside content counts, asset checks and publishing in the cutover plan. “The nodes are there” does not mean customers or authors can discover them.

Separate three kinds of missing

First, confirm the content exists at the expected path and is published where needed. Second, confirm the query searches the intended repository scope, properties and language. Third, confirm the relevant index has processed that content and supports the query shape. These are different faults; rebuilding an index will not fix a path filter that excludes the migrated section.

Pick a diagnostic set of pages, not a random sample: a recently moved page, an older page, a page with unusual metadata, each major locale and a page that should be excluded. Record the source path, destination path, publish state, expected search terms and expected result position or inclusion. This becomes a repeatable acceptance suite.

Measure index readiness explicitly

Adobe's indexing best practices recommend understanding query behavior and index design rather than adding indexes by intuition. Run representative queries and inspect query plans and index status in the target environment. Compare expected and observed result sets; do not rely on a single “indexing finished” indicator.

If indexing is still catching up after a large transfer, define a measured wait and a go/no-go threshold. For example, all critical product pages and 99% of the agreed validation set must be discoverable, with zero excluded pages appearing. The threshold should reflect the site, but it must be written before launch pressure rises.

Include content-model changes

Migration often changes paths, templates, tags or property names. A query or component built against the old model may silently return fewer results. Ask whether custom search code still reads the same fields and whether moved assets or metadata have been transformed consistently. Check permissions with an anonymous user and a representative author; permission behavior can make a page look “unindexed” to one audience and visible to another.

Keep a rollback or mitigation plan for failed search readiness. That might be a temporary route to a known content index, delayed launch of a search-heavy experience or a targeted remediation of a bad query. The plan should say who can authorize it.

What a buyer should require

An AEM migration statement of work should include search acceptance evidence: representative queries, expected result sets, index validation, owner sign-off and a post-launch monitor. Otherwise the programme can declare migration complete while customers cannot find the content it moved.

Adovo’s view

A migration is complete only when people can reach the content they were meant to use. Counts of transferred assets and a green index job measure motion through a system; they do not measure discoverability.

Search belongs in the cutover decision, with representative journeys across language, permissions and content types. When a critical query still fails, calling the move complete only transfers the problem to the customer.