M's Works

Menu

PHP migration and recovery of the software you already have.

Version upgrades, projects abandoned by the supplier, code nobody understands anymore. We get it back into production without stopping it. From Palermo, across Italy.

Request a technical auditSee the projects
«Poi sono entrato in contatto con M's Works e abbiamo risolto ogni singolo problema.»
Luca de Filippis, Finanzamille Inc. · excerpt on Trustpilot

Sound familiar?

And what staying this way costs you, every month.

  • Your host is forcing a PHP upgrade and you're afraid the site will break.

    Putting it off doesn't stop the clock: a version with no more fixes stays open to every new flaw. And sooner or later the host upgrades anyway, on its own schedule.

  • Whoever built it doesn't answer anymore: you have neither the code nor the access.

    Every change, even a small one, is stuck. If the domain expires or the server goes down, nobody can get in.

  • You've been told the only option is to rebuild everything from scratch.

    You pay again for what you already paid for. And the rules the old software followed, without anyone writing them down, only show up once they're gone.

What we do

01

Version migrations

PHP 7.4 → 8.4, WordPress and WooCommerce, dated JavaScript frameworks towards React and Next.js. Tested on staging, migrated without stopping production.

02

Recovery of abandoned projects

Supplier gone, credentials lost, a repository you've never seen: we recover access, domains and code and give you back what you've already paid for.

Also

Code audit

What it does, where it's fragile, what's abandoned.

Performance

Slow queries and overlapping plugins.

Security hardening

Stale dependencies and unsupported versions.

Server migration

Hosting, domains and certificates, with rollback.

Software back on its feet, with the client's name on it

«Da imprenditore, ho speso migliaia di euro tra vari freelance e piattaforme come Fiverr per creare un sito web all'altezza delle aspettative. Risultato? Migliaia di euro buttati e nessun risultato concreto. Poi sono entrato in contatto con M's Works e abbiamo risolto ogni singolo problema.»

Luca de Filippis

Finanzamille Inc.

Excerpt · verified review on Trustpilot
Read the case studyfinanzamille.com ↗
Members area: the platform's news section
The platform landing page on a phone

A subscription platform, rebuilt on infrastructure they own

0.2%rows dropped when migrating the archive, all of them users deleted years earlier

An unsupported booking system replaced, with every old address redirected

Priolo the Barbers · Palermo, since 1982

Case study →

Why not rebuild from scratch, or pay for a few fixes by the hour?

They're fair choices, and sometimes they're enough. If the software can't be saved, the audit says so. Here's what changes.

What you know before starting

M's Works: The audit: what's inside, how many days it takes, whether it's worth it.

Rebuild from scratch: A quote for what you want, not for what you have.

Fixes by the hour: Not much: the code gets discovered as the work goes.

The software you have

M's Works: What holds up stays, the rest gets changed.

Rebuild from scratch: It's thrown out, along with the rules it held.

Fixes by the hour: It stays as it is, with one more patch.

Production while the work happens

M's Works: Staging, tests and a rollback ready, then the agreed window.

Rebuild from scratch: The old one stays on until the new one is ready.

Fixes by the hour: It depends: sometimes the work happens on the live site.

Access and code

M's Works: Documented and handed to you. The code is 100% yours once paid.

Rebuild from scratch: It depends on what the contract says.

Fixes by the hour: It depends on who holds them today.

The first step is a free call.

Tell us what you have and what no longer holds up. If the code needs reading, we propose a technical audit: that's where we see what's inside, how many days it takes and whether it's worth doing.

What you get
  • A reply within 24 hours.
  • A free first call about what you have and what you want to achieve.
  • If needed, the audit: code, dependencies and infrastructure read one by one.
  • A written audit: where the software is fragile, how many days it takes, whether to migrate or rebuild.
  • If you then give us the work, the audit isn't billed separately.
Request a technical audit

The first call and the preliminary check are always free. The full audit has a cost, which you only pay if you don't go ahead or give the work to someone else.

  1. 01AuditThe code, dependencies and infrastructure you already have. It's paid, and deducted from the work if you go ahead.
  2. 02PlanWhat gets migrated, in what order, with which risks. If a rebuild makes more sense, this document says so.
  3. 03ExecutionOn staging, with tests and a rollback ready, then into production in the agreed window.
  4. 04Verification and handoverPost-migration checks, documentation and access handed over to you.
It's for you if

you have software in production that you can't stop or throw away: PHP, WordPress and WooCommerce, or a dated JavaScript framework.

It's not for you if

you need a quick patch on a system nobody has looked at, or you run .NET, enterprise Java or a mainframe. We're not the right people for that, and we'll say so straight away.

Before starting, people ask us

“Wouldn't it be better to rebuild?”

Sometimes, yes. If the software can't be saved we say so in the audit, instead of billing you months of patches.

The proof

On Finanzamille the platform was rebuilt, off the no-code generator, but only after reading the code page by page. The historical archive, though, was moved, not thrown away.

The case study →

“What if it breaks during the migration?”

We work on staging with tests and a rollback ready: production is only touched in the agreed window.

The proof

For Finanzamille, the archive migration was rehearsed on real data before the final cutover, using the same procedure. The old platform couldn't be written to, not even by accident.

The case study →

“Why is the audit paid?”

Because on code we've never seen, a free estimate would be a gamble. And if you go ahead, it's deducted.

The proof

On Finanzamille, reading the code before writing a single line turned up a subscription that was just for show: it displayed a badge, but non-paying users saw everything.

The case study →

What people ask us

Yes, it's what we do. We always start with an audit of the code you have: on code we've never seen, a blind estimate isn't reliable.

Got software you can't just throw away?

Tell us what you have in production and what broke. We start with a technical audit: we tell you what's inside, how many days it takes and whether it's worth doing.

Request a technical auditMessage us on WhatsApp

“If opportunity doesn't knock, build a door.”

Milton Berle