Digitising Data Transfer - DMI27 update

Digitising Data Transfer - DMI27 update

ID

RM284

Version

1.0.1

Type

Roadmap Item

Contracting Vehicle(s)

Title

Digitising Data Transfer - DMI27 update

Description

Update to the Data Migration Standard to support Internet based transfers for Practice migrations

Date Added

Jul 23, 2025

Standards and Capabilities

Data Migration, Baseline Assurance Standard

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

Uplift

Status

Closed

Publication Date

Sep 2, 2025

Effective Date

Sep 16, 2025

Incentives / Funding

No

Incentive / Funding Dates

N/A

Background

Following Supplier feedback, updates have been made to the Data Migration Standard to clarify the requirement supporting Internet based transfers for Practice migrations.

Outline Plan

Supplier Solutions must be fully compliant with the change by the Effective Date.

Summary of Change

Data Migration: BAS Requirement updated

Applicable Contracting Vehicle(s)

ID

Requirement

Applies to

Level

Category A

Category B

Category C

All

DMI27

Perform a migration of data from a sSource Solution Supplier (SSS) to a tTarget Solution Supplier (TSS) over the internet., conforming to the Cross Functional Requirements outlined within the DMS Data Transfer - Cross Functional Requirements Document.

  • Internet-based transfers must conform to the Cross Function Requirements outlined within the DMS Data Transfer - Cross Functional Requirements Document

  • If, under the circumstance that a bandwidth of >= 70 Mbps and a latency of <200ms cannot be achieved, then a fall back to physical media transfer can be used

  • If, under the circumstance that physical media is deemed necessary, and the target Supplier is primarily cloud-based, then a Solution supported by the target Supplier’s cloud provider must be used, for example AWS Snow Cone or Azure Data Box

  • If, under the circumstance that both Suppliers are primarily cloud-based, then an internet-based transfer must be used. This is due to the potential number of additional transfers steps when using physical media between two alternative cloud providers

Suppliers are to agree their own process and solution for transferring extracts, so long as the outcome is in line with the requirements set out within the DMS Data Transfer Cross Functional Requirements Document and the overall Data Migration Standard. Where agreement cannot be found, the fall back process described here is to be used.

Target and Source

MUST

Self-certification with Supporting Evidence

Self-certification description to include:

  • If physical media is known as being required to support data migration, then justification will be provided.

  • For internet-based transfers, confirm Confirmation that all the Requirements listed within the ‘DMS’ Data Transfer - Cross Functional Requirements Document are met, along with any supporting evidence. 

If the Source Solution Supplier uses multiple Data Transfer Mechanisms to support multiple Target Solution Suppliers, self-certification description to include:

  • Confirmation that multiple Data Transfer Mechanisms are provided in order to meet the needs of multiple Target Solution Suppliers.

Self-certification

Self-certification description to include:

  • If physical media is known as being required to support data migration, then justification will be provided.

  • For internet-based transfers, explicitly confirm Confirmation that all the Requirements listed within the ‘DMS’ Data Transfer - Cross Functional Requirements Document are met.

If the Source Solution Supplier uses multiple Data Transfer Mechanisms to support multiple Target Solution Suppliers, self-certification description to include:

  • Confirmation that multiple Data Transfer Mechanisms are provided in order to meet the needs of multiple Target Solution Suppliers.

 

Self-certification

Self-certification description to include:

  • If physical media is known as being required to support data migration, then the justification will be provided.

  • For internet-based transfers, explicitly confirm Confirmation that all the Requirements listed within the ‘DMS’ Data Transfer - Cross Functional Requirements Document are met.

If the Source Solution Supplier uses multiple Data Transfer Mechanisms to support multiple Target Solution Suppliers, self-certification description to include:

  • Confirmation that multiple Data Transfer Mechanisms are provided in order to meet the needs of multiple Target Solution Suppliers

Full Specification

Data Migration v 2.1.2

Assurance Approach

Suppliers are expected to evidence their compliance with Requirement DMI27.