Statamic Upgrade
This isn't a standalone service. It's the upgrade step for in-house teams who need their site upgraded before Statamic Migration can begin.
Why the upgrade has to come first
Migration moves your site onto a server I manage with Ploi, ready for ongoing maintenance. For that handover to work cleanly, the site needs to already be on the current Statamic release.
So the upgrade has to happen first. Either your team runs it, or I do. Either way, it's a defined piece of work that lands the site on the current version, then migration follows.
In-house upgrade
If your team has the time, running the upgrade in-house arrives at the same place. Statamic publishes a clear upgrade guide for every major release. This service is for when in-house isn't on the table.
What I do
I take a working copy of the site and get it running locally, perform the upgrade there, it's then uploaded to your new Ploi managed staging server and run it through testing before anything is touched in production.
Statamic core, Laravel, and PHP raised to the current supported versions.
Composer packages and addons updated to compatible releases.
Templates, blueprints, and custom code adjusted for breaking changes.
What I need to know
To scope the work, I'll need a few things from you:
Which version of Statamic the site is currently running.
What PHP version the server uses
Any custom code, custom field types, or third-party integrations.
Which addons are installed.
Whether the codebase is in version control, and access to the repo.
Once the site is on the current version, migration can follow. This service isn't offered as a standalone upgrade. It only runs as the step that gets your site ready for migration and the maintenance that follows.
