Compatibility
A clear fit before you move.
Bring your website to Originless. Keep your existing editor or make updates with our AI assistant.
Your CMS, connected when you need it. We build the publishing connection your website needs as part of your migration. Keep your familiar editor or make updates with our AI assistant, with the scope agreed before you move.
Keep your CMS in a private editing workspace
| Platform | Your editing and publishing path |
|---|---|
| WordPress | Keep WordPress and compatible editing tools in a private capsule. Public marketing sites and blogs publish independently; commerce and membership features need separate assessment. |
| Statamic | Keep the control panel and publish generated output. Forms and other live features are handled as part of your migration. |
| Kirby | Keep the Panel, project and content files. Review custom routes, media and external data before publication. |
| Grav | Keep the Admin interface and file-based content. Themes and dynamic plugins need a compatibility review. |
| ProcessWire | Keep the existing editor, templates and content. Custom page behavior determines migration scope. |
| Craft CMS | Keep the control panel and private preview. Publish content pages independently; Craft Commerce needs a separate solution. |
| Joomla | Keep the native administration interface. Publish articles and marketing pages independently; extensions and member features need review. |
| Ghost | Keep the writing experience for public blogs. Memberships, paid access, newsletters and social features require separate services or assessment. |
| Drupal | Keep the editor and content workflows. Custom modules, access rules and complex content views determine the work required. |
| TYPO3 | Keep the backend and publishing workflow. Languages, workspaces and extensions need a site-specific review. |
| MODX | Keep the Manager and existing content. Custom snippets, forms and live behavior need review. |
| Silverstripe CMS | Keep the CMS interface and project. Publish public content independently; private assets and custom application behavior need assessment. |
| Concrete CMS | Keep in-context editing in the private source. Review blocks, themes and add-ons before publication. |
| October CMS | Keep the backend, themes and content. Interactive components and custom application features need review. |
| Wagtail | Keep the editor and private preview. Custom application views, images and search determine compatibility. |
| django CMS | Keep native content editing. Custom applications and plugins need their own compatibility assessment. |
| Umbraco | Keep the backoffice for modern, compatible projects. Legacy installations may need modernization before a capsule migration. |
| Strapi | Keep the admin interface and build the public frontend from published content. Live visitor requests to the CMS must be removed or separately handled. |
| Directus | Keep the editing interface for content projects. Realtime applications and operational databases are a separate use case. |
| Payload | Keep the admin interface and existing project. Public application features must be assessed separately from content publishing. |
| Keystone | Keep the admin interface and content model. Suitable frontends can publish independently; live application APIs need separate treatment. |
Keep your Git or desktop editor
| Platform | Your editing and publishing path |
|---|---|
| Decap CMS | Keep the Git-backed editor and publish a repository build. Authentication, media and previews remain part of the editing setup. |
| TinaCMS | Keep TinaCloud or a compatible private backend and build from the project's content. Preview and authentication need to be preserved. |
| Publii | Keep the desktop CMS and publish its complete static output through Originless. |
Keep your hosted content editor
| Platform | Your editing and publishing path |
|---|---|
| Contentful | Keep the content editor and use published content during a website build. Preview, media and publishing events need an integration. |
| Sanity | Keep Studio and Content Lake. Build the public website separately and preserve the editing preview. |
| Storyblok | Keep the visual editor with a compatible preview and publication connection. Build the public release from approved content. |
| DatoCMS | Keep the editor and build the existing frontend from published content. Review media and any live content requests. |
| Prismic | Keep the editor and content service. Generate the public site separately while preserving a private editing preview. |
Keep your visual site builder
| Platform | Your editing and publishing path |
|---|---|
| Webflow | Keep Designer and content editing in a paid Workspace. Eligible static exports can use a free Starter Site plan with Originless hosting. CMS-driven sites need a publishing integration because native export omits Collection content. |
| HubSpot Content Hub | Keep the hosted editor and publish exported pages and blog content. CRM forms, personalization, memberships and workflows need separate handling. |
| Duda | Keep the original project and publish through repeat exports. The editor does not edit externally hosted files; dynamic pages and other omitted features need assessment. |
Import your site. Update it with AI.
| Platform | Your editing and publishing path |
|---|---|
| Wix | Import your Wix website into Originless, then make updates using the AI assistant. |
| Squarespace | Import your Squarespace website into Originless, then make updates using the AI assistant. |
| Framer | Import your Framer website into Originless, then make updates using the AI assistant. |
The right fit depends on your website
Publish public pages, blogs, portfolios and documentation independently from your editing environment. Forms, search, commerce, accounts and personalized features need their own review, even when the CMS itself is compatible.
Known compromised sites require separately scoped cleanup before publication. Standard publication packages are up to 1 GiB; larger sites need a review. This is separate from your retained-storage allowance.
Platform guide updated October 8, 2026. Your migration includes a review of the themes, extensions and features your website uses.
Check my website