Time-Series SCADA Database Migration Readiness Checklist

Role: Principal Data Architect specializing in Industrial IoT and high-throughput energy telemetry systems.

Context

• Source SCADA Store: {{source_db_engine}}
• Target Time-Series Platform: {{target_timeseries_platform}}
• Ingestion Rate: {{ingestion_frequency_hz}}
• Retention Rule: {{retention_policy_period}}
• Regulatory Standard: {{utility_compliance_framework}}
• Active Sensor Tag Count: {{scada_tag_count}}

Task

Generate a structured, phased pre-migration readiness checklist that database administrators and industrial automation engineers must execute to validate data integrity, compression efficiency, tag indexing, and compliance constraints before migrating live utility SCADA telemetry.

Method

1. Inspect the incoming telemetry payload structure and define partitioning rules for {{scada_tag_count}} active tags.
2. Review downsampling, rollup tiers, and continuous aggregate queries against {{retention_policy_period}} requirements.
3. Validate chunk interval sizing and memory allocation for the {{target_timeseries_platform}} cluster under {{ingestion_frequency_hz}} load.
4. Design validation checkpoints comparing historical query outputs between {{source_db_engine}} and the new target.
5. Establish schema-level constraints to prevent unbounded cardinality spikes from smart grid sensor edge nodes.
6. Audit write-ahead logging, write buffers, and failover targets against {{utility_compliance_framework}} reliability controls.
7. Formulate a step-by-step verification gate covering automated reconciliation, backfilling, and live parallel-run validation.

Constraints

• Checkpoints MUST be organized by migration phases: Pre-Migration Prep, Live Mirroring, Validation, and Cutover.
• Every checklist item MUST specify the verification method (e.g., automated SQL check, load simulation, manual review).
• You MUST NOT recommend proprietary tools without standard open or platform-native equivalents.
• The checklist MUST contain a distinct section addressing non-negotiable {{utility_compliance_framework}} retention mandates.
• Format every actionable line item as a markdown checkbox - [ ].

Output format

Provide the review as a markdown document with the following four numbered sections:

1. Architecture & Capacity Verification (4-6 checklist items)
2. Telemetry Ingestion & Cardinality Checks (4-6 checklist items)
3. Data Integrity & Backfill Validation (4-6 checklist items)
4. Cutover & Compliance Sign-Off (3-5 checklist items) Each item must follow the pattern: - [ ] [Owner Role] Item description | Verification: <method>.

Self-review

• Confirm all 6 input variables are explicitly referenced and contextualized within the checklist.
• Verify that every checklist item is actionable, unambiguous, and formatted with - [ ].
• Check that section headings match the required 4-part output structure exactly.