How we migrated TechTenstein from WordPress.

The starting problem

The former WordPress site mixed relevant service information with a much larger historical content footprint. Replacing the design alone would have left broken links, duplicate or thin search surfaces, and uncertain handover. Our aim was a faster, clearer service website that still treated existing URLs deliberately.

What we did

1. Backed up and inventoried: we retained a recoverable copy before cutover and gave all 540 inventoried legacy routes an explicit migration decision.
2. Separated useful content from old volume: relevant service routes received substantive replacements; only individually reviewed articles remained indexable. Other routes were redirected only to genuinely equivalent destinations or returned 410 when no replacement existed.
3. Built a smaller public journey: service pages now explain scope and ownership; free planning and bounded audit tools help visitors prepare before an enquiry. Private workspace, monitoring and checkout features are separately gated until their operational checks are complete.
4. Verified the release: we tested route outcomes, canonicals, sitemap inclusion, HTTPS, public pages and rollback evidence before and after cutover.

What the checks show—and do not show

The release record shows 540 migration-route outcomes read back and 38 canonical public pages checked in the September 2026 deployment. A later bounded website-audit run scored the homepage 100 after a title correction; a separate mobile PageSpeed Insights laboratory run also scored 100. These are point-in-time checks, not a promise of a 100 score on every device, evidence of passing all Core Web Vitals, or proof of improved rankings or enquiries.

Google Search Console reported 27 clicks and 90 impressions for 15–21 September, compared with 47 clicks and 157 impressions for 8–14 September. Bing recorded no clicks in either of those windows. The periods straddle the rebuild and have too little comparable post-launch data for a causal claim. Brand and misspelling queries also dominate the visible Google clicks.

What we would ask before migrating another site

• Which pages actually attract qualified visitors or customers, and which only exist because they were published?
• Who controls the domain, hosting, analytics, Search Console, content, forms and third-party integrations?
• Which old URLs have a true equivalent, and which should return 404 or 410 instead of redirecting to the homepage?
• Can forms, mail delivery, privacy handling and rollback be tested before switching traffic?
• What baseline and comparison window will be used to judge search and enquiry results after launch?

This note describes TechTenstein’s own implementation and recorded checks. It does not claim a customer outcome or guarantee traffic. If you are planning a rebuild, the free migration planner can help you list the decisions first; our website service explains how a scoped project can follow.