Import & migration

See what it will do
before it does it.

Every governance programme starts with a spreadsheet, and usually several. The risk register is in Excel, the control matrix came from the last auditor, and the vendor list belongs to procurement. Getting them in should not be a consulting engagement, and it should never be a write you cannot inspect afterwards.

Two steps, on purpose

Preview, then confirm. Never one irreversible button.

Upload a CSV or a spreadsheet and the engine parses it against the object you are importing into, then shows you what each row would become: what is valid, what is missing, and what will be rejected. Nothing is written yet.

Only when you confirm does it write, and every row's outcome is recorded as a job you can reopen later. An import is not a black box that either worked or did not.

How an import runs
ParseCSV or spreadsheet, against the object
Previewrow by row, nothing written
Confirman explicit second action
Logper-row outcome, kept as a job
Made for the messy reality

Real files are not clean, and pretending otherwise is how data gets lost.

Validated per field

Each value is checked against the field it is landing in, so a bad date or an unknown option is caught in preview and not halfway through the write.

Relationships come across

A row can point at a record in another object by its readable identifier, so hierarchies and links survive the import rather than needing a second pass.

An auditable job

The import itself is a record: who ran it, against which file, at what time, with what result. It sits in the same sealed trail as everything else.

Migration, not just import

Coming off a legacy GRC platform is the normal case, not the exception.

Bring your history
Closed findings, retired policies and past assessments come in as records, so the trail does not start on go-live day.
Bring your structure
Your entity ladder, your control framework and your existing mappings come across as configuration rather than being rebuilt by hand.
Bring your identifiers
Records keep a readable identifier your organisation already recognises, so a reference in an old audit report still finds the right thing.
Then stop importing
Once a source is connected through an integration, the spreadsheet round trip stops being part of the process.
An import you cannot inspect
is a data loss event waiting for a date.
Design partner programme

Bring us the question your regulator is going to ask.

A small cohort across banking, fintech, insurance, healthcare, technology, private equity and the public sector. Early access, real influence, pricing that holds.

We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.