Coordinate file transfer, database preparation, configuration checks, backups, URL validation and a controlled go-live decision.
Migration is one controlled state transition, not a sequence of unrelated uploads. Nexus must preserve a recoverable before-state and keep go-live authority explicit.
The screen keeps the objective visible while the project, systems, AI roles, progress, decisions and verification move through one operational record.
Prepare this website on the new server, preserve the current live site, verify the copy, and do not switch the public launch until the migration package is ready for approval.
Project objectiveI understand the requested outcome. I am fixing the scope, constraints, authority and evidence required before work begins.
Scope · constraints · authority · success testConfirmed source read authority and destination write authority. DNS, mail routing and final go-live remain separate controlled actions.
Project permissions · capability scope · blocked actionsOpened the source SFTP and database connections, then verified the destination host, document root, database and staging URL before copying anything.
Source SFTP + Source database + Destination hostingCreated a complete source backup with file hashes, database export, configuration record and current public checks so the original site can be restored.
Source SFTP + Source databaseThe live site, target server, database, environment settings, public routes and launch boundary were loaded.
Project rules · history · accepted decisionsThe migration worker is inventorying files, database tables, absolute paths, scheduled jobs, mail settings and environment-specific configuration before packaging the move.
Files · pages · records · linked business data12,480 files, 64 database tables and required configuration differences were mapped without changing the current live site.
Authorised working environmentThree environment-specific exceptions need review: mail transport, scheduled jobs and one absolute media path.
Work graph · normal cases · exceptionsA deployment package was created, transferred to the target, database content was restored and server-specific settings were applied.
Authorised change setThe new environment was checked against file manifests, database counts, key routes, forms and content expectations before launch.
Result against objective and project rulesThe mission remains inside the approved scope and authority. Sensitive actions outside that boundary remain locked.
Permission and scope boundaryResolve the three environment exceptions and approve the public switch. The current live site remains untouched.
Human attention queueThe new server contains a verified working copy. Go-live is a single controlled decision with rollback material prepared.
Verified mission stateMission scope, evidence, decisions, changes and verification have been attached to the project for the next command.
Project history · evidence · decisionsThe work stays attached to one outcome even when several systems and specialist AI roles contribute.
The owner approves the final switch and resolves environment-specific decisions such as DNS, credentials and unexpected application behaviour.
The new server contains a verified working copy. Go-live is a single controlled decision with rollback material prepared.
The mission closes with source-linked evidence, a clear authority record and verification against the original objective.
Source and target manifests match after environment exclusions.
Database row counts and required tables agree.
Key public journeys pass on the target host.
The current live environment remains available until go-live.
The move is treated as one verifiable mission with a before-state, destination state and controlled release point.
Staging refreshes, domain changes, multi-site consolidation, server moves and disaster-recovery rehearsals can use the same pattern.
Every case uses its own project, systems, messages, decisions, metrics and result while preserving the same mission language.
Inspect a plugin package, deploy it to the authorised test site, activate it, run the agreed checks and keep production rollout under a separate approval.
OPEN MISSION WORKFLOWFind the former name across websites, text files, navigation and project material, apply safe replacements and isolate context-sensitive uses.
OPEN MISSION WORKFLOWReceive supplier or administrative documents, extract the relevant facts, compare them with existing records and ask only where the document is unclear.
OPEN MISSION WORKFLOW
Describe the project, outcome and decisions you want to retain. Nexus organises the operational work around them.
