Import the content. Leave the clutter.
Plan an authorized website migration with clean extraction, source provenance, meaningful structure, and a reviewable destination collection.
Read the guideImport solutions
Content Workflows
Connect authorized web and document sources to a reviewable editorial destination.
Start with an editorial inventory
Choose which pages, manuals, and revisions belong in the collection. Identify source ownership and the fields needed by the destination. Preserve the distinction between a publication date, a source modification observation, and a processing timestamp.
Map headings, code, tables, and attachments intentionally. Not every visible page element belongs in the content record. Review navigation removal on different layouts so cleanup does not accidentally discard meaningful warnings.
Separate extraction from approval
Keep received, extracted, reviewed, and published states distinct. A nonempty title and body are not sufficient evidence that an article survived migration. Provide a side-by-side source reference and a clear list of unresolved links or missing assets.
Assign correction work to the right owner. A broken extraction selector needs engineering attention; an obsolete instruction needs editorial review. The same generic failure status should not conceal those differences.
Maintain the collection after launch
Track source revisions and derived content relationships. A revised document should create a reviewable change rather than automatically inherit approval from an older extraction. Define whether missing source material is archived, deleted, or queued for review.
Test a code-heavy page, a document with tables, and an article that relies on an image. A useful content pipeline preserves meaning across these variations and leaves enough provenance for future maintenance.
Define your first acceptance check
Choose a representative source, an owner for the destination contract, and a small set of results that a reviewer can inspect. Include a correction case and an interrupted attempt before expanding the workflow.
The developer guides connect these planning decisions to record shapes and local examples. Keep your implementation narrow enough that its outcome is easy to explain.
From Import Notes
A little reading. A better workflow.
Give your documents a second life.
Build a document import that preserves headings, handles uncertain extraction, and connects useful text to its original source and revision.
Read the guide