Migration acceptance

What Should You Test Before Signing Off a CCMS Content Migration?

An import is a starting point. Acceptance needs evidence.

Content

Confirm the agreed content arrived.

Relationships

Check reuse, links and context.

Outputs

Review what readers receive.

Everyday work

Repeat authoring, review and publishing.

A successful import does not, by itself, establish that a CCMS migration is ready for everyday use. Before signing off, test whether the agreed content arrived, whether its relationships still work and whether the team can produce the outputs it needs.

The practical starting point is an acceptance plan: a record of what will be checked, who will check it and what evidence is needed to approve the result. Agree that plan before the migration so that success is not decided after the fact.

Define the scope you are accepting

Choose a representative content set for the first test. Include straightforward material and the examples that are difficult to handle today: tables, images, reused content, conditional instructions, links or localized material where applicable.

Record exactly what the test includes. A successful result for one product family does not establish that every publication will behave the same way. If important content types are excluded, make that visible and plan how they will be tested later.

The acceptance record should identify the source version, destination version, expected outputs and agreed exclusions. Without that baseline, reviewers may compare different versions and mistake intended changes for defects.

A migration is a route, not a single import

Conceptual acceptance workflow

1Source contentAgree the scope2MappingPreserve relationships3Test migrationUse a pilot set4ValidationCheck against evidence5Sign-offRecord the decisionChecks fail? Revisit mapping and retest.
1Source contentAgree the scope2MappingPreserve relationships3Test migrationUse a pilot set4ValidationCheck against evidence5Sign-offRecord the decisionValidate → revisit → retest
Validate content, relationships, outputs and everyday work. If checks fail, revisit mapping and repeat the test before sign-off.

Check content and relationships separately

An inventory can help confirm that expected items are present. It cannot establish that a reader will receive the right information. Check both.

For example, confirm that a procedure includes the expected steps and illustrations. Then check the links from the publication to that procedure, any shared content it uses and any context that determines where it appears.

In DITA, content reference mechanisms support reuse within topics and maps, as described in the OASIS DITA specification. If your content uses those mechanisms, include representative reuse cases in your migration tests rather than checking only whether files open.

Do not assume that matching filenames prove matching meaning. Identifiers, metadata and relationships can matter to the way content is found, assembled and maintained.

Practical framework

Your acceptance record

Scope

Source version, destination version and exclusions

Check

Expected result, actual result and supporting evidence

Decision

Impact, accountable owner and retest status

Use this structure for a pilot or an agreed migration stage. A pilot sign-off does not approve the entire repository.

Review the output readers will use

Compare the agreed source and destination outputs. Inspect navigation, headings, links, illustrations and tables. Where you publish variants, check that each test output includes the intended instructions and excludes material that does not apply.

Use the team's real acceptance needs to set the depth of review. A cosmetic difference may be acceptable if an approved template changed. A missing warning or incorrect product reference needs a different response. Reviewers should know how to distinguish an intentional change from an unresolved issue.

Keep evidence with the test result: output samples, screenshots, issue references or a short explanation. A record that says only “passed” is difficult to understand when a question emerges later.

Test the next day of work

Migration acceptance should also cover what happens after import. Ask an author to locate a topic, make an approved change and move it through the intended review process. Ask the relevant team to publish the changed content and inspect the result.

Include the people who will actually use the system. A technical specialist completing a task during implementation does not show whether a trained writer or reviewer can repeat it in ordinary work.

Record the training and configuration used during the test. If a task depends on a step that is not documented, resolve that dependency before the team relies on it.

Give defects an owner and a decision

Use a simple issue record: expected result, actual result, evidence, impact, owner and retest status. Avoid combining unrelated problems in one item. A clear issue is easier to resolve and verify.

Agree which issues prevent acceptance and which can be handled later. Any accepted exception should have a named decision owner. This does not require every cosmetic issue to stop a project; it prevents important exceptions from disappearing into informal conversations.

Finally, record who approves the migration stage and what that approval covers. A pilot sign-off should not silently become approval of the entire repository.

For the wider planning context, see Bluestream's discussion of switching CCMS solutions. Acceptance testing turns the migration plan into evidence your team can review.

Further reading

Background guidance; these sources do not endorse a particular CCMS.

Questions about migration acceptance

Is a successful import enough to approve a migration?
No. It confirms only part of the process. Check agreed content, relationships, outputs and the workflows the team needs to perform after the move.

Who should perform the tests?
Use a combination of technical checks and reviews by the people responsible for content accuracy, publishing and everyday work. Assign an owner to each acceptance area.

Can we approve a migration with unresolved issues?
That depends on the agreed criteria and the impact of each issue. Document any accepted exceptions and who has authority to accept them.

Continue your CCMS evaluation

Planning a CCMS evaluation? Register for What To Look For When Choosing A CCMS, taking place December 2.

Talk to Bluestream

Have a question about your CCMS evaluation? Contact our team.

Sign-up for the latest Bluestream News

Close