Website & application migration in Florence
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 Firenze Community
Florence is the capital of Tuscany, with about 361,000 residents in the city and about 1.5 million in the Florence, Prato and Pistoia metropolitan area. Its economy leans on tourism, fashion and industry, which means many local sites serve two audiences at once: Italian customers and visitors who search in English. A migration has to keep both of them finding the same pages after the switch. This page describes how I move a site from WordPress, Joomla, Drupal or an old framework to Astro or Next.js, and what I check so that search traffic survives it.
When is migrating to Astro or Next.js worth it for a Florence business?
Migration pays off when the current CMS holds back speed, security or publishing, and smaller fixes have already been tried. Typical signs: a slow server response on shared hosting, an admin panel slower than the public site, plugin updates nobody dares to run before the tourist season, and a release process without any tests. If removing a few heavy plugins and adding caching would fix the problem, that is the cheaper answer and I will tell you so.
Astro suits content sites: hotels, restaurants, small shops, studios with portfolios. It ships plain HTML by default and adds JavaScript only where a component needs it. Next.js fits when the site behaves more like an application: logged-in areas, booking flows, personalised pages. Both can read content from a headless WordPress, so the editing side does not have to change on day one. More on the trade-offs on the Next.js and Astro migration page and the headless CMS development page.
How do I keep my URLs and rankings during the move?
The URL map is the core document of the project. I build the list of old URLs from four places: the XML sitemaps, the server logs, analytics and the links report in Search Console. That list includes images and PDFs, not only pages, because people link to those files directly.
Each old URL gets one line: where it goes on the new site, or why it is retired. Then:
- every moved URL gets a permanent redirect (301 or 308) straight to its final destination, with no chains,
- retired pages point to the closest relevant page, never to the homepage in bulk,
- the redirects stay in place for at least a year, which is Google’s own recommendation, and in practice I leave them indefinitely,
- internal links in the content are rewritten to the new URLs, so visitors do not pass through redirects at all.
If the domain itself changes, for example from an old .com to a new .it, I also file a Change of Address in Search Console for every verified variant of the old domain. For path changes on the same domain that step is not needed.
What happens to the Italian and English versions?
Multilingual WordPress sites usually run on a plugin such as WPML or Polylang, and each stores translations differently. I first export the translation groups: which Italian page pairs with which English one. On the new site that relationship becomes explicit in the content model, not hidden in a plugin table.
Hreflang is where migrations quietly break. Google ignores the tags unless every language version links back to the others, the codes must be valid ISO language codes (it, en, or en-GB with a region), and the URLs must be absolute. I check this on the built HTML, because a correct-looking CMS setting can still render a broken pair.
What moves besides the text?
The content model decides how much editing pain you keep. I map each content type (pages, posts, rooms, products, events, team members) to a typed collection with required fields, so a missing title or image fails the build instead of reaching production. Structured data moves with it: Organization, LocalBusiness, Product or Event markup is generated from those fields rather than pasted into each page. Titles, meta descriptions and canonicals carry over unchanged unless you decide otherwise; a migration is a bad moment to rewrite every snippet.
Forms, newsletter sign-ups and tracking scripts are listed separately. Each one either gets a working replacement or is dropped on purpose, with a note in the URL map.
What about data protection and accessibility rules in Italy?
The supervisory authority for the GDPR in Italy is the Garante per la protezione dei dati personali. A migration is a natural point to list every third-party service the site sends data to: analytics, fonts, maps, booking widgets, chat. I document where each one is hosted and whether it loads before or after consent, so you can check the list against your privacy notice.
On accessibility, Italy transposed the European Accessibility Act through Legislative Decree 82/2022, and AgID is the supervisory authority for the digital services it covers. Whether your site falls under it depends on what you sell and how, which is a question for your legal adviser, not for me. What I can do technically is make sure the new templates do not regress: one H1 per page, real headings, labelled form fields, alt text carried over from the media library, and keyboard navigation that works on menus and booking forms.
How does a staged cutover work?
- A staging copy of the new site is built from a full content export and blocked from indexing.
- A script requests every URL in the map and checks the status code and the final destination. The cutover waits until every line passes.
- I compare rendered titles, canonicals, hreflang and structured data between the old and new page for a sample from each content type.
- The switch happens outside your busy hours. If the site moves section by section, edge rules send each section to the new frontend as it is ready.
- The new XML sitemap goes to Search Console.
What can go wrong, and how do I check for it?
- Redirects that loop or chain. Caught by the status check before launch and repeated after it.
- Old URLs that never appeared in the sitemap. Server logs and backlinks expose them. They are the reason the map is built from four sources, not one.
- A noindex left over from staging. I check the robots meta tag and the HTTP headers on the live site in the first hour.
- Rankings that wobble. Some movement is expected. In Search Console the old URLs should drop out of the index while the new ones gain impressions over the following weeks. If an important page loses traffic and stays down, I compare the old and new versions of that page first: content, internal links, headings.
How do I start a migration with you?
Send me the current site address, the CMS and its version, the languages you publish in, and where your traffic comes from (search, booking platforms, ads, social). With that I prepare a written scope: what moves, what is retired, how the cutover runs, and what I need from your side. At the end the repository, the deploy pipeline, the URL map and a short publishing note stay in accounts you own.
FAQ
Why are Florentine luxury hospitality, fashion, and artisanal businesses migrating to Astro?
Florence is a global cultural and commercial destination, blending luxury hospitality, high-end leather manufacturing, fashion houses, and architectural tourism. Legacy WordPress setups burdened by dozens of plugins lead to slow TTFB on mobile connections, high hosting expenses, and vulnerability risks during high-traffic tourism seasons. Migrating to Astro removes unnecessary JavaScript from the critical path, pre-compiling pages to pure static HTML that loads instantly across global networks while securing complete immunity from database-level attacks.
How do you preserve Italian and English search rankings during the transition?
Before touching production code, I crawl every existing URL, metadata tag, canonical link, and image asset across both language branches. Each legacy endpoint receives a permanent 301 redirection rule configured at the edge or maintains its exact canonical URL. Reciprocal hreflang tags (it-IT, en) are verified on rendered static output to guarantee search engines index the appropriate regional variants without confusion.
Can our Florentine editorial team maintain catalog updates through WordPress?
Yes. Your existing administrative dashboard can be decoupled, allowing WordPress or Strapi to operate solely as a content API. Creative directors and copywriters continue updating collections and room rates within their standard workspace, while Astro compiles and distributes static pages automatically upon publication.
What Italian and European regulations are incorporated into the migration?
Every migration strictly complies with the EU GDPR under Garante per la protezione dei dati personali supervision, Italian Legislative Decree 196/2003 (Privacy Code), and European Accessibility Act mandates under Legislative Decree 82/2022 (WCAG 2.2 AA). Typefaces, client scripts, and imagery are bundled locally within EU hosting perimeters, preventing unvetted telemetry transmissions to international cloud infrastructure.
What is the expected delivery timeframe for a Florence website migration?
A typical corporate replatforming covering 15 to 45 unique page templates, multilingual translations (Italian, English), and custom booking or catalog forms spans approximately 3 to 5 working weeks from initial crawl analysis to production cutover.
Selected projects
Examples of my work.
Corporate Website: centrum-csr.com
centrum-csr.com is a modern online platform dedicated to promoting the concept of Corporate Social Responsibility (CSR) and sustainable development. The webs...
Corporate Website: DIGITAL WORLD CAPITAL LLP
Digital World Capital LLP is an alternative investment manager specializing in the telecommunications and media sectors on a global scale. The company focuse...
Corporate Website: DUNE Resort
In the eastern part of Mielno, an exclusive apartment complex by the Baltic Sea, DUNE Resort, is being developed. This exceptional investment evokes the lu...
WordPress support & development in Florence
Need this service: Next.js / Astro migration in Florence?
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.