SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
A PHP system that has been earning money for eight years is an asset, not an embarrassment. Most of the time it needs modernising rather than replacing — and knowing which is the actual skill.
What we can show you
A PHP system that has been earning money for eight years usually needs modernising rather than replacing — and knowing which is the actual skill.
Most legacy PHP is not bad code; it is code whose context was lost. The business rules inside it are often the only written record of how the company actually works, which is exactly why rewriting from scratch loses more than it gains.
Modernisation means making change safe again: characterisation tests around the parts nobody understands, a supported PHP version, dependencies that receive security fixes, and a deployment anyone can run.
Modernise when the data model still matches the business. Rewrite when it does not, or when the domain has changed beyond what the code can express — we cost both options before recommending one.

Price
From $7,990
Timeline
3 weeks to first release
Payment
50/50 by milestone
The two options costed honestly, because the wrong choice here is expensive in both directions.
Where this stack earns its place in a project, and what we would use instead if it did not.
Systems without a framework, with logic in templates and no tests. We add characterisation tests first, then change things safely.
PHP 5.6 or 7.x to a supported version, dependency by dependency, with a rollback plan at every step.
Strangler approach: new modules in the new framework, old ones retired one at a time, business never stops.
Input validation, session handling, secrets, dependency vulnerabilities — the findings that turn up in every first audit.
The best stack is usually the one your team can maintain after we leave.
Systems that work and generate revenue, where the goal is lower risk and faster change rather than a new logo on the admin panel.
Cases where the business logic is genuinely simpler to rewrite than to decipher. We will show you the cost of both and let the numbers decide.
Rates
$28–55/hour by role
Fixed builds
From $7,990
Discounts
Dedicated −10% · partners −15%
The part that is specific to this stack rather than true of every project.
Four things we can prove, not four adjectives.

We capture current behaviour, including its bugs, so a refactor can be proven not to change it.

New code beside old, traffic moved module by module, rollback available at every step. The business never stops.

If we find a bug on the way, we report it and price the fix separately rather than quietly improving something your operations depend on.

Once the audit tells us what we are agreeing to support, Care from $790/month keeps it alive.
Industries
Legacy PHP runs quietly in logistics, manufacturing and property back offices — that is where we meet it.
Answered by the people who would do the work, not by a sales team.
An audit first: dependencies, extensions, test coverage and the paths that carry money. Then an incremental upgrade plan with a rollback at each stage.
Repair, unless the data model is wrong at the root or the domain has changed beyond what the code can express. We cost both options before recommending one.
Usually yes: parallel environments, traffic shifting and a rollback plan. Downtime windows, when unavoidable, are agreed in advance and kept short.
Yes — often the fastest setup, since they hold the domain knowledge and we bring the modernisation discipline.
Yes, on a Care plan from $790 a month, once the audit has told us what we are agreeing to support.
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
Need this stack with a senior review included?
Tell us what exists today — a green field, a legacy codebase, or a team that needs two more pairs of hands. We answer with a scope, a price and a date.
We do not take work on a stack we cannot review internally at senior level.
Tell us what you need — we'll suggest the format and the timeline. We normally reply within one business day.
or write to us directly