Why we don't rewrite a MODX site from scratch entirely

A large legacy site almost never consists solely of pages and templates.

Over the years, it accumulates:

  • URLs and SEO;
  • data;
  • users;
  • orders;
  • integrations;
  • business rules;
  • exceptions and manual processes that no one really remembers anymore.

Attempting to rewrite everything at once means this entire system must be perfectly replicated by switchover day.

It looks good on paper.

In practice, it is one big moment of truth where sales, indexing, integrations, and the routine work of employees can all break simultaneously.

We consider such a risk unnecessary.

Instead, the legacy MODX site is gradually transformed from a monolith into a replaceable part of the system: first, the environment is frozen; then, an API is isolated; after that, the new frontend and individual sections begin to live outside the old runtime.

Each stage delivers a working result. Each stage can be tested. Each stage can be rolled back.

Our goal is not to rewrite the site gracefully. Our goal is to transition the business to a new architecture without a leap into the unknown.