Your team uploads a CSV, an Excel file or a PDF. AI maps it onto your database, even when the headers are messy, every row is checked before it is saved, and nothing that fails is silently lost.

The problem
Most business systems still take data the slow way. A supplier sends a price list, a customer sends an order sheet, a branch sends a stock count, and someone re-types it, or pastes it into a template and hopes the columns line up. The headers never match, a price says "POA", a row has no name, and the mistakes surface weeks later in a report nobody trusts.
We built this import for Kikstart itself, where the assistant maps supplier price lists into a product catalogue. This project builds the same approach into your app: your files, your tables, your rules for bad data. The team behind it has spent more than 25 years building business software for accounting, manufacturing, distribution and retail, where an import that loses rows is not an option.
How it works
A CSV, an Excel file or a PDF goes in through a page in your app. The file stays on your own storage.
A model matches the file's headers to your fields, so "Item Description" lands in product name and "Retail (USD)" in price, with a confidence on every match.
The mapping is tested against every row before anyone approves it. Missing names, invalid prices and duplicate keys are caught here, not in your database.
Valid rows are written through one safe write path. Each failed row is recorded with its reason, ready to fix and re-import.
Packages
Prices in US dollars, fixed before we start. Nothing is billed by the hour.
Starter
$400
5-day delivery · 1 revision
One CSV or Excel format mapped to your database, with a downloadable report of failed rows and why they failed.
Standard
$900
10-day delivery · 2 revisions
Everything in Starter, plus one document type such as a PDF, read by AI and checked the same way.
Advanced
$1,800
15-day delivery · 3 revisions
Several sources, a failed-rows table, and an admin screen where your team reviews, fixes and re-runs the rows that failed.
Add-ons
| Fast deliveryStarter in 3 days, Standard in 6, Advanced in 10. | +$100 / +$200 / +$400 |
| Additional revisionOne more round of changes within the agreed scope. | +$75 |
| Extra document or file typeAnother source format, read and checked the same way. Adds 3 days. | +$300 |
Included
Your code, in your repository
The import lands in your codebase as a module you own, not a hosted service you rent.
A failed-rows report
Every rejected row with its reason, in your file's own columns, so it can be fixed and re-imported as it is.
Low running costs
Mapping and extraction run on cost-efficient models, and a file that matches its template needs no AI call at all.
A walkthrough and handover
Setup instructions, and a walkthrough of how the import works and how to extend it.
See it


From you
Sample files
Two or three real files per source, with sensitive data removed.
Your target fields
The tables and fields the data should land in, and access to your repository if we are building into an existing app.
Your rules for bad data
For example, skip rows with no price, flag duplicate codes, or default the currency when a file leaves it out.
The steps
We read your samples and your database, and confirm the mapping and the rules before building.
Upload, AI mapping, validation, the write path and the failed-rows report, in your codebase.
We run your own files through it and tune the mapping until the results are right.
Source code, setup instructions and a walkthrough, then your revision rounds.
Questions
Tell us what you need and we will confirm the package, the price and the delivery date.