SvelteKit to WordPress: The Complete Migration Guide

SvelteKit is the framework a lot of developers wish more teams used: compiled output that ships minimal JavaScript, first-class TypeScript support, sensible defaults, and a genuinely elegant reactivity model. Its weakness is the same as every modern framework's — editorial workflow. New content is a git push. Non-technical stakeholders either learn Markdown and the CLI or wait for a developer with build access. Migrating to WordPress unlocks the editorial workflow without giving up Svelte's compiled interactivity. Blog posts become database rows editors can update in a browser. Marketing pages become templates non-technical staff can customize through the block editor. Meanwhile, everything Svelte compiled — the animations, the reactivity, the interactive components — ships inside the WordPress theme and behaves exactly the way it did on your Vercel or Netlify deployment. The second reason is longevity. SvelteKit is excellent but young, and its adapter API has changed over major versions. WordPress has run the same core PHP APIs for two decades. If long-term maintainability is a business concern, WordPress is the safer bet for the presentation layer even when Svelte is the better choice for the components inside it.

With adapter-static configured, `vite build` produces a fully pre-rendered site the pipeline consumes directly. Every route in the output ships as a WordPress template. Svelte components compile into the same JavaScript they always did, and that JavaScript enqueues into the WordPress theme so hydration keeps working. Stores keep their state. Transitions keep transitioning. Actions and use directives keep firing. Styles compile through Svelte's scoped-styles pipeline into hashed class names, which stay hashed inside the theme's CSS file. Assets from `static/` copy into the theme root, and assets imported from Svelte components get fingerprinted into `assets/`. What does not carry over is anything that required a Node process — form actions, server-only load functions, hooks.server.js. Those get flagged in the audit and need a WordPress-side implementation before your site is functionally complete.

Install adapter-static and update svelte.config.js: ```js import adapter from '@sveltejs/adapter-static' export default { kit: { adapter: adapter({ fallback: 'index.html' }) } } ``` Add `export const prerender = true` to your root +layout.js so every route pre-renders by default. For routes that cannot pre-render (authenticated dashboards, dynamic API-driven pages), set `prerender = false` explicitly and decide whether to reimplement them post-migration or leave them as SPA fallbacks. Run `npm run build` locally and inspect the `build/` folder. Every page you expect should be present as an .html file. If any are missing, either add them to `kit.prerender.entries` in svelte.config.js or make sure they are linked from somewhere the crawler can discover.

Upload your ZIP or connect GitHub. The pipeline detects SvelteKit through the `@sveltejs/kit` dependency and runs vite build in production mode. Because adapter-static already pre-renders, headless Chrome only needs to validate that the pre-rendered HTML matches the runtime behavior — a much faster pass than starting from scratch. Static routes become WordPress pages. Dynamic routes become templates. Assets get rewritten. The output is a downloadable WordPress theme, usually within about five minutes.

Install a caching plugin, an SEO plugin, and an SMTP plugin — same trio as every other migration. If your SvelteKit site used form actions to submit contact forms, decide whether to use Contact Form 7 (free, universally understood) or a WordPress REST endpoint that mirrors your action handler. If you had server-only load functions that fetched from a database, port them to WordPress REST endpoints. The @wordpress/api-fetch pattern is close enough to fetch() that most Svelte components need no changes to their onMount fetch calls.

Do not skip switching to adapter-static. Trying to migrate a Node-adapter build produces a pile of unusable server code that the theme cannot enqueue. Do not leave server-only load functions in the tree unmigrated — they will silently fail after conversion and take content with them. Do run the free preview. SvelteKit's tight compilation means differences between the original and the WordPress render are usually zero, but occasionally a transition or scroll behavior diverges and the preview is where you catch it. Do not forget to remove +server.js API routes from the audit output. Every one of them needs a WordPress REST endpoint or a serverless function replacement, and forgetting one means an entire feature quietly stops working.

Upload on the homepage or connect your repo. Preview the WordPress render for free before paying, and verify every route, every transition, and every store hydrates correctly. Conversion typically takes about five minutes.