An agreed list of design elements, content, URLs, and functionality to preserve
WordPress rebuild & migration
WordPress rebuild without redesign.
You like the way your website looks, but need a different foundation for maintenance, performance, or future features. Honor Tech can rebuild a WordPress website without a full redesign, either keeping WordPress or moving to a custom codebase. We agree on what stays, migrate approved content, preserve useful URLs, and test the customer journeys before launch.
The service
Keep the familiar experience. Change the foundation.
Your logo, colors, typography, page layouts, navigation, photographs, and approved copy can remain part of the rebuilt site. We use representative pages from your current website as the visual reference and agree on desktop and mobile acceptance criteria before extending the implementation across the site.
A rebuild changes how the website is constructed. A redesign changes how it looks and is organized. They can be separate decisions: you can replace a theme or page builder, rebuild templates, or migrate away from WordPress while retaining the customer-facing design. Any layout, accessibility, or content changes are identified and approved rather than quietly expanding the project.
The platform decision follows your editing needs. Staying on WordPress can preserve familiar publishing tools. Moving to custom code gives developers direct control over components and delivery, but needs an agreed process for future content updates. Existing plugin behavior, licensed fonts, media rights, and integrations must be checked before promising an exact reproduction.
A strong fit when
When the design still works for your business.
Businesses with an approved visual identity and useful website content that need a more maintainable implementation. If the main issue is limited to hosting, images, or one plugin, a focused repair may be enough. Our WordPress decision guide helps compare repair, rebuilding, and replacement. For a real migration example, see how we rebuilt Honor Tech’s own website.
See Honor Tech’s own WordPress migrationWorking templates reviewed against the existing desktop and mobile experience
A content inventory and direct permanent redirects for approved URL changes
A tested launch, rollback plan, and clear responsibility for future updates
Website sizes and capabilities
What can be preserved in a WordPress rebuild?
Preservation is a set of agreed deliverables. We compare the existing site with staging, record intentional changes, and verify the things your visitors and publishing team depend on.
Your design and brand
Use the current website as the reference instead of beginning with new visual concepts.
- Retain approved colors, logos, typography, imagery, layouts, and navigation.
- Review key pages at agreed desktop and mobile sizes.
- Approve necessary accessibility fixes and any changes to interactions or licensed assets.
Your content and media
Move useful pages and posts deliberately, including the details that a simple copy-and-paste can miss.
- Inventory pages, posts, author names, dates, images, alt text, and downloads.
- Rebuild page-builder layouts and shortcodes in the destination; they do not transfer automatically.
- Carry forward approved titles, descriptions, headings, and internal links; reconcile the migrated inventory.
Your URLs and journeys
Keep valuable addresses unchanged where practical and give changed addresses a relevant destination.
- Preserve the domain and existing paths when they still fit; changing platforms does not require changing URLs.
- Map each changed URL to its closest relevant page with a direct server-side 301 redirect.
- Test menus, forms, downloads, analytics, and integrations along with page appearance.
What does a rebuild without redesign cost?
Keeping an approved design can reduce visual exploration and revision work. The remaining effort depends on distinct templates, content condition, page-builder dependencies, forms, integrations, URL mapping, and launch testing.
For budgeting only, our hypothetical example assumes eight public pages, twelve blog posts, three reusable layouts, one email inquiry form, and up to five changed URLs. At an assumed 50–80 hours entirely at the $85 standard hourly rate, the development subtotal is $4,250–$6,800. This is an illustrative scenario, not a package, quote, or the cost of Honor Tech’s own website.
The example assumes approved copy and assets, one language, the same domain, and developer-managed content updates. Hosting, licenses, ongoing support, a new editor interface, shopping, and new integrations are excluded. Senior or specialist work uses the applicable published rate, confirmed before work begins.
Review the sample budget and pricing assumptionsCapabilities
How content and URLs survive the transition.
A successful migration accounts for existing pages and visitor journeys before the platform changes. These checks reduce avoidable disruption; search rankings can still fluctuate after launch.
Inventory before implementation
Combine a crawl with the WordPress export, media library, sitemap, analytics, and search data. Identify valuable landing pages and linked downloads, including addresses that are no longer in the menu.
Content mapping and reconciliation
Give each source page a destination and a decision: retain, update, combine, or retire. Compare page and media counts, review representative posts, and verify author attribution, dates, headings, and download links.
URL preservation and redirects
Keep existing public paths when practical. For each approved change, test the old address, permanent redirect, and final destination. Update internal links to the final URL and avoid redirect chains or sending unrelated pages to the homepage.
Search signals carried forward
Review titles, descriptions, canonical URLs, structured data, robots rules, and the XML sitemap. Staging access restrictions must be replaced with the intended public indexing settings at launch.
Forms and publishing workflow
Recreate required plugin behavior or reconnect supported services. Test validation, confirmations, delivery, and analytics. Confirm who will edit pages and publish posts after the move.
Launch and monitoring
Back up the original site, rehearse cutover, and define rollback. Verify production URLs and forms, submit the current sitemap, monitor crawl errors and search traffic, and retain permanent redirects for the long term.
Delivery approach
A controlled move from the current site to the rebuilt one.
- 01
Review the current website, editing workflow, content, accounts, and business goals. Decide whether a focused repair, a WordPress rebuild, or a platform migration is justified.
- 02
Approve the preservation inventory, reference pages, URL map, exclusions, estimate, and review schedule. Identify the person who can approve exceptions.
- 03
Rebuild representative templates in staging and compare them with the approved reference. Migrate content and media, then reconnect forms and required services.
- 04
Review desktop and mobile layouts, keyboard use, content completeness, redirects, metadata, and form delivery. Agree on a content freeze or final synchronization so last-minute edits are included.
- 05
Launch with backups and a rollback path. Check the public site, indexing settings, sitemap, and redirects, then hand over the editing and maintenance responsibilities.
Related technology insights
Practical context for the decisions around the system.
Optimize, Rebuild, Replace, or Leave It Alone? What to Do With an Existing WordPress Site
A balanced guide to keeping, optimizing, rebuilding, or replacing a WordPress website based on performance, editing, maintenance, design, SEO, and long-term ownership.
Read the articleHow Much Does a Business Website Cost? What You’re Really Paying For
A practical explanation of business website pricing, with a hypothetical WordPress rebuild budget and the scope, migration, and ownership choices behind an estimate.
Read the articleWebsite Accessibility Testing: What an Automated Scan Can Miss
Website accessibility testing needs more than a scan. Learn what keyboard, screen reader, form, and zoom checks can reveal before visitors get stuck.
Read the articleRelated services
Explore the services around this work.
Business website development
Plan a new design, expanded website, or connected customer experience when the scope goes beyond preserving the existing site.
Explore this serviceApplication support and maintenance
Define responsibility for updates, monitoring, troubleshooting, and improvements after launch.
Explore this serviceCommon questions
Useful detail before the first call.
Can you rebuild a WordPress website without changing its design?
Yes. We can retain the approved visual design while rebuilding the implementation on WordPress or moving to custom code. We agree on reference pages and acceptance criteria first. Accessibility fixes, unsupported interactions, and license restrictions can require specific approved changes.
Do we have to leave WordPress?
No. If your team benefits from WordPress editing and publishing, rebuilding its theme or templates may be the right choice. A custom-code migration is an option when its operating model fits your business and the process for future content updates is clear.
Will our blog posts, images, and URLs be preserved?
Approved content and media are inventoried and mapped to the destination. Existing URLs can usually remain when the domain and routing allow it. Changed paths need relevant permanent redirects. Page-builder layouts, shortcodes, downloads, metadata, and plugin features need separate migration checks.
Will we lose search rankings when we move away from WordPress?
Changing platforms does not require abandoning existing URLs or content, but no migration can guarantee unchanged rankings. We preserve useful paths, map redirects, review metadata and indexing settings, and monitor production crawl errors and search performance after launch.
Is Honor Tech’s website a real example?
Yes. This website was rebuilt from WordPress into an Astro-based codebase. Selected existing articles were recovered, legacy addresses redirect to current pages, and the project now supports reusable templates, responsive images, technical SEO, protected inquiry forms, and checked deployments. Its design and content have also evolved; it demonstrates a real migration and continued development.
What should we send for an estimate?
Send your current website address, the design elements you want to keep, approximate page and post counts, required forms and integrations, editing needs, account-access constraints, and launch timing. We review those details before confirming scope and price.
Have something ambitious in mind?
Bring the site you want to keep and the problems you need to solve.
Tell us where you are, what is getting in the way, and what a strong outcome looks like. We’ll come back with practical next steps.