Website & application migration in Seville
I migrate sites from WordPress, Joomla, Drupal, Angular, Vue and other technologies to Astro and Next.js. I plan each migration to keep SEO, content and features intact and switch over in an agreed window. I work alone and have years of experience with both legacy and modern stacks.
- I have had a wordpress.org account since 2006.
- I contributed to WordPress core for versions 7.0 and 7.1.
- I maintain 30 plugins on wordpress.org.
- I organise and speak at WordCamps.
- I have attended every WordCamp Europe from 2017 to 2026.
- Local WordPress meetup: WordPress Sevilla
A Seville company usually asks me about Astro or Next.js when its website has become harder to run than the business behind it: a WordPress install where every plugin update breaks something, a Joomla 3 site nobody dares to touch, a Drupal 7 build past its end of life, or a custom PHP framework that only a former contractor understood. Across the Andalusian capital, web estates support diverse operations: science, renewable energy and engineering firms at Cartuja Science and Technology Park (Parque Científico y Tecnológico Cartuja, PCT Cartuja) on Isla de la Cartuja, aerospace and advanced manufacturing suppliers around Aerópolis (Parque Tecnológico Aeroespacial de Andalucía) in La Rinconada and Alcalá de Guadaíra, agri-food and olive-oil exporters across the Guadalquivir valley, and hospitality, MICE and cultural tourism operators in Casco Antiguo, Nervión, Triana and Los Remedios. I take your legacy site, record everything search engines and customers already know about it, and rebuild it on a lighter frontend from Gdynia without losing the rankings, links and language versions you already have.
Is a migration worth it, or would a cleanup of my WordPress be enough?
Sometimes a cleanup is the honest answer. If the problem is a slow theme, unused plugins and no page cache, a migration only moves the same mess to a new stack. When that is the case, I state it in the written scope and recommend fixing the existing install instead. A migration makes sense when the CMS itself is the obstacle: the core version is out of support, editors fight a brittle visual builder instead of publishing, every release goes out untested, or the frontend cannot pass Google’s official Core Web Vitals thresholds (Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, Cumulative Layout Shift up to 0.1) on mobile networks.
I choose between Astro and Next.js per route group rather than treating them as interchangeable:
- Astro fits content sites, B2B engineering pages, industrial and agri-food product catalogues, hotel and event venues, and technical documentation. Pages are compiled to static HTML at build time and ship zero client-side JavaScript by default, hydrating interactive islands (such as an RFQ form, a room-type filter or a distributor map) only where needed.
- Next.js fits sites with logged-in supplier or client areas, live availability and booking flows, dynamic pricing calculators or personalised content, where server rendering and API routes justify a runtime server.
- Headless CMS options: You can keep WordPress on a locked-down subdomain as a headless editing backend via the REST API or WPGraphQL, move to a dedicated headless CMS, or store structured content in typed Git Markdown collections.
Why Seville aerospace, engineering and hospitality sites outgrow legacy CMS stacks
Organisations in Seville and its metropolitan area run into three recurring architectural bottlenecks on older monolithic platforms:
- Heavy technical documentation and tender libraries. Engineering, renewable-energy and aerospace subcontractors at PCT Cartuja and Aerópolis publish extensive certification sheets (EN 9100, ISO standards), R&D project archives, EU Horizon grant pages and PDF tender documentation. Over years of WordPress or Drupal use, media folders and custom post types accumulate thousands of URLs that external institutional partners link to directly. Rebuilding in Astro organises these into strict, schema-validated Content Collections while keeping every legacy document URL alive via edge redirects.
- Seasonal hospitality and event traffic spikes. During major Seville calendar peaks such as Semana Santa, the Feria de Abril, international congresses at FIBES (Palacio de Exposiciones y Congresos de Sevilla) and autumn cultural seasons, hotel, restaurant and venue websites face sudden surges in mobile lookups. A static or edge-cached Astro frontend serves pre-built HTML directly from the CDN without hitting a PHP/MySQL origin that can lock up under load.
- B2B export catalogues across Spanish, English and French. Agri-food producers, industrial equipment makers and logistics firms around the Port of Seville (Puerto de Sevilla, Spain’s only inland river port) sell across Europe, North America and North Africa. Replacing fragile multilingual plugins with a deterministic build-time locale router eliminates database join slowdowns and broken translation links.
What happens, step by step, during the migration?
- Inventory. I crawl the live site and merge that list with the XML sitemap, the Google Search Console performance report, analytics landing pages and, where available, server access logs. Each URL gets a row with its status code, title, canonical, language, internal links pointing to it and whether it earns organic clicks or backlinks.
- Typed content model. Posts, pages, products, categories, authors and custom fields become typed collections. In Astro that means Content Collections validated with a strict Zod schema, so an entry without a title, canonical path or valid date fails the build in CI instead of going live with a broken layout.
- URL map and single-hop 301s. Every old address either stays identical or points to exactly one new address with a single
301redirect. No redirect chains and no blanket redirects to the homepage. You get the map as a spreadsheet and versioned file to read and approve before launch. - Metadata and structured data. Titles, descriptions, canonicals, Open Graph tags and Schema.org JSON-LD (
Organization,LocalBusinesswhere accurate,Article,Product,LodgingBusiness,BreadcrumbList,FAQPage) are generated deterministically from the content model. - Staging and parity verification. The new build runs on a staging address closed to search indexing (
X-Robots-Tag: noindex, nofollow). I compare old and new page by page: status code, title, canonical, main heading, language pairs, structured data and body text completeness. - Staged or single-step cutover. Small corporate sites switch in one atomic DNS or proxy step. Larger portals move section by section behind edge routing rules on the same domain while the legacy server remains available for instant rollback.
- After launch. I submit the new XML sitemaps, then follow Search Console coverage, the 404 report and Core Web Vitals field data, adding redirects for any obscure legacy URLs that external referrals surface.
Pre-cutover verification gates for Seville migrations
Before production traffic switches to the new Astro or Next.js build, I verify six concrete gates on staging:
| Verification gate | What I test on staging | Passing criterion before cutover |
|---|---|---|
| URL & PDF preservation | Full crawl + GSC indexed pages + analytics landings + backlink targets | 100% resolve with 200 OK at the existing path or a single-hop 301 to the mapped target |
| Hreflang reciprocity | Bidirectional es, en (and any export locales) plus x-default in HTML and sitemaps | Every localized route links to itself and all siblings; zero one-way or redirecting hreflang tags |
| Structured data parity | Rendered JSON-LD compared against legacy templates per page type | Zero validation errors; Organization, LocalBusiness and FAQPage schemas intact |
| Core Web Vitals readiness | Zero-JS static HTML baseline, responsive AVIF/WebP images and font loading | Built to meet official web.dev thresholds (LCP <= 2.5 s, INP <= 200 ms, CLS <= 0.1) |
| AEPD & LSSI cookie gate | Network panel inspection on a fresh browser session before consent interaction | Zero non-essential analytics or advertising scripts/cookies executed prior to opt-in |
| Forms & booking endpoints | End-to-end submission of contact, RFQ, newsletter and booking enquiry forms | HTTP 200/201 delivery confirmed with GDPR processor disclosures and spam protection |
How do Spanish and English versions survive the move?
Castilian (castellano) is the official Spanish language of the State under Article 3.1 of the Spanish Constitution, while Article 3.2 makes other Spanish languages official only in their respective Autonomous Communities according to their Statutes. The Statute of Autonomy for Andalusia (Ley Orgánica 2/2007) establishes no second co-official language, while recognising and protecting the Andalusian linguistic modality (modalidad lingüística andaluza). Seville is the capital of Andalusia and the largest metropolitan area in southern Spain. For a Seville business website, that means Spanish (es / es-ES) is the primary version, with English (en), French (fr) or German (de) added where the company sells to international tourists, aerospace partners or export buyers.
The English and export versions are where CMS migrations most often break. WPML and Polylang store translation links in custom database tables, and a naive export loses those relationships. I export the translation groups explicitly, rebuild each group around a shared translation ID with a file per language, and generate the hreflang tags from that ID with es, en and an x-default. Before launch I verify on the built HTML that every page lists its sibling and that the sibling points back, because Google ignores a one-way pair, and a browser never warns you. Existing slugs stay intact: if the Spanish page lives at /es/servicios/ and the English one at /en/services/, both URLs survive without unnecessary redirects.
Which Spanish and Andalusian rules does the new site have to meet?
A rebuild is when legal obligations often get dropped by accident because they lived inside legacy widgets or plugins. I verify four statutory layers during the build:
- Provider identification (Aviso Legal under LSSI-CE). Article 10 of Ley 34/2002 (LSSI-CE) requires your company name (denominación social), registered address in Seville, email or direct electronic contact channel, commercial registry data (Registro Mercantil de Sevilla: tomo, folio, hoja) and tax identification number (NIF) to be permanently, easily and directly accessible. I carry the legal notice across and verify it stays linked in the global footer of every template.
- Cookies and AEPD guidelines. Article 22.2 LSSI-CE allows storing or reading non-essential data on a user’s terminal device only after informed consent. In accordance with the AEPD Guía sobre el uso de las cookies, the first banner layer must offer an explicit reject button (Rechazar) alongside the accept button (Aceptar) with equal visual prominence, plus granular purpose controls. On the new build, analytics and marketing scripts remain unexecuted until consent is granted, and legacy trackers you no longer use are removed completely.
- Data protection (AEPD and the Seville-based Andalusian Council). For private companies, the supervisory authority under the GDPR and Ley Orgánica 3/2018 (LOPDGDD) is the Agencia Española de Protección de Datos (AEPD). Seville is also the seat of the Consejo de Transparencia y Protección de Datos de Andalucía (on Calle Conde de Ibarra). Under Article 57 of Ley Orgánica 3/2018, this Andalusian authority supervises data processing by the regional public sector (Junta de Andalucía), local entities (Ayuntamiento de Sevilla, provincial bodies) and natural or legal persons providing public services on their behalf (concesionarios or public contractors). Before new forms, CDN edge nodes and hosting providers go live, I provide a complete written list of sub-processors and server regions so your privacy notice matches reality.
- Accessibility (Ley 11/2023) and Andalusian consumer rules. Ley 11/2023 transposes the European Accessibility Act into Spanish law, covering consumer e-commerce and digital contracting services from 28 June 2025 (with a statutory exemption for service microenterprises employing fewer than 10 people and under EUR 2 million in annual turnover or balance sheet total). In addition, businesses serving consumers in Andalusia must respect Real Decreto Legislativo 1/2007 (TRLGDCU) and the Andalusian electronic complaints sheet rules (Decreto 82/2022 on Hojas de Quejas y Reclamaciones). I build the new templates with semantic heading order, labelled form fields, visible keyboard focus and WCAG 2.1 AA contrast, tested with keyboard navigation and automated accessibility checks before launch.
How we work together remotely (and what stays with you at handover)
I operate WPPoland as a solo engineer based in Gdynia, Poland. When you hire me for a Seville migration, you work directly with the person writing your code and verifying your redirects:
- Written communication only. I work without phone calls, video conferences or live screen-sharing sessions. Every audit, URL map, staging link and status update arrives in writing by email or Git pull request, and I reply in writing on working days.
- Client-supplied design. If you want to change the visual appearance of your website during the move, your designer or creative agency provides the Figma files or mockups and I implement them. If you want to keep your current look, I translate your existing layout directly into clean Astro or Next.js components.
- Full ownership at handover. You keep the Git repository, the CI/CD deploy pipeline, the environment variable structure and a written record of the URL map and every decision about changed addresses. If you also want local peer references in Seville, the local community group is WordPress Sevilla. For technical background on my approach, see my Next.js and Astro migration page and headless CMS development.
How to get a written scope for your Seville website
Send me a message via the contact page with your current site address, the CMS and version it runs on, the language versions you publish, and where your traffic comes from (organic search, paid ads, newsletters, B2B referrals or booking marketplaces). I will inspect your setup and reply in writing on working days with a concrete migration scope: what moves, which addresses change, whether Astro or Next.js fits each section, and what I need from you before work starts.
Selected projects
Examples of my work.
E-commerce Development: car-mechanic-huntington.co.uk
The website project car-mechanic-huntington.co.uk was created with the aim of professionally presenting the services of a car workshop. The primary goal of t...
E-commerce Development: centrumpoludnie.pl
centrumpoludnie.pl is an information portal for a shopping centre in southern Gdansk, covering shops, promotions, news, and simple administration.
E-commerce Development: dkf.za.pl
DKF.za.pl is a website created in 2010 for the Film Discussion Club “ZA”, operating as part of the Polish Federation of Film Discussion Clubs. The project wa...
WordPress support & development in Seville
Need this service: Next.js / Astro migration in Seville?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.