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 guideGOOD DATA. GREAT POSSIBILITIES.
Plan website content imports around an authorized source inventory, a clear extraction rule, and a destination readers can actually use.
Identify the pages, languages, and revisions that belong in your collection. Prefer an approved structured export when it preserves the required content better than rendered HTML. Keep retrieval credentials and source authorization outside imported records.
A link on a page is not an instruction to expand the migration. Decide which external references remain links and which assets need an authorized copy.
Identify the main content area and preserve headings, lists, code, and essential table context. Review selectors on several layouts before applying them broadly. Parsing HTML is not a substitute for a sanitization policy when content will be displayed in an active page.
Keep a traceable source address and extraction version. A cleanup rule that removes a footer should not also remove a repeated warning in an instruction.
Resolve relative links using the source context, then map them to the intended destination. Track missing images and attachments as review tasks. Separate a temporary retrieval failure from an intentional source deletion.
Use a reference set with a tutorial, a code-heavy page, a table, and an image-dependent article. Check meaningful content, not just the presence of a title and body.
Use a small, representative source and write down the expected result for one accepted record, one correction, and one repeated attempt. Keep the original values and the destination expectations visible throughout the review.
Use the format guides for source decisions and the local quickstart to see a simple mapping in action.