Import
Any spreadsheet in. Clean, matched records out
Statements, claimant lists, provider files and bulk updates arrive in every shape. Set up how a file should be read once. From then on, every file that arrives, whether by email, from a workflow or uploaded by hand, is checked, matched and loaded the same way
What you can do
Spreadsheets loaded the same way every time
Files are read against a saved profile, checked before anything is written and matched to the right records, with a report for every row
Map a file once, reuse it every time
Build a reusable import profile in four guided steps: Extract, Transform, Validate and Load. Pick the sheet, header row and data rows, map each column to a field with a live preview, and set the rules that catch bad data before anything is written.
Runs itself when files arrive
A spreadsheet attached to an email is picked up in Triage and imported automatically. Workflows can pass files straight to an import too, with values such as a case reference carried onto every row. No downloading, no re-uploading, no one waiting to press run.
Create, update or both
Add new records, update existing ones, or do both, matched on the fields you choose, with duplicate detection built in. Only fields that can receive data are offered, so nothing is written to the wrong place.
Every row accounted for
Each import has a report showing what happened to every row. Fix a failed row on screen and re-import just that row. Every imported row can also start a workflow, so one spreadsheet can update hundreds of cases end to end.
How it works
Three steps from spreadsheet to records
1
Map the file once
Pick the sheet, header row and data rows, then map each column to a field with a live preview.
2
Set the rules
Validation catches bad data before it’s written, and matching decides whether each row creates, updates or both.
3
Let it run
Files arriving by email or from a workflow are imported automatically, with a report on what happened to every row.
What makes it different
Import turns a one-off upload into a repeatable process. The profile is built once, every file after that is checked, matched and loaded the same way, and a failed row can be fixed and re-imported on its own.
Stronger together
Works With
Explore further
See Import on your kind of work
Bring a process you wish worked better. We will show you how it would be modelled, automated and reported on in Volume, with your objects and your language
