Website & application migration in Stockholm
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 Stockholm
You run a commercial or institutional website in Stockholm on WordPress, Joomla, Drupal, or an ageing custom framework and want to move to Astro or Next.js without losing organic search rankings or incoming enquiries. Working solo, remotely and in writing from Gdynia across the Baltic in the same Central European Time zone, I execute these migrations directly from the initial URL inventory and content schema through to Google Search Console verification after cutover. The full engineering methodology is covered on my page about migration to Next.js and Astro; this page explains what a rebuild involves specifically for a business in Stockholm.
Do I need a migration, or would optimising the existing site be enough?
Not every slow website needs a new frontend. If server caching is missing, images ship uncompressed, or twenty unused plugins are active, fixing those bottlenecks on your current CMS is cheaper and faster. A migration to Astro or Next.js pays off when the obstacle sits inside the underlying architecture: the theme loads heavy JavaScript bundles across every route, every core or plugin update feels like a production gamble, security patches get postponed because nobody knows what will break, and editors wait longer in the admin dashboard than visitors wait on the public site.
I base that recommendation on concrete measurements: real-user Core Web Vitals field data against Google’s official thresholds (Largest Contentful Paint up to 2.5 s, Interaction to Next Paint up to 200 ms, Cumulative Layout Shift up to 0.1), server response times, the number of plugins injecting frontend scripts, and the maintenance cost of recent updates. If the numbers point to a straightforward WordPress cleanup, I state that in writing before any migration scope is proposed.
Stockholm’s technology, financial and life-science sectors: where decoupled frontends excel
Stockholm is the capital and most populous city of Sweden, with roughly one million residents in the municipality (Stockholms stad) and about 2.5 million across Greater Stockholm. Across commercial districts from Norrmalm, Östermalm, and Kungsholmen to Kista Science City, Hagastaden, and Södermalm, Stockholm companies operate digital platforms with high expectations for speed, design precision, and regulatory compliance:
- Fintech, Banking and Enterprise SaaS (Norrmalm, Bibliotekstan, Kista, Södermalm): Software scaleups, payment platforms, and financial institutions headquartered in Stockholm publish bilingual or global portals (
sv,en, plus Nordic and DACH locales) that combine product marketing, security compliance documentation, and developer API guides. Moving from a monolithic WordPress install to Astro allows engineering teams to maintain technical docs in Git-backed MDX while marketing teams publish campaign landing pages without risking site-wide plugin conflicts. - Life Sciences, Medtech and Biotech Research (Hagastaden, Solna / Karolinska corridor, Uppsala axis): Clinical research companies, diagnostics vendors, and biotech spin-outs maintain strict regulatory documentation, investor relations reports (under Nasdaq Stockholm disclosure rules where listed), and multi-language product sheets. A pre-rendered Astro frontend eliminates public database vulnerabilities and guarantees that every historical PDF and URL resolves in a single hop.
- Industrial Engineering, Cleantech and B2B Consultancies (Kungsholmen, Hammarby Sjöstad, Sundbyberg): Engineering groups, sustainability consultancies, and architectural practices rely on fast mobile portfolios, structured case study hubs, and technical resource libraries. Astro handles the public content site with zero unnecessary JavaScript, while Next.js can power authenticated client dashboards or interactive calculators on a dedicated route.
How does a Stockholm migration to Astro or Next.js work in practice?
- Comprehensive URL inventory. I collect every URL that is live or receives external traffic. Google’s documentation on site moves with URL changes names the essential sources: XML sitemaps, analytics and raw server access logs, the external links report in Google Search Console, the CMS database itself, and embedded assets such as images and PDF documents (whitepapers, annual reports, product datasheets) that need permanent redirects too. Server logs routinely reveal older campaign pages and linked PDFs that appear in no sitemap.
- Version-controlled redirect map. Every legacy URL receives an explicit destination: retain the exact address, redirect via a single-hop HTTP 301 to its closest equivalent, or return a deliberate HTTP 410 when content is permanently retired. Redirects point straight at the final canonical target with zero chains and zero catch-all redirects to the homepage. Because Google advises keeping permanent redirects active for at least a year (and ideally indefinitely for visitors following older links), storing the redirect map as a file in your Git repository and edge config is far safer than relying on a database plugin setting.
- Typed content model. A legacy WordPress post or Drupal node is rarely just a title and body. Shortcodes, visual page-builder blocks, ACF fields, and embedded forms must become structured, typed fields (validated with Zod in Astro), or legacy HTML clutter follows you into the new build. Together we decide in writing whether WordPress stays on a private subdomain as a headless CMS, whether content moves to Markdown/MDX files in Git, or whether another headless CMS fits your editorial workflow better.
- Structured data and metadata parity. Page titles, meta descriptions, canonical tags, Open Graph properties, and Schema.org JSON-LD (
Organization,BreadcrumbList,Article,Product,FAQPage) move with the content. I compare them page by page between the legacy site and the staging build, because SEO plugins previously generated much of that markup automatically. - Multilingual
hreflangverification. Most Stockholm corporate sites run at least a Swedish (svorsv-SE) and an English (en) edition, and often add Norwegian (nb), Danish (da), Finnish (fi), or German (de). Google ignoreshreflangannotations unless translated pages point back to each other reciprocally and list themselves. After a migration, everyhreflangreference must point directly at the new canonical URLs, which I verify on the compiled HTML before cutover. - Staged cutover. Compact corporate sites switch in one coordinated window during low traffic. On larger domains, I migrate sections one at a time behind edge routing rules (for example, the documentation hub or blog first, then corporate service pages), keeping the rest on the legacy system until each section is verified.
Pre-cutover verification table for Stockholm migrations
| Verification area | What I check before switching production traffic |
|---|---|
| URL & PDF redirect ledger | Every indexed URL and linked PDF in Search Console and server logs returns HTTP 200 or a single 301 hop |
| Nordic & international hreflang | Bidirectional return links (sv, en, Nordic/EU locales) and self-referencing canonicals verified in HTML |
| Core Web Vitals thresholds | Templates verified against official web.dev thresholds (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1) |
| IMY & PTS privacy/cookie rules | Zero non-essential cookies or tracking scripts firing before explicit user consent under LEK (2022:482) |
| Lag (2023:254) & (2018:1937) | Semantic HTML landmarks, heading hierarchy, form labels, focus order and WCAG 2.1 AA contrast checked |
| Aktiebolagslagen footer details | Registered company name (AB), municipal seat (säte i Stockholm) and organisationsnummer verified |
What should a Stockholm business check under Swedish law before relaunching?
Rebuilding every template at once is the cleanest moment to verify compliance with Swedish language, privacy, electronic communications, accessibility, and corporate disclosure rules:
Language (Språklag 2009:600). Under the Swedish Language Act, Swedish is the principal language in Sweden (Section 4), alongside five recognised national minority languages: Finnish, Yiddish, Meänkieli, Romani Chib, and Sami (Section 7). While a private company is free to choose its publishing languages, Stockholm enterprises selling both domestically and internationally almost always run Swedish and English side by side, and public-sector suppliers frequently maintain structured multilingual access. Deciding URL prefixes (/sv/, /en/), translated slugs, language switcher behaviour (linking to the exact translated counterpart rather than the homepage), and hreflang architecture happens before content moves.
Personal data and cookies (IMY, Dataskyddslagen 2018:218 & LEK 2022:482). Sweden’s GDPR supervisory authority is the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY, headquartered in Stockholm), while Post- och telestyrelsen (PTS) supervises cookie and terminal storage rules under Chapter 9, Section 28 of the Electronic Communications Act (Lag 2022:482 om elektronisk kommunikation, LEK). In a migration, this directly affects contact forms, recruitment portals, newsletter sign-ups, analytics scripts, and embedded widgets. Before cutover, I document which data goes where, which processors handle it, and in which EU/EEA region it is stored, and I wire the frontend so zero non-essential cookies or tracking scripts execute before the visitor gives informed consent.
Accessibility (Lag 2023:254 & Lag 2018:1937). Since 28 June 2025, Sweden’s Act on the Accessibility of Certain Products and Services (Lag 2023:254 om vissa produkters och tjänsters tillgänglighet), transposing the European Accessibility Act (Directive (EU) 2019/882) and supervised for e-commerce by PTS, applies to consumer e-commerce services and covered digital services (with an exemption for microenterprises having fewer than ten employees and annual turnover or balance sheet not exceeding 2 million euros). Separately, government authorities, municipalities, and qualifying publicly funded actors have been covered since 2019 by Lag (2018:1937) om tillgänglighet till digital offentlig service, supervised by DIGG (Myndigheten för digital förvaltning), which requires a published accessibility statement (tillgänglighetsredogörelse) with a feedback mechanism. Building new Astro or Next.js components with semantic headings, alt text, keyboard operability, and WCAG 2.1 AA contrast from day one avoids expensive retrofits later.
Corporate website disclosures (Aktiebolagslagen 2005:551). Under Chapter 28, Section 5 of the Swedish Companies Act (Aktiebolagslagen), a Swedish limited liability company (aktiebolag, AB) must display its registered company name (företagsnamn), the municipality where its board has its registered seat (säte, e.g. Stockholm), and its corporate identity number (organisationsnummer, 10 digits registered with Bolagsverket) on its website and electronic communications. I verify that these statutory details remain intact across all language footers.
Common migration failure points on a Stockholm domain and how I prevent them
- Forgotten campaign and document URLs. An older campaign landing page or investor PDF that still carries external backlinks returns HTTP 404 after launch if only the XML sitemap was checked. After cutover, I test the complete historical URL list from Search Console and server logs against the live domain.
- Dropped metadata or duplicate canonicals. Missing canonical tags or unmapped meta descriptions show up in Search Console weeks later if unchecked. Before launch, I run an automated HTML diff across old and new templates.
- Search Console indexing transitions. I submit the updated XML sitemap in Search Console and monitor the Page Indexing report and Core Web Vitals field data over the weeks following launch. The Change of Address tool is used only when moving between different domains or subdomains (such as
.comto.se). - Forms and CRM webhooks. Contact forms, HubSpot/Salesforce/Pipedrive webhooks, and newsletter sign-ups are tested on staging with real submissions before the DNS switch.
How to start a Stockholm migration with me
Send me your current website URL, the CMS and version it runs on, the languages it publishes in (sv, en or others), and an overview of your main traffic sources (organic search, paid ads, newsletters, referrals) via the contact page. Read-only access to Google Search Console helps if you can grant it. I reply in writing on working days with a free initial estimate and written scope covering the URL inventory, the recommended target framework (Astro or Next.js), the content model, and a staged cutover plan.
WordPress community signals in Stockholm
Meetup: WordPress Stockholm (https://www.meetup.com/wordpress-stockholm/).
Selected projects
Examples of my work.
abovio.pl, Electronics Distribution with Extensive Product Catalog
Abovio.pl is an advanced online store project in my WordPress developer portfolio, created as an electronics distribution platform for both companies and ind...
Airhelp - WordPress Project | WPPoland
AirHelp was founded in 2013 as a start-up and has grown to become the global leader in defending air passenger rights, helping over 13 million people underst...
alextg.pl - WordPress Project | WPPoland
alextg.pl is a WordPress website for a company that helps customers obtain financing. The project focused on clear service presentation, contact flow and stable technical upkeep...
WordPress support & development in Stockholm
See also in Sweden
Need this service: Next.js / Astro migration in Stockholm?
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.