Change a thousand records, and put them back
Upload a spreadsheet, map the columns once, and Aprimo Data Import validates every row, shows you exactly what will change, and writes it. Each run keeps the values that were there before, so an import that went the wrong way is one click from being undone.
For Aprimo administrators and marketing operations teams doing migrations, bulk corrections and metadata clean-ups.
The safety rail around a bulk write
Nothing is written until you have seen it
Validation catches missing required fields, absent ID columns and values outside a selection list. The preview then shows the exact change before a single record moves.
A run you can take back
Prior values are captured before an update, and reverting a run restores the records it touched.
Every row is accounted for
Each row comes back with its outcome and, where Aprimo refused it, the error Aprimo gave. Download the lot as a CSV.
Your Aprimo credentials stay out of it
Sign in with your Microsoft work account. The app reaches Aprimo through the platform's central auth layer, and each tenant's data is scoped on every request.
Six steps, in one sitting
Choose and upload
Pick the object and the operation, then drop in a CSV or XLSX of up to 50,000 rows.
Map the columns
Columns match to Aprimo fields by header, and you can save the mapping as a template to reuse next time.
Validate and preview
Every row is checked, then previewed as the change it will make. Unmapped columns are ignored rather than guessed at.
Execute and keep the receipt
Run it, watch the per-row results, download them as CSV, and revert the whole run later if you need to.
What it can change
Four Aprimo objects
Activities, Projects and DAM records can be created, updated or upserted; Programs can be updated. Field lists are read from your own Aprimo metadata.
Mapping templates
Save a column mapping per object type and reuse it, so a monthly load is a two-minute job the second time.
The spreadsheets you already have
CSV or XLSX, dragged and dropped, up to 50,000 rows per file.
Files alongside records
Bring the asset files with the metadata and attach them to the DAM records the import creates or updates, up to 20 MB per file.
Run history
Who ran what, when, against which tenant and object, with every row's outcome kept alongside it.
Stop or reverse
Cancel a run while it is going, or revert a finished one back to the values it replaced.
Numbers worth knowing
Bring us your worst spreadsheet
Show us the bulk change you have been putting off, and we will run it through validation and preview with you.
Get in touch