Migration plans list tasks. Sign-off needs evidence. This checklist is organized by phase and written as questions a manager can ask without reading the code. If an answer is unclear, that phase is not finished.
1. Assessment
- Is there an inventory of databases, sizes, growth, and peak write volume?
- Is there a count of stored procedures, functions, triggers and Agent jobs, with unused ones marked?
- Which SQL Server features are in use that have no direct PostgreSQL equivalent: linked servers, CLR, Service Broker, SSIS, SSRS, cross-database queries?
- Which applications, reports and integrations connect, and who owns each one?
- What are the agreed recovery time and recovery point objectives on the new platform?
2. Conversion
- Is every data type mapping that changes behavior recorded with its reason?
- Is case sensitivity decided per column, not left to the default?
- Is each stored procedure classified as mechanical, redesign, or retire? See T-SQL to PL/pgSQL conversion.
- Are application queries tested against PostgreSQL, including ORM-generated ones?
- Do scheduled jobs have a new home and their own alerting?
3. Validation in QA
- Is data reconciliation repeatable across tables and test cycles?
- Has replication been interrupted on purpose and rebuilt without risk to the source?
- Has performance been measured under representative load, not a quiet test window?
- Which lag, error or mismatch threshold stops the release, and who owns that evidence?
4. Cutover
- Who has the authority to pause, and who decides between resume and rollback?
- Are the stop signals and thresholds written down before the window opens?
- Is the order for stopping writers and background jobs documented and rehearsed?
- Who tells the business what happened, and when?
5. Rollback
- Has rollback been rehearsed after PostgreSQL has accepted writes, not only before?
- What happens to each transaction accepted after cutover if the team has to return?
- How long did the rehearsal take from decision to validated service, and does that fit the agreed limit?
- Who verifies data before service resumes?
6. The first ninety days
- Does alerting watch what fails on PostgreSQL: vacuum health, replication lag, connection saturation?
- Has the operations team performed a point-in-time recovery on the new platform?
- Are backup, access, change control and escalation accepted by the receiving team in writing?
- Is there a date and a set of conditions for retiring the old platform?
How to use this
Put a name and a date next to every question. An item with no owner is not in progress. The phases map to the Production Migration Notes, which explain the reasoning behind each one. The tools guide covers what software can and cannot do for each phase.
Where this leads
Datrick runs SQL Server to PostgreSQL migrations and operates the database afterward, with named engineers and a written scope. The service page describes the delivery model: SQL Server to PostgreSQL migration. For a first read of risk and effort, see the migration risk assessment.
Related: SQL Server to PostgreSQL migration · migration risk assessment · Production Migration Notes · PostgreSQL DBA services
