This Statement of Work defines the migration of Coastal Credit Union's core banking platform from on-premise infrastructure to a dedicated private cloud, executed across five governed milestones with full parallel-run validation, a rehearsed cutover, and a 30-day hypercare window before decommissioning legacy systems.
Provider will design, provision, and operate a dedicated private-cloud environment for the Client's core banking platform, migrate all production and reporting workloads, validate functional parity through a supervised parallel run, and execute a rehearsed weekend cutover. Work is delivered in five milestones, each gated on signed acceptance before the next begins, and each carrying a documented rollback path so the Client is never exposed to an unrecoverable state.
A weekly 30-minute steering checkpoint with the named sponsors, a written status report each Friday with risk/issue log and burn-down, and a milestone-exit review before any acceptance sign-off. <b>RAG status</b> escalates to the executive sponsors on any amber held two weeks running.
Provider supplies a migration lead, a solutions architect, and a DBA; the Client names a technical sponsor (decisions), a DBA (production access), and a compliance reviewer (regulatory sign-off). Acceptance decisions sit with the <b>Client technical sponsor</b>; scope changes require both sponsors.
The Client will provide read access to production schemas, a named technical sponsor, and a maintenance window for the cutover weekend. Provider's timeline assumes the existing data model is documented to the level supplied in discovery; material undocumented dependencies surfaced after Milestone 1 are handled via the change-control process on the execution sheet. Regulatory examiners are notified by the Client at least 30 days before go-live, and a frozen change window applies to the legacy platform for the duration of the parallel run.
Change control. Any change to the scope, deliverables, schedule, or fee in this SOW takes effect only through a written change order signed by both named sponsors. Verbal or informal requests do not alter this SOW, and Provider is not obligated to perform unscoped work without one.
Governing agreement. This SOW is incorporated into and governed by the Master Services Agreement referenced on the title sheet. Where this SOW and the MSA conflict, the MSA controls except as to scope, deliverables, fees, and schedule, which this SOW controls.
Acceptance. A deliverable is accepted when the Client signs its acceptance criteria or fails to respond within five business days of submission. Provider warrants each deliverable against material defects for 30 days after acceptance and will remediate at no charge within that window.
Confidentiality & data. All member data accessed during migration is Confidential Information under the MSA. Provider holds no copies beyond the active environments and certifies destruction of migration staging data within 30 days of go-live.
Term & termination. This SOW commences on the effective date and remains in force until the final deliverable is accepted and the hypercare window closes, unless terminated under the MSA. On termination for convenience, the Client pays for all accepted milestones plus work in progress to the date of notice.
Notices. Formal notices under this SOW are sent to the named sponsors at the addresses on the title sheet, in writing, by email with read receipt and confirmed by a copy sent by recognized courier. A change of notice contact is itself a notice.