Migration Guides
This document provides guidance on migrating from other CMS platforms to Sveltia CMS. Specific instructions are provided for Netlify/Decap CMS.
Migrating from Other Platforms
Migrating from other CMS platforms to Sveltia CMS can vary in complexity depending on the source CMS. Below are guides for some of the more common platforms.
Netlify CMS or Decap CMS
Sveltia CMS is designed to be a direct successor to Netlify CMS (now Decap CMS). A migration from Netlify/Decap CMS to Sveltia CMS is intended to be as seamless as possible. This guide will walk you through the necessary steps to migrate your existing setup to Sveltia CMS.
Our Showcase also features various sites that have been migrated from Netlify CMS and Decap CMS. Check out these examples to see how other users have successfully transitioned to Sveltia CMS.
- Examples of sites migrated from Netlify CMS
- Examples of sites migrated from Decap CMS
- Discover more sites with GitHub search
Static CMS
Static CMS was a community fork of Netlify CMS that introduced several unique features. While we don’t have a full migration guide for Static CMS, many of the concepts and configurations are similar to those in Netlify CMS. We have documented some of the key differences and considerations when migrating from Static CMS to Sveltia CMS.
Pages CMS
Pages CMS is also inspired by Netlify CMS and shares similar concepts and configurations. Sveltia CMS has more features and flexibility, while Pages CMS offers a hosted solution with a more limited feature set.
We don’t have a dedicated migration guide for Pages CMS yet, but you can ask your AI assistant to convert your Pages CMS configuration to Sveltia CMS format. Check out the Start Guide for more information on how to get started with Sveltia CMS.
Other Headless CMSs
We’ll continue to expand our migration resources to cover popular headless CMS platforms. If you are using a different CMS and are interested in migrating to Sveltia CMS, check back here for future migration guides or just look at the Start Guide to get started.
If your current CMS is Git-based, the migration process should be relatively straightforward. Typically, you will need to configure your Sveltia CMS setup to match your existing content structure.
See our Showcase for examples of sites that have successfully migrated from other headless CMS platforms to Sveltia CMS.
- Examples of sites migrated from DatoCMS
- Examples of sites migrated from Keystatic
- Examples of sites migrated from TinaCMS
Traditional CMSs
More and more users are choosing to switch from traditional CMS platforms, especially WordPress, to static sites powered by Sveltia CMS. This approach is often preferred by small site owners and developers because of its cost-effectiveness, performance, flexibility and security benefits.
The migration process involves exporting content as static files, typically in Markdown format, and creating a new site from scratch using your preferred framework. Our Start Guide can help you get started with Sveltia CMS.
Our Showcase also features various sites that have been migrated from WordPress and other platforms, demonstrating the possibilities and benefits of using Sveltia CMS.
- Examples of sites migrated from WordPress
- Examples of sites migrated from Joomla
- Examples of sites migrated from Drupal
- Examples of sites migrated from Ghost
Website Builders
Users are also migrating from website builders like Wix and Squarespace to Sveltia CMS. The migration process is similar to that of traditional CMS platforms, involving exporting content and creating a new site with Sveltia CMS.
See our Showcase for examples of sites that have successfully migrated from these website builders to Sveltia CMS.
- Examples of sites migrated from Wix
- Examples of sites migrated from Squarespace
- Examples of sites migrated from GoDaddy Website Builder
- Examples of sites migrated from Google Sites
Migrating from Earlier Versions of Sveltia CMS
See the detailed migration instructions here: