What the migration covers
The transfer route depends on your WordPress.com plan and current setup. A content export, a full backup, and a media archive contain different things.
- Current platform
- WordPress.com
- Destination
- WordPress
Posts, pages and attachments
We inspect the available export and map authors, categories, tags, comments, and content into the new installation. The standard XML export points to media rather than containing the media files. We check that agreed images and downloads are copied and still work before retiring the source.
Theme and editor compatibility
The destination needs the theme, blocks, and plugins that support your pages. We check availability and licensing, then rebuild any unsupported pieces. Representative pages include galleries, embedded media, and reusable patterns so an apparently successful import does not conceal broken layouts.
Followers and paid features
Newsletter subscribers, followers, paid memberships, and other WordPress.com-connected features need their own handoff decisions. We review the available Jetpack or provider-supported route and preserve consent and access requirements. A transferred article archive alone does not establish that these relationships moved.
Domain and hosting operations
We configure the WordPress destination and plan domain, HTTPS, redirects, and email-record continuity. A custom domain and a wordpress.com address have different redirect options. We document the chosen setup and who will maintain the site after launch.