php2modern
PHASE B · MIGRATION METHODOLOGY

Rebuild, not translate.

We keep what matters — business logic, data integrity, integrations and user behavior — and prove it with parity tests, in a new repository. Migration starts only after a delivered Assessment Report, an accepted Proposal and a signed Contract.

01 — APPROACH

Two strategies. The Assessment chooses.

Incremental, behind a routing layer

A routing layer sends each request to the legacy application or the new one. Modules move one at a time, each verified by parity tests before the next. Legacy is retired only when acceptance criteria are met.

Fits: large or revenue-critical apps, many integrations
Phase 0
Phase 1
Phase 2
Phase 3
new systemlegacy serving
02 — PARITY TESTS

The old system is the specification.

Before and during the build, we derive tests from what the legacy application actually does. Each milestone is accepted against those tests before it is invoiced.

ROUTESSame inputs reach the same pages and endpoints, or are redirected on purpose.
OUTPUTSDocuments, exports and API responses match agreed expectations.
RULESPricing, approvals, calculations and permissions behave as before.
DATAMigration scripts rehearsed on a copy — never the live database.

Milestones and payment split are defined per contract.

03 — FOUR SEPARATE AUTHORIZATIONS

One signature never implies another. Payment never authorizes anything.

  1. 01 · repository_readRead your codeBefore any access. Signed by whoever can grant it.
  2. 02 · code_processingAnalyze itBefore any analysis. AI is a separate sub-scope.
  3. 03 · new_repository_creationCreate the new repoOwner, access, IP assignment, transfer terms.
  4. 04 · production_cutoverTouch productionSigned by your contract signer and technical owner.

Each record names the signer, assets, permitted activities, time window and how to revoke it. A revoked record stops the related work at once.

04 — CUTOVER

Two rollback plans, written before the switch.

T−7 DAYSLower DNS TTLsExact records listed in advance.
T−1Final rehearsalData migration on a fresh copy.
T · AGREED WINDOWCutoverOnly under signed production_cutover.
T+Verify & monitorVerification queries, agreed checks.
ROLLBACK A · DNS / TRAFFICReturn DNS or proxy routing to the legacy system. TTLs set in advance, records listed, executor named.
ROLLBACK B · DATAReconcile or restore data written after cutover. Point of no return, backup, sync-back method and verification queries defined.
05 — HANDOVER

You leave with the system. We leave with nothing.

  • Repository transferper contract
  • Documentation & runbooksoperations-ready
  • Our access revokedyou rotate credentials
  • Warranty windowlength set in contract
  • Working copies deleteddated deletion record

Every migration starts with an Assessment.

About the AssessmentDiscuss your modernization project