DataShift NGCBN data residency
Services

Know it, move it, prove it.

Three capabilities that build on each other. Each produces something you can put in front of an examiner.

01 · Data inventory

A register of what you actually hold

Every system holding payment or personal data: what it holds, where it sits now, where it is going, its status and who owns it.

It deliberately covers systems we cannot move. Core databases, nightly backups and log stores hold the same payment data as the buckets, and the obligation covers them too. A register limited to what our tool happens to handle would misrepresent your position — which is the opposite of the point.

  • Every entry attributed to a named person and dated
  • Entries linked to the migration that evidences them, where one exists
  • A system claimed complete with nothing behind it is flagged, not hidden
REGISTER EXTRACT
Statement archive
Object storage
✓ Confirmed
Nightly backup vault
Backup
Declared only
Core banking database
Database
Not started
1 Count the source Before anything moves, so scope is fixed and dated 2 Transfer Resumes where it stopped; nothing is copied twice Read it back Every object checked at the destination, by size
02 · Verified migration

Object storage, moved and checked

Any S3-compatible source to any S3-compatible Nigerian provider, using credentials you generate from your own accounts.

  • Scope is fixed first. The source is counted before the transfer begins, so the record states exactly what it covered.
  • Every object is confirmed. Read back from the destination and size-matched, rather than assumed because an upload did not error.
  • Interruptions resume. A transfer that stops picks up where it left off; you do not pay egress twice.
  • Keys are destroyed once the transfer is confirmed.
03 · Attestation

The document you hand over

One pack covering the register, the migrations that evidence it, and the declarations behind everything else. It reports what is backed by a confirmed migration and what rests on a statement, as separate counts.

There is no overall score. Blending declarations with verified migrations into a single percentage would invent a verdict, and the first person to test it would be an examiner.

3
systems recorded
1
backed by evidence
2
declared only
1/3
movable by this platform

An honest position statement, including the part that is inconvenient for us.

Evidence

What a completion record says

It is issued only when every enumerated object has been confirmed. Otherwise it refuses, and tells you why.

Boundaries

What it doesn't do

A compliance platform that overstates its reach is worse than none, because somebody will rely on it.

  • Does not move databases, backups or log stores. Object storage only. Record them in the register and evidence them elsewhere.
  • Does not verify jurisdiction. We see a bucket name and an endpoint. Neither reveals where the hardware is, so location is your declaration.
  • Does not certify compliance. No document we produce says an organisation complies with the circular or the NDPA. That is a regulator's judgement.
  • Does not discover systems. The register is what you tell it. We cannot confirm it is complete.
  • Does not mask or inspect content. Objects move byte for byte and are confirmed by size.
  • Gives no compliance score. Mixing declarations with confirmed migrations into one number would manufacture a verdict.
Ask us anything about the above