MIGRATION PLANNING

Move the application with a recovery plan.

A migration includes code, persistent data, DNS, verification, and a decision about when to switch traffic.

Scope the move before scheduling it

Application requirements and data size determine the migration plan. Do a staging rehearsal and agree on validation and rollback criteria before a production cutover.

  1. 01

    Discover

    • Inventory PHP, extensions, server rules, database, uploads, queues, and scheduled work.
    • Record domains, DNS authority, TLS requirements, and external dependencies.
    • Agree on the allowed interruption and the person who can approve cutover.
    GO / NO-GO

    The application and all persistent services have an owner.

  2. 02

    Rehearse

    • Build from the chosen revision on the compatible engine.
    • Restore a suitable data copy and test reads, writes, uploads, and background work.
    • Verify the restore procedure and document required credentials as references.
    GO / NO-GO

    A staging copy passes functional and recovery checks.

  3. 03

    Cut over

    • Plan the final synchronization or write freeze.
    • Confirm ownership, DNS changes, certificate readiness, and application health.
    • Keep the prior environment available and record the traffic-switch time.
    GO / NO-GO

    Data consistency, routing, and rollback conditions are agreed.

  4. 04

    Validate and retain

    • Exercise the agreed business workflows and review error observations.
    • Keep backups and the previous runtime for the agreed retention window.
    • Document the final release, domain target, recovery point, and unresolved follow-up.
    GO / NO-GO

    The application owner accepts the result.

Confirm runtime availability and a verified recovery procedure before scheduling a production move.

YOUR APPLICATION. YOUR WORKFLOW.

Bring your PHP application, choose the runtime it needs, and keep releases, domains, and operations together in your Orisite panel.