Where Does Your Data Actually Live? Data Residency Questions UK SMEs Should Ask Before the Next Contract Is Signed

  • 2 weeks ago
  • 0

A contract says “cloud-hosted”. That tells you very little about where your business data is stored, where it is processed, who can access it or where it will be restored after an outage.

For a UK SME, these are not abstract compliance questions. They affect operational resilience, supplier risk, customer commitments and the cost of leaving a service. Before signing or renewing a hosting or SaaS agreement, get a clear picture of the full data journey, not just the location of the primary server.

This is where consultancy should come before procurement. As a Fractal IT Director, David’s role is to connect business requirements, systems and infrastructure into one coherent strategy. The service contract and any Managed IT Services should support that strategy, not define it by default.

Abstract map relief with data-centre buildings and restrained gold connection paths

“Where is our data?” is several questions

Business data may be held on an on-premise server, in a provider’s cloud environment, or across several SaaS platforms. A single process, such as taking an order or paying an invoice, could involve data moving between those systems.

Ask providers to distinguish between:

  • Storage: where live records, attachments and backups are held.
  • Processing: where the service handles or analyses information.
  • Access: where support teams, administrators and subcontractors may connect from.
  • Resilience: where replicated data or disaster-recovery copies are kept, and where a restore would take place.
  • Connected services: where integrations, analytics, identity systems and extensions send or hold data.

A UK business region does not automatically mean UK-only storage, processing, support access or recovery. The answer may depend on the provider, the service, the configuration and the contract. Ask for specifics in writing, including any exceptions and the relevant subcontractors.

The National Cyber Security Centre’s cloud-provider guidance recommends understanding the countries in which information is stored, processed and managed, as well as access rights and how location changes are communicated. Treat a supplier’s general statement about “secure UK hosting” as the start of due diligence, not its conclusion.

Questions to ask before signing

Whether you are buying a cloud platform or renewing an established SaaS subscription, ask the provider and implementation partner:

  1. Which locations apply to each type of data? Ask about production and test environments, backups, logs, metadata and support information, not only the main database.
  2. Who can access the information, and from where? Clarify the provider’s staff access, partner access and any emergency support arrangements.
  3. What happens during a regional outage? Confirm where failover or recovery takes place and whether that location meets your requirements.
  4. Can locations or subprocessors change? Ask how much notice you will receive and what options you have if a change is unacceptable.
  5. Which documents make these commitments binding? Review the data-processing terms, service-level agreement, subprocessor information, retention terms and exit provisions.
  6. How do we get our data back? Establish export formats, timescales, deletion arrangements and what happens to backup copies after termination.

Record the answers in a data-flow diagram or register. “The provider handles it” is not a useful record for management, auditors or your next supplier review.

Business Central: settle residency questions during implementation

For some SMEs, Dynamics 365 Business Central can serve as a cloud-hosted core finance and ERP system. A Dynamics 365 Jump Start should therefore be more than a quick deployment exercise: implementation is the right time to confirm environment location, integrations, access and recovery arrangements.

Ask the implementation team to document the environment’s localisation and applicable geography, and show you where to verify it after deployment. Confirm how the provider’s terms apply to your specific environment and which services or features may involve other locations. Business Central’s geography and data-residency information should be reviewed alongside its service overview, not inferred from the fact that Microsoft operates UK datacentres.

Then map every connection: banking feeds, payroll, payment platforms, document storage, reporting tools and extensions. A UK-configured ERP cannot determine where a third-party application stores its own copy of your data. Review each supplier and integration on its own terms.

Hybrid estates: data may still sit on-premise

Cloud migration does not mean every critical record has moved. Some firms still rely on on-premise servers, specialist applications or legacy platforms alongside cloud services. That can be a sensible architecture, but only if someone understands the dependencies and plans for them.

For organisations running IBM i Management or AS/400 workloads, establish where the system and its backups are hosted, who manages access, and how it connects to newer cloud services. The important question is not simply “Should we move it?” It is whether the current platform, the proposed hybrid architecture and the business recovery plan fit together.

Two secure server environments linked by a subtle gold line, representing recovery across locations

Disaster Recovery: where does the restore actually happen?

Backups are valuable only when they can be restored in a time and location that work for the business. Ask the supplier, or your internal IT lead, to explain:

  • Which systems and data are included, and what is excluded?
  • How often are backups taken, how long are they retained, and where are they stored?
  • Where would data be restored after a site or regional outage?
  • What are the agreed recovery time objective (RTO) and recovery point objective (RPO)?
  • When was a restore last tested, and what did the test cover?

Translate RTO and RPO into business language. “Four hours” is only meaningful if everyone agrees which service must be available within that period. “One hour of data loss” needs to be assessed against the consequences for orders, finance, clinical operations or customer records.

A plan that matched last year’s servers may not match this year’s SaaS and cloud estate. Revisit it after migrations, contract renewals and significant changes to integrations. Our Disaster Recovery consultancy can help assess whether recovery arrangements align with the systems the business now depends on.

Technology Expense Management can reveal the hidden estate

Data-location reviews often expose a second issue: the organisation may be paying for services no one has fully mapped. Old hosting agreements, duplicate SaaS subscriptions, unused licences and overlapping connectivity can persist after systems change.

Technology Expense Management brings hosting, cloud, SaaS and connectivity costs into one review. The aim is not just to cut invoices. It is to connect each cost to an owner, a business purpose, a contract and the data or service it supports. That can reveal forgotten systems as well as duplicated spend, and give finance and IT a stronger basis for renewal decisions.

Ordered matte-black technology modules with subtle gold details, suggesting a clear view of IT costs and assets

Compliance evidence is not the same as residency assurance

ISO 27001 and Cyber Essentials are useful consultancy domains, but neither should be treated as a shortcut to proving where data lives.

For ISO 27001, check the provider’s current certificate and its scope. Certification relates to a defined information-security management system; it does not, by itself, guarantee UK-only data residency or prove that your own configuration and suppliers are appropriate.

Cyber Essentials addresses baseline security controls, including firewalls, secure configuration, security updates, user access and malware protection. It is not a data-location certificate. Your organisation still needs a clear asset register covering cloud services, hosting providers, integrations and responsible owners. The NCSC’s Cyber Essentials overview is a useful starting point.

Good evidence joins these pieces up: a current asset and supplier register, documented data flows, relevant contracts, access controls and tested recovery arrangements. Guided consultancy can help make that evidence consistent rather than assembling it in a rush when a renewal or assessment is due.

Make the decision before renewal day

Before signing, agree what data-location requirements actually matter to your business. They may differ by system, customer commitment or regulatory obligation. Then compare providers against those requirements, document any exceptions and agree what happens if the service changes.

The strategic work comes first: understand the data, map dependencies, test recovery and evaluate the total cost. Cloud Solutions, Network Solutions, Voice and Connectivity and Helpdesk Support can then be selected as execution services that fit the plan.

For an overview of the wider Evestaff group, visit evestaff.co.uk. For IT strategy, begin with the more useful question: not just where your data is today, but whether you know where it goes next, and what it would take to get it back.

SEO tags: Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, data residency UK, hybrid cloud, UK SME data security, cloud contracts, SaaS due diligence, Business Central data residency

Join The Discussion