Mon–Fri 09:00–18:00 UK
Rows of labelled storage boxes and cable trays under cool and warm light
Illustrative generated image — not our premises

Data processing & related hosting · registered in Coventry

Your data, handled with the hosting written down.

M & T Data Centre takes the data your organisation already has — exports, spreadsheets, logs, feeds, databases — and turns it into something reliable: cleaned, processed on a schedule, stored somewhere sensible, backed up, and documented so you can see what happened to it.

We work behind the scenes for teams who do not want to become infrastructure specialists, but cannot afford for their data to be fragile.

Describe your data Run a planner

  1. In

    Intake

    Files and feeds received, checked and logged.

  2. Run

    Processing

    Repeatable jobs that clean, join and reshape.

  3. Keep

    Hosting

    Data and services placed on agreed infrastructure.

  4. Prove

    Restore

    Backups that are tested, not assumed.

About the name

What “data centre” means here

Our name
is not a building

M & T Data Centre Limited is the registered name of the company. We do not claim to own or operate a physical data-centre facility, and the registered office in Coventry is a legal address, not a server hall.

Hosting is arranged on infrastructure agreed with each client — typically established hosting or cloud providers selected for the job — and we document exactly where your data sits, who can reach it and how it is protected. Being clear about this is part of handling data responsibly: you should always know which organisation physically holds your information.

B01 / Services

Six working units

Each unit is a defined piece of work with clear inputs and outputs. Most clients use two or three together.

U1

Data intake and cleaning

Receiving files and exports in whatever state they arrive: inconsistent columns, mixed date formats, duplicates, stray characters. We define validation rules with you, apply them, and report what was rejected and why.

Out: clean dataset + rejection report
U2

Scheduled processing

Turning a manual monthly spreadsheet ritual into a repeatable job: the same inputs, the same transformations, the same outputs, every time, with a log of each run.

Out: run log + delivered output files
U3

Managed hosting arrangements

Databases, file stores and small data services placed on suitable hosting, configured, access-controlled and documented.

Out: environment record
U4

Backup and restore

Designing retention, setting up copies and, crucially, testing restores on a schedule.

Out: restore test notes
U5

Migration and transfer

Moving datasets between systems or providers with checksums, reconciliation counts and a rollback plan.

Out: reconciliation sheet
U6

Data handling documentation

Data-flow maps, retention schedules, access lists and runbooks written for the people who will actually use them. Useful for internal governance and for answering supplier questionnaires accurately.

Out: data-flow map, retention schedule, runbooks

Full service specifications

B02 / Journey

The six-stage data journey

Every engagement maps your data onto the same journey. It keeps conversations concrete: which stage is fragile, and what would fix it?

  1. Arrive

    Where data comes from, in what format, how often, and who sends it.

  2. Check

    Validation rules: required fields, types, ranges, duplicates, encoding.

  3. Shape

    Joins, lookups, calculations and reformatting into the target structure.

  4. Store

    Where the result lives, under what access controls and retention.

  5. Deliver

    Outputs to people and systems: files, tables, extracts, reports.

  6. Retire

    Archiving and deletion when the data has served its purpose.

Walk through each stage in detail

Specification

Inputs, outputs, decisions

WorkWhat you provideWhat you receiveDecisions that stay with you
CleaningSample files, a description of what “correct” looks like, known problem casesValidation rules in writing, cleaned output, a rejection report per runWhat to do with rejected records
ProcessingCurrent manual steps, input locations, required outputs, timingAutomated job, run log, alerting on failure during working hoursBusiness rules and sign-off of first outputs
HostingWorkload description, data sensitivity, budget range, any provider preferencesProvider options compared, configured environment, environment recordChoice of provider and data location
BackupRecovery expectations: how much data you could lose, how fast you need it backRetention pattern, configured copies, restore test notesAcceptable loss and recovery time
MigrationSource and target systems, cut-over constraintsMigration plan, reconciliation counts, checksums, rollback routeGo / no-go at cut-over
B05 / Planner

How big will it get?

Before choosing where data lives, estimate where it is heading. Enter today’s volume and a growth guess; see the primary data and the total with backup copies.

Two more planners: retention and transfer windows

Illustrative planner

Storage growth projector

Arithmetic projection from your own estimates. It ignores compression and de-duplication and is not a quote.

B04 / Resilience

Resilience is a set of habits

We do not sell uptime percentages we cannot personally guarantee. We build arrangements that fail gracefully and recover predictably.

1

More than one copy, in more than one place

Backups stored separately from the primary data, with at least one copy that ordinary credentials cannot alter or delete.

2

A restore is the only proof

Restores are tested on a schedule agreed with you, and the results written down — including the failures.

3

Least access, reviewed

People and services get the access they need, recorded in an access list that is reviewed at agreed intervals.

4

Every job leaves a trail

Processing runs log what went in, what came out and what was rejected, so problems are traceable.

5

Documentation someone else can follow

Runbooks written so a competent colleague could restore or rerun without us.

6

Honest hours

Support runs Monday to Friday, 09:00–18:00. Arrangements are designed around that, not around promises of constant watch.

Boundaries

What we will not claim

You should be able to rely on every sentence on this site. So, plainly:

  • We do not operate our own data-centre building
  • No 24/7 monitoring
  • No certifications we do not hold
  • No undisclosed subcontracted hosting
  • No invented uptime figures
  • No sale or reuse of client data
Engagements

Three ways to work together

Fixed project

A defined piece of work with a start, an end and a handover: cleaning a legacy dataset, migrating to a new environment, setting up backups.

  • Written scope and acceptance criteria
  • Handover documentation included
  • Optional follow-on support

Ongoing operation

Scheduled processing runs and hosted environments looked after month by month.

  • Run logs and periodic reports
  • Restore tests on schedule
  • Working-hours support

Review

An independent look at how your data currently moves and is protected.

  • Data-flow map
  • Risks ranked by impact
  • Practical next steps
B07 / Support

When something looks wrong

A run produced odd numbers. A file did not arrive. Someone needs access removed today. Support requests reach the same people who built your arrangement.

We acknowledge support requests on working days and work through them in order of impact. For clients with ongoing operation, the agreed runbook sets out what happens when a scheduled job fails and who is told. We are open about hours: outside Monday to Friday 09:00–18:00, nobody is watching, and arrangements are designed with that in mind.

How support works

B09 / Contact

Bring the awkward dataset.

Tell us what arrives, how often, where it needs to end up and who needs to read it. A plain description is enough for a first conversation; samples can wait until we have agreed how they will be handled.

Open the enquiry form Support for existing work

Replies on working days, Monday to Friday, 09:00–18:00 UK time. We do not offer round-the-clock monitoring.

Registered office

31 Mellowdew Road, Coventry, England, CV2 5GH

Map placeholder. Registered office address from Companies House. It does not indicate a data facility or visitor premises, so no pin is shown.

Look up the address on OpenStreetMap