This is a starter set of operating documentation for audit preparation, migration, and support. Client-specific playbooks are prepared after the audit phase.
Migration checklist
Before the audit, prepare a list of servers, business systems, users, integrations, databases, critical working hours, and responsible contacts.
Production service inventory
Number of RDS/VPN users
Preferred migration window
Responsible contacts
VPN access
Server access should go through a protected perimeter. Each administrator needs named credentials and the minimum required privilege set.
Named access accounts
Separate admin roles
Access revocation on team changes
Critical change log
Backup policy
The base retention window is 7 days. For critical systems, copy frequency and restore testing should be agreed explicitly.
7-day retention
Restore validation
Separate rollback plan
Backup success control
Support escalation
To speed up response, each incident request should state the affected service, business impact, start time, and the responsible contact.
Incident severity
Affected service or server
Symptoms and start time
Clarification contact
Quick guides
Short guides before kickoff
What to include in an audit request
Describe the systems involved, how many people use them daily, any deadlines you are working against, whether 1C or M.E.Doc access is required, and which types of downtime are unacceptable.
How a migration window is planned
First we confirm backups and rollback coverage, then validate test access, and only then schedule the production cutover during the lowest-risk business period.
What to verify after migration
Check user logins, database access, print/export flows, integrations, backup status, and baseline performance during working hours.