The data you already hold, moved home.
Most of the data a regulator cares about is already in your databases. Load it from a CSV, in the console for smaller files or with a command-line tool for large ones, and get the same rows back with tokens in place of values.
New customers can be protected from day one. The millions of BVNs and account numbers already sitting in your main database, its replicas and its exports are the real exposure.
Check the file first
Map columns to data types, and run a check that stores nothing and reports problems by row and column.
Load it in batches
Values go into the vault through the normal API, so access rules apply and every value is in the audit log.
Swap in the tokens
Put the tokens back in your database, check your systems still work, then delete the original file.
Check, then load
rv import -url https://onshore.bank.internal -vault v_live_ng01 \
-sa sa_migration -key-id key_01 -key-file migration.seed \
-file customers.csv -map bvn=bvn,phone=phone -ref customer_id -check
# Then run again without -check. You get:
# customers.csv.tokens.csv customers.csv.errors.csvTwo ways in
The console reads the file in your browser and sends it in batches. The rv import tool suits large files, and carries on after being stopped.
A dry run first
Run with -check and nothing is stored. You get the problems, never the values.
Tokens and errors files
A tokens file to load back, and an errors file that names rows and columns only. Both readable only by you.
Safe to run again
Fields that give the same token each time can be loaded twice without storing the value twice. The console warns about fields that don't.
Same rules as live traffic
Imports go through access rules and the audit log like any other call. There is no back door.
Copy setup between installs
Export fields, data types, access rules and connections from test to live. Rules arrive as drafts, connections as watch only, and nothing is deleted.
Early access: tested with synthetic files on one machine, not yet at the size of a bank's full customer base.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.