Faith Forge LabsWebsite Maintenance
4 MIN READ

Questions to ask before a major website change

Find out what could be interrupted, what a restore would undo, and who makes the decision if the change goes wrong.

They aren’t a reason to delay every small edit. Use the questions relevant to the component, data and responsibility being changed.

Which system is authoritative during the work?

When a website is copied to a new host or restored privately, two versions may exist. Decide which one staff should use and where new records belong. A rehearsal can be useful without becoming a second operating system for the business.

For a move, identify what happens to submissions or edits made after the first transfer. A final synchronization, controlled pause or another supported method may be appropriate. The answer depends on the platform, but leaving it unspecified invites missing or conflicting information.

What would a restore undo?

The chosen copy represents an earlier state. Ask which records, files and settings changed afterward and whether those changes can be preserved or reconciled. Don’t assume that “restore yesterday” is a harmless way to reverse a single unwanted edit.

Distinguish restoring files from restoring data and configuration. The person authorizing recovery needs enough information to understand the consequences, including what remains uncertain. Preserve the current state where appropriate before taking a destructive recovery step.

What can the test copy do outside itself?

An application copied from production can retain configuration for email, payments, webhooks, storage or scheduled tasks. A test action may therefore have consequences beyond the preview page unless those boundaries are controlled.

Identify the outgoing connections and decide how each will be handled in the rehearsal. Some can use a test service; some may be disabled; some need a separately authorized check. Record the resulting limitation so a simulated result isn’t described as proof of a live integration.

Which services share an account without sharing a purpose?

A hosting account may contain website files and also support email or DNS. A domain registrar may provide additional services, while a separate vendor runs the application. An invoice alone doesn’t describe that topology accurately enough for a migration.

Before cancellation or a nameserver change, inventory the records and services involved. Provider documentation should guide the actual operation. DNS caching can affect when changed records are used; Cloudflare's TTL reference explains the mechanism, but its specific settings shouldn’t be assumed for another provider.

Who can approve an interruption or additional cost?

The technical contact may understand the change without authority to pause a business process or purchase a new service. Identify the person who can make those decisions, and establish what happens if they are unavailable during the planned work.

The scope should also explain which actions can proceed within the original agreement and which require another decision. That’s more useful than discovering halfway through a migration that a necessary provider feature has no approved owner or budget.

What would count as a failed release?

Define the checks that matter and the threshold for using the recovery plan. A missing critical journey deserves a different response from a minor visual discrepancy. The release owner should know who can accept a limitation and who can decide to reverse the change.

Recovery itself may need coordination. If records have arrived since the switch, moving back to the old system can create another reconciliation problem. The plan should consider that consequence rather than treating rollback as an instant universal undo.

What must the next maintainer know?

Record decisions that would otherwise look arbitrary: why an old service remains active temporarily, why a test integration is disabled, why a component has an exception or why a particular record was retained. Include the condition for reviewing or removing the exception.

A short explanation can prevent a future cleanup from undoing a necessary safeguard. Keep secrets elsewhere, but leave the reason and responsible owner visible in the project record.

Use the project brief to capture the applicable answers and the handover checklist to verify they survive completion.