The starting point
Business challenge
The sites depended on legacy WordPress infrastructure and accumulated content, media, redirects, and obsolete URLs. Migration risk included broken internal links, lost search visibility, missing assets, deployment errors, and difficult rollback.
Alexander’s role
Work and solution
Alexander personally managed content and media migration, URL inventories, redirect mapping, 301/404/410 analysis, internal-link validation, SEO preservation, staging and production deployment, backups, rollback planning, and post-release health checks. He built a Git-based deployment flow covering dependency installation, build, audit, synchronisation, and environment checks. For one site, a validated Astro build contained 203 pages and 15,305 internal links with zero broken internal links. He also implemented a server-side connection from website contact forms to Odoo CRM.
What changed
Project result
The sites ran on an Astro, Node.js, Nginx, and Linux stack with repeatable deployments and verified link integrity. On one migrated property, removal of the validated legacy WordPress installation reduced server disk usage from approximately 38 GB to 19 GB while the production site continued to return HTTP 200.
Business effect
What the work made possible
Reduced legacy infrastructure overhead, improved maintainability and deployment control, preserved content relationships during migration, lowered the risk of lost leads through broken forms or links, and created a cleaner technical platform for future content growth.