Skip to content
Back

Moving from Silverstripe to Statamic: when it makes sense and how it works

Mak Kordić •

If your website runs on Silverstripe 3 or 4, it no longer receives security fixes: support for version 3 ended in September 2021 and for version 4 in June 2025. You have two routes: upgrade to Silverstripe 6, or move to another system. Moving pays off mainly when you cannot find a team to maintain Silverstripe.

At CNJ we worked with Silverstripe for years and are still listed in its partner directory. That is why we regularly get requests to take over maintenance of existing sites. We no longer take on Silverstripe maintenance, but we can move a site to a system we do maintain. This article explains when that makes sense, when it does not, and how the migration works.

Where Silverstripe stands today

Silverstripe is not an abandoned system. It is developed by a company in New Zealand, version 6 was released in June 2025, and the latest minor release came out in October 2026. The problem with most sites that reach us is not the system but the age of the installation.

According to endoflife.date, the situation is:

  • Silverstripe 3: security support ended on 30 September 2021.

  • Silverstripe 4: security support ended on 10 June 2025.

  • Silverstripe 5: security fixes until 30 April 2027.

  • Silverstripe 6: the current version.

The second problem is finding developers. Silverstripe's community is strongest in New Zealand and Australia. In Slovenia, very few teams still work with it. If your contractor stops, there is almost no replacement.

The third problem is that upgrading between major versions is not a button. Going from 3 to 4 meant rewriting a large part of the code, which is why many sites stayed on the old version. A site on version 3 today does not get to version 6 by upgrading; it gets there by being rebuilt.

Three options

1. Stay and upgrade to Silverstripe 6

This makes sense if the site is really an application: a lot of custom business logic, integrations with other systems, complex user accounts. The condition is a team that knows Silverstripe and will still maintain it three years from now. For a Slovenian company that will almost certainly be a team abroad.

2. Move to Statamic

This makes sense if the site is mostly content: pages, news, forms, several languages. And if you want a contractor you can call in your own time zone. It pays off most when you are planning a redesign anyway.

3. Move to another system

Statamic is not the only choice. WordPress has the most developers and plugins, but also the most ongoing maintenance and security updates. Umbraco is a good fit for organisations that work in a Microsoft environment. The right route depends on who will maintain the system and what your editors need.

Why Statamic

For sites coming from Silverstripe, we recommend it for four reasons.

  • Same language, wider community. Statamic is also written in PHP and runs on similar hosting. It is built on the Laravel framework, which many developers know, so changing contractors is not hard.

  • Content as files. By default Statamic stores content in files, not in a database. Every change can be committed to Git automatically, which gives you a history of the content, simple backups and a test environment without copying a database. A database is still available for large volumes of content.

  • Familiar for editors. The control panel has block-based editing, similar to the Elemental module in Silverstripe, a preview before publishing, roles and permissions, and several languages.

  • A separate front end, if you want one. Content can be read through an API by a separate website or app. That is how cnj.si works.

It is fair to state the downsides too. Statamic has fewer ready-made add-ons than WordPress. The Pro edition, which most business sites need, is paid: at the time of writing, November 2026, it costs $349 per site with one year of updates, then $99 a year. The Core edition is free but has a single user account.

What maps to what

A migration is not a copy; it is a translation from one content model to another. Most concepts have a counterpart.

  • Page types become collections with blueprints.

  • DataObjects become collections or taxonomies.

  • Elemental blocks become sets in the Bard editor.

  • Files and images move into the asset library.

  • Members and groups become users and roles.

  • UserForms forms become Statamic forms.

  • Multilingual content with Fluent becomes several linked sites, one per language.

  • .ss templates are written again, as Statamic templates or as a separate front end.

What cannot be mapped is custom business logic. It has to be written again, which makes its size the main driver of cost.

How the migration works

  • Inventory. We list the content types and the number of records, modules, integrations with other systems, forms, and every URL that search engines know.

  • Deciding what not to move. Ten-year-old news and pages nobody visits often stay behind. Less content means a cheaper migration and a better site.

  • Content model. We set up collections and fields in Statamic. This is the moment to fix what bothered you in the old system.

  • Export and import. We export the content from the Silverstripe database to CSV or XML files. Statamic has an official importer add-on that imports entries, taxonomy terms and users from those files and maps fields through an interface. Block-based content and relations between records need custom transformers.

  • Templates and design. The front end is built again. If a redesign was planned, this is the time.

  • Redirects and launch. Every old URL gets a redirect to the new one. The old site stays reachable read-only for a while, so you can check whether anything is missing.

What not to forget

These are the places where migrations most often go wrong.

  • Internal links in text. Silverstripe stores links and images inside content as shortcodes with a record number, not as URLs. They have to be converted on export, or you get a site full of dead links.

  • Redirects. Without them you lose the search traffic you spent years building.

  • Forms. Move not only the fields but also where the notifications go and who reads them.

  • User passwords. As a rule they cannot be transferred. Users set a new one the first time they log in.

  • Search, scheduled tasks and integrations with email or CRM systems. On the old system they work quietly, so they get forgotten.

  • Old personal data. Form submissions from years ago are often something you no longer have a reason to keep. A migration is a chance to delete them.

When we do not recommend moving

If the site is on Silverstripe 5 or 6 and you have a contractor who maintains it, there is no reason to change. The same applies if the site is really an application with a lot of custom logic: upgrading will be cheaper than rebuilding. We recommend moving when the site is mostly content, the installation is old, and there is nobody to maintain it.

How to start

Send us the address of the site and, if you have it, access to the code. We make the inventory and tell you whether upgrading or moving is the better deal, and what we would and would not migrate. If it turns out that an upgrade with your current contractor is the better route, we will tell you that too. Get in touch or see the Build & Launch package.

Frequently asked questions

Is Silverstripe abandoned?

No. Version 6 was released in June 2025 and gets regular updates. What is abandoned are the older versions: 3 since 2021 and 4 since June 2025.

Can we stay on Silverstripe 4?

The site will keep working, but without security fixes. The risk grows every month, especially if the site collects personal data through forms or has user logins.

What does moving to Statamic cost?

It depends on the amount of content, the number of content types, custom functionality, and whether you redesign at the same time. That is why we set the price after the inventory. The Statamic Pro licence is a one-off $349 with one year of updates.

Is search ranking preserved in a migration?

Yes, if every old URL is redirected to its new one and page titles and descriptions are kept. A short fluctuation after launch is normal; a lasting loss is almost always caused by missing redirects.

Will editors manage in the new system?

As a rule, quickly. Block-based editing is similar to Silverstripe with the Elemental module, and the control panel is simpler. A short introduction is usually enough.

Why not WordPress?

WordPress is a legitimate choice, especially if you already have a team for it. It needs more ongoing maintenance, because a site depends on plugins from different authors. Statamic has fewer of those dependencies, which makes maintenance more predictable.

We write about it. We also build it.

Let's talk about your project

A 30-minute call to understand what you're building and how cvan we help. No brief required.

Prefer email?

info@cnj.si