Sylius 1.14 security support ends in 58 days
Sylius 2 upgrade.
I upgrade Sylius 1.x stores running in production to Sylius 2, without stopping sales. I built Sylius Upgrade Analyzer, the open source tool listed on the Sylius Store that measures this work.
I have already upgraded production Sylius stores for my clients. Their names stay confidential, and I am happy to walk you through those projects on a call. You talk directly to the person writing the code, in English or French.
Support calendar
| Version | Security fixes | What it means |
|---|---|---|
| Sylius 1.13 | Ended 30 April 2025 | Upgrade to 1.14 first |
| Sylius 1.14 | 31 December 2026 | Last 1.x release, the starting point of every upgrade |
| Sylius 2.0 and 2.1 | Ended (28 Feb and 30 Sep 2026) | Do not target them |
| Sylius 2.2 | End of March 2027 | Possible step if your server cannot run PHP 8.3 yet |
| Sylius 2.3 | Ongoing | Recommended target: PHP 8.3, Symfony 6.4, 7.4 or 8 |
Sources: Sylius release cycle and endoflife.date.
What actually changes in Sylius 2
Front end. Semantic UI and jQuery are replaced by Bootstrap 5, Symfony UX and Stimulus. Your theme and custom admin screens are rewritten.
Templates. Template overrides and Sonata block events give way to Twig Hooks. Usually the largest item.
Order flow. winzou/state-machine is replaced by Symfony Workflow. Business rules hooked to order, payment or shipping states move.
Payments. Payment Requests arrive next to Payum, and the core Stripe and PayPal Express gateways are gone.
API. API Platform 2.7 moves to 3 and then 4. Headless front ends, mobile apps and ERP connectors need retesting.
Platform. PHP 8.2 or later (8.3 for 2.3), SwiftMailer replaced by symfony/mailer, over 150 classes removed, services private by default.
How I run an upgrade
- 1. Measured diagnosis. I run Sylius Upgrade Analyzer on your code and give you every blocking point, ranked by severity, with an estimate in days. Free of charge.
- 2. Target and plan. 2.3 or an intermediate step, which plugins to keep, replace or rewrite, in what order, and when to switch.
- 3. Preparation on 1.14. Latest patch, PHP upgrade, deprecations removed, automatic fixes applied and reviewed, all without touching the live store.
- 4. Upgrade on a dedicated branch. Twig Hooks, theme, workflows and payments rewritten, with the money paths tested at each step: search, cart, checkout, emails, invoices, exports.
- 5. Switch without stopping sales. Rehearsal on a copy of production with real data, switch at the quietest hour, rollback ready, then monitoring and minor 2.x upgrades.
The tool behind the estimate
Sylius ships no official Rector set for upgrading the core from 1.14 to 2.0. Sylius Upgrade Analyzer fills that gap: 49 analyzers built from the official UPGRADE files, more than 40 automatic fixes, effort estimates and a sprint planner. It runs locally, so your code never leaves your machine. It is open source under the MIT licence, on GitHub, the Sylius Store and Packagist.
composer require --dev pierre-arthur/sylius-upgrade-analyzer
vendor/bin/sylius-upgrade-analyzer sylius-upgrade:analyze --target-version=2.3Common questions
When does Sylius 1.14 support end?
Bug fixes for Sylius 1.14 ended on 31 December 2025 and security fixes end on 31 December 2026. Your store keeps running afterwards, but a vulnerability found later will not get an official patch.
How long does a Sylius 1 to 2 upgrade take?
From a few weeks for a store close to the standard to several months for a heavily customised platform. The free diagnosis gives you a realistic figure for your own code before you commit.
Which version should I target?
Not 2.0 or 2.1, which no longer receive security fixes. I recommend 2.3, which requires PHP 8.3. If your hosting cannot move to PHP 8.3 yet, 2.2 is a possible step, supported until the end of March 2027.
Will my plugins work on Sylius 2?
Not all of them. The analyzer checks every plugin in your composer.json against the Sylius Store and Packagist. For the others I suggest a replacement, a port or dropping the feature.
Will the store go offline?
No. The work happens on a separate branch and environment, the switch is rehearsed on a copy of production, and a rollback is ready.
Do you work with agencies?
Yes, as a white-label subcontractor. The analyzer can audit several projects and produce a consolidated view, so an agency knows which stores to upgrade first.
Free upgrade diagnosis
Tell me your Sylius version and, if you can, your list of plugins. I reply personally within one working day, run the analysis on your project and send you a commented report with an estimate in days. It is yours to keep, whoever does the upgrade. More about me: freelance Sylius developer.