WellViewData migrationSnowflake
1. Agree on what must match
Before migrating records, define the well and job scope, target fields, expected report outputs and reconciliation rules. Agree whether inactive, archived and historical records are included.
2. Validate parent-child relationships
Well data is relational. A well may contain multiple jobs, daily reports, rigs, cost records and operational logs. The migration should preserve keys, foreign-key relationships and the meaning of each child record.
3. Review date and time logic
Reporting date, entry date and operational start/end timestamps are not interchangeable. Test time-zone handling, operating-day boundaries and asset-specific daily report conventions.
4. Reconcile at multiple levels
- Source and target counts for wells, jobs and daily reports.
- Unique identifiers and duplicate records.
- Totals by well, job, rig and operating date.
- Cost, duration and performance calculations used by existing reports.
- Exceptions, null values and unexpected changes in classifications.
5. Validate real business reports
Matching row counts alone does not prove a successful migration. Compare known operational reports, dashboards and selected high-risk wells against the original system.
6. Document assumptions and exceptions
Keep a mapping register, exception log, test evidence and sign-off criteria. This creates traceability for future support and subsequent system changes.