Migration Assessment Tool | CMS Migration Planner

Establish the current platform, site shape, and broad migration footprint.

Current platform

Wix Assess the migration path from Wix. Squarespace Assess the migration path from Squarespace. Shopify Assess the migration path from Shopify. Webflow Assess the migration path from Webflow. Joomla Assess the migration path from Joomla. Drupal Assess the migration path from Drupal. Custom site Assess the migration path from Custom site. Other platform Assess the migration path from Other platform.

Site type

Brochure site Use brochure site as the primary project model. Blog or publication Use blog or publication as the primary project model. Ecommerce store Use ecommerce store as the primary project model. Membership or gated site Use membership or gated site as the primary project model. Directory or listings Use directory or listings as the primary project model. Booking or appointment site Use booking or appointment site as the primary project model. Portfolio site Use portfolio site as the primary project model.

Approximate site size

1 to 10 pages Light inventory, usually cleaner direct migration scope. 11 to 50 pages A moderate site that still benefits from structured QA. 51 to 200 pages Enough content that redirects and cleanup start to matter. 200+ pages Large migration inventory with higher planning overhead.

Blog post count

0 to 10 posts Minimal archive or little editorial history. 11 to 50 posts A modest archive that still needs metadata review. 51 to 100 posts Enough content that taxonomies and links matter. 101 to 500 posts Large archive with real SEO continuity risk. 500+ posts Major editorial migration with strong QA needs.

Commerce presence

No products Informational or lead-generation site only. Catalog only Products are displayed, but checkout is limited or external. Transactional store The site takes payments or manages orders directly.

Does the site have customer or member accounts?

Yes Logins or account state need to be preserved or rebuilt. No The site does not depend on account-based experiences.

Map the migration before you pick the build path.

Current site basics