A warehouse move affects the queries, scheduled data loads and reports your business relies on. Start with those dependencies. Discuss your current setup and reporting requirements with MatrixC before agreeing the migration scope.
Source systems and warehouse workloads
Queries, scheduled data loads and reports
Data access and location requirements
Validation and sign-off responsibilities
Cutover, handover and support scope
BigQuery is a data warehouse destination. Google's migration tools can support assessment, SQL translation and data transfer. Dataflow processes batch or streaming data and can support data pipelines. The appropriate combination depends on the workloads being moved.
Google's BigQuery migration documentation and Dataflow overview explain the product roles. Confirm the services included in your MatrixC quotation.
List the source systems, tables, queries and reports in scope. Identify their owners and any access or data-location requirements before choosing the migration approach.
Choose the reports and business totals that need comparison. Define the checks, acceptable differences and sign-off owner before switching users to the new platform.
Confirm who will monitor scheduled loads, investigate failed jobs and manage access. Include usage costs and support responsibilities in the discussion.
Describe your existing platform, data sources, approximate data volumes and refresh schedules. Include the SQL jobs and dashboards that business teams depend on.
Discuss an initial workload to test, the checks needed before release and an acceptable cutover window. Agree who can approve the move and what happens if validation fails.
Set out the operating instructions, access roles and support arrangements needed after the move. The quotation should define the agreed work, responsibilities, exclusions and timing.
Share your current platform, the reports you need to preserve and your intended timing. The team can discuss the next step and confirm the work that belongs in a quotation.
