Statement of Work, Data Platform Migration

Statement of work

A time and materials SOW for a data migration, written to sit under a master services agreement without contradicting it.

Make one like thisEditable, then download as a PDF

The whole document

Every page as it was built, in order. All the wording, figures and tables were written for this example, so the structure can be judged on real content.

Bayside Retail Group runs weekly reporting from a SQL Server warehouse built in 2016. Refreshes now take eleven hours and finish after the Monday trading meeting. This statement of work covers migrating that warehouse to a cloud platform, rebuilding the twelve reports the trading team depends on, and handing over the pipeline to Bayside staff.

This SOW is governed by the Master Services Agreement between the parties dated 4 March 2025. Where the two documents conflict, the Master Services Agreement prevails.

Review the existing warehouse, catalogue every table and job in use, and confirm which of the 340 objects are actually read. Produce a target model and a migration sequence agreed with the Bayside data lead.
Build ingestion for the eight source systems in scope: point of sale, ecommerce, inventory, loyalty, finance, rostering, supplier EDI and web analytics. Incremental loads, with a daily reconciliation against the source row counts.
Rebuild the twelve reports listed in Appendix A, matched to the current numbers within a tolerance of 0.5 percent, with a signed comparison for each one.
Runbook, on-call procedure and two half day sessions with the Bayside data team, plus four weeks of supported operation after cutover.

Fees are time and materials, invoiced monthly in arrears against a timesheet. The estimate above is not a cap; Fennel Analytics will notify Bayside in writing when spend reaches 80 percent of the estimate and no further work is done past the estimate without written approval. Travel is charged at cost and only when requested in writing.

Bayside has ten business days to accept or reject each deliverable in writing. A deliverable not rejected within that window is accepted.
A rejection must state which acceptance criterion is not met. Fennel Analytics corrects and resubmits within ten business days at no extra charge where the fault is ours.
:
:
:

What makes this document work

Acceptance has a clock

Ten business days to accept or reject in writing, and silence counts as acceptance. That one clause prevents most invoice disputes.

The estimate has a trigger

Work stops at the estimate unless approved, with notice at 80 percent, so nobody is surprised by the invoice.

Assumptions are listed

Access, availability and licences are written down, which is what turns a delay into a variation instead of a fight.

Questions people ask

What is the difference between an SOW and a proposal?

A proposal sells the work. An SOW defines it for delivery: deliverables, acceptance, rates and assumptions.

Should an SOW include rates or a fixed price?

Either, but say which. This example is time and materials with an estimate and a stop point.

Who signs an SOW?

Someone authorised on each side, usually under an existing master agreement that carries the legal terms.

What makes an SOW go wrong?

Vague deliverables and no acceptance process. Both are handled explicitly in this example.

Make yours in about a minute

The button opens the document generator with this document already described. Change the wording to your own business, pick a theme, and edit any section afterwards.

Make my statement of work

Other document examples

Tax invoice

An invoice with everything an accounts team needs to pay it without emailing you back.

Business proposal

A fixed price proposal from a studio to a clinic, written the way a buyer reads one: the number first, then what they get for it.

Project status report

A month four report on a construction fit out, including the bad news, which is what a status report is actually for.

New to the builder? Start withcreate a document with AI, thenlay it out exactly how you want it.