Site Migration

Moving a thousand-page site into a new CMS is usually the project that kills the project. RIFT's migration pipeline automates the mechanical work and puts a human decision gate at every step that matters.

The four stages

1 · Crawl

The pipeline fetches your existing site — sitemap first, then pages and assets — and identifies the shared chrome (headers, footers, navigation) so page content can be separated from template noise.

2 · Classify

Every crawled page is classified into content archetypes: article, landing page, contact page, policy document, listing, and so on. Archetype definitions are reviewable and adjustable — you see the classification before anything is created.

3 · Parameterize

The pipeline detects the repeating visual patterns across your pages — cards, callouts, heroes, stat rows — and proposes a formal design system from them: tokens for your actual colors and spacing, and components with named parameters extracted from the repeating markup. Each proposed component shows the real pages it was derived from.

4 · Migrate

Content is created in bulk in the CMS: folder structure mirroring your URL paths, content items with cleaned bodies referencing the proposed components, assets uploaded and linked, and internal links rewritten from hard-coded paths to identity-based references that survive future restructuring.

Human decision gates

The pipeline pauses for your decision wherever judgment matters: approving archetype definitions, accepting or rejecting each proposed design component, resolving ambiguous pattern matches, and confirming bulk operations before they run. Runs can be paused, resumed, or cancelled at any point, and a dry-run mode validates any operation without committing it. The pipeline drives the same audited API as every other RIFT integration — nothing bypasses the record.

What you end up with

• Your content in RIFT — foldered, classified, and internally linked by identity rather than brittle paths.
• A proposed design system derived from your site's actual visual patterns, ready to review, refine, and promote.
• A migration report of every page, decision, and transformation for the compliance file.