Move an existing website to Neopress
Plan the pages, content, URLs, and integrations you need to move, then switch your domain after verification.
Decide what needs to move
A website move includes more than matching the homepage design. List the pages, articles, images, forms, languages, search metadata, and important URLs you need to retain. Also list external systems such as booking tools, payments, email platforms, and customer databases. These need a separate integration decision.
Neopress offers migration assistance. Share your existing website URL through the contact or migration option and confirm the scope with the team. Additional design or development work may need a separate scope and cost agreement.
Import one page or rebuild a structured site
The new website flow can use Import an existing page as a starting point for a single URL. Check the generated copy, design, links, and images. Importing one page does not transfer the entire original CMS or keep the source website continuously synchronized.
For a blog, documentation area, or customer stories, create the appropriate collections and move each item as content. Connect list and detail pages, preserve useful slugs, and recreate translated versions as linked entries.
Prepare the cutover
- Build and review the target pages while the existing website stays available.
- Map old URLs to the new URLs. Keep the same path when practical.
- Create and test forms; confirm where responses will be reviewed.
- Check page titles, descriptions, images, language URLs, and search settings.
- Publish the target pages and content, then inspect the default public address.
- Connect your domain and follow the DNS records shown in Neopress.
- Add appropriate redirects for URLs that have changed.
If you need a gradual move
Progressive site migration lets Neopress serve pages already moved while retrieving unmatched paths from an existing site origin, such as legacy.example.com. The original domain points to Neopress. The old website must remain reachable at a separate origin that does not point back to Neopress.
This is different from mounting a Neopress website beneath example.com/new-site while another platform owns the root. That subdirectory connection is not currently supported. Read the redirects and progressive migration guide before choosing this approach.
Verify after switching
Open the homepage, your most visited old URLs, key content pages, and each language. Submit a form you control to verify the workflow. Recheck Search Console and the sitemap for the connected domain. Content and URL continuity help you manage the move, but no migration can guarantee unchanged search rankings.