SilverStripe Development Australia and New Zealand

Migrations, upgrades and long term support in SilverStripe, for organisations publishing more than a template can hold.

Mostly migrations, upgrades and the work after

  • Migrations onto SilverStripe

    Content moved across from WordPress or another CMS with custom scripts, preserving URLs so nothing that ranks loses its address.

  • Version upgrades

    Moving from older SilverStripe onto the current release, including the module and template work that comes with it.

  • Taking over an existing site

    A review of the codebase you already have, then a retained developer who knows it, rather than someone relearning it every time.

  • New builds

    Custom page types and content blocks modelled on how your team actually publishes, rather than a page builder that lets the design drift.

  • Design systems in code

    Type scale, spacing, colour and components defined once and mirrored in the CMS, so what gets designed is what gets built.

  • Ongoing development

    A retained developer who already knows your codebase, rather than someone relearning it every time you need a change.

How a SilverStripe project runs

  1. Review

    We read the existing site and its content model before proposing anything. On an upgrade or a migration that review is most of the value, because it is where the surprises live.

  2. Model and build

    Page types and blocks are modelled around your real editorial workflow, then built. You get a staging site to publish on while the build is still moving.

  3. Migrate and launch

    Content migrated, redirects mapped, editors trained. Then we stay available, because a CMS is something you live with rather than something you launch.

SilverStripe work

Common questions

For content heavy sites it gives you a content model that matches how your team publishes, instead of a page builder that lets every new page drift from the design. It is also a smaller attack surface to maintain.

Yes. We pull content through the WordPress REST API with custom migration scripts and preserve URLs, so nothing that was already ranking loses its address.

Yes. Upgrades usually involve module replacements and template work as well as the core version, so we review the site first and give you a written scope of what the upgrade actually involves.

Often. We start with a review so you get an honest read on the state of the codebase before committing to anything ongoing.

Yes. We work with organisations across Australia and New Zealand, and a good deal of our SilverStripe work is in New Zealand.

Ready to start?

Tell us what you are trying to build. We reply within one business day.