How it works

From source files to a reviewed import package.

Kauro checks, prepares and verifies your files. Your team chooses what is in scope, approves every change and runs the import.

The six stages of a project

Choose a stage to see what happens, what you get and what stops it.

Your teamA sealed set and its exact count
01 Upload and seal your files
Your team
Who acts, what it needs and what happens at each stage
Who acts
Your team uploads, chooses and seals. Kauro reads the files and shows what they contain; nothing is changed at this stage.
What it needs
An account: after the fit form, account creation and onboarding, including your agreement to the terms, come before anything is uploaded.
CSV or XLSX exports, one object per file or worksheet, each with a single header row.
Stay within the limits: up to 50 files in one set, up to 2 GB for each file and 5 GB for the whole set, up to 800 columns in a table, and up to 500,000 billable source units in one project at launch.
Your team's confirmation that it may process the data.
For an import into a destination Kauro qualifies, the destination's settings, which your team confirms before the check starts. Supported services shows which destinations are open.
What happens
Kauro reads each file's format from its content, not from its name.
Before anything is counted, you see what each file and worksheet holds: its first rows, hidden sheets, formulas and anything that could not be read.
Your team includes or leaves out every file and worksheet, and chooses how headers, formulas and hidden rows are read. A hidden sheet is included only when you say so.
Sealing fixes the files, the choices and the count together. A sealed set never changes.
Your team uploads its exported files, chooses what is in scope and seals the set. Everything after this is measured, priced and prepared on the sealed set.
What you get
The exact count of billable source units: each admitted object, such as a contact, a company or a deal, counted before any duplicates are unified.
The project's scope: the sealed set, the service you choose and, for an import, the destination you confirmed.
What stops it
A file in another format, an encrypted or legacy workbook, or a workbook with macros, external links or embedded objects.
If a worksheet is too large to upload, export it as CSV or split it. Kauro never cuts a file silently.
Data in a category the service excludes, such as credentials or secrets, full payment card data, health data and other sensitive personal data. The service terms list every excluded category.
A change after sealing means a new version of the set. It replaces the old one, and approvals and quotes of the old one never carry over.
KauroWhat is wrong, measured on all of it
02 The free data health check
Kauro
Who acts, what it needs and what happens at each stage
Who acts
Your team starts the check; Kauro runs it. Your team reads the result in the project; nothing is decided or changed at this stage.
What it needs
A sealed set and, for an import, the destination your team confirmed.
What happens
It counts duplicate candidates, invalid values and what would block the import in the destination, on all the data you sealed, not on a sample.
It proposes the changes a plan could make, and lists the decisions only your team can take.
A duplicate candidate is a signal to review, never a confirmed duplicate.
Kauro measures the whole sealed set and shows what it finds before anything changes. The check is free and creates no obligation to buy.
What you get
Exact counts for each kind of issue, the proposed changes, the open decisions and the blockers, shown in your project.
What was measured on the whole set is kept apart from examples and from what is only proposed.
What stops it
The check is bounded, so it is not always immediately available, and how long it takes depends on the size of your files and on current capacity.
If its budget runs out, what was measured is kept and the result says plainly that it is incomplete.
Files outside the supported services: the check says so and stops there.
Your teamA plan your team approved
03 Review and approve the plan
Your team
Who acts, what it needs and what happens at each stage
Who acts
A person your team allows to approve. Kauro proposes; software that helps to interpret the data cannot approve anything.
What it needs
The result of the check, with its proposals and open decisions.
Someone who knows the data and may take business decisions about it.
What happens
Kauro proposes how columns map, which groups of duplicate candidates may be unified, how records relate to each other and which values are normalised.
Your team keeps, changes or rejects each proposal. Whatever is not approved stays as it was.
The plan is validated against the sealed set and the destination before it can be approved.
Approving is a separate, explicit action. Pressing Enter never approves anything.
Your team reviews every proposal, keeps or rejects each one, answers the open choices and then approves the plan as a whole.
What you get
An approved plan. The approval names the exact plan, sealed set, destination and checks it applies to.
What stops it
A required choice left open, or a validation that finds a blocker.
A new version of the files after the approval: the plan is reviewed again, and approvals are never reused.
An approval withdrawn before the preparation starts.
Your teamA confirmed order at the quoted price
04 Quote and payment
Your team
Who acts, what it needs and what happens at each stage
Who acts
Kauro issues the quote. A person your team allows to buy confirms it and pays.
What it needs
An approved plan: there is no quote before the plan is approved.
The sealed count of billable source units.
What happens
The price is the band of your service that holds the count of billable source units. Prices are in USD, before tax.
The price counts the units in the files your team sealed, before duplicates are unified, not the rows delivered.
The quote shows the units, the band, at most one discount, any tax, the total, how long the price is valid and anything that blocks the purchase.
The price stays valid for 14 days.
The quote is Kauro's offer. The order is made when your team confirms it, on the current approved plan, while the price is valid.
A payment counts as received only when Kauro has matched it to the exact amount of the order. Returning to a page never confirms a payment.
Kauro prices the project from the sealed set and the approved plan. Your team checks the quote, confirms it and pays.
What you get
A confirmed order for the scope you approved, at the quoted price.
What stops it
The price has expired: a new quote is needed.
The scope changes: new files or a changed plan need a new approval and a new quote.
The tax that applies to you has not been reviewed: the quote is not issued until it is.
At launch a project holds up to 500,000 billable source units. If yours is larger, ask in writing.
See the prices and estimate yours
KauroA package that passed every check
05 Preparation and verification
Kauro
Who acts, what it needs and what happens at each stage
Who acts
Your team starts the preparation once the order is paid; Kauro runs it and checks it.
What it needs
A paid order, with its approval, sealed set and destination still current.
What happens
Only the approved changes run, on the sealed files.
Every file produced is read back and checked: the counts must reconcile, and every output row must trace to the source rows it came from.
The checks recompute the result, so totals that match with the wrong data still fail.
The project shows each stage of the work separately: waiting, running, checking and released. A sign of activity is never shown as a share of the work done.
Kauro applies the approved plan to the sealed set and checks the result before anything is released.
What you get
A released package that passed every check.
What stops it
A check fails: the package is not released.
The approval is withdrawn, the payment is reversed or the project is cancelled.
Your teamYour import, run by your team
06 Delivery and your import
Your team
Who acts, what it needs and what happens at each stage
Who acts
Your team. Kauro does not write to your CRM at any step.
What it needs
Your own authorised account in the destination, and your own import tools.
Whatever the destination needs before an import. Kauro does not deploy fields, validation rules, automations or external identifier settings.
What happens
Your team imports the files in the order the instructions give.
For an import in stages, your team imports one stage, returns its result and receives the next verified stage.
A download link works for a short time, and the package is kept for a limited period. Data handling lists each period.
Your team downloads the package and runs the import in its own account. The project stays prepared for import until your team reports the result.
What you get
The files to import, the rows held back as exceptions, the trace of every row, the documentation and a manifest that adds up.
A report of what was found, what your team decided and what changed.
Instructions for the service you bought: for an import Kauro qualifies, written for that destination and the settings you confirmed; for Clean your data, standard files with no steps for a particular CRM.
What stops it
A stage result that does not match what was prepared: the next stage is not released. A file marked as a success is not proof on its own.
The end of the keeping period: the package is removed and cannot be downloaded again.
See the sample delivery

Where your responsibility starts

Your team is responsible for confirming that it may process the data, for the decisions that only the business can make, and for the import into the target. Kauro does not write to your CRM at any step.

Check your data for free

Review supported services See the sample delivery

From source files to a reviewed import package.

The six stages of a project

Upload and seal your files

The free data health check

Review and approve the plan

Quote and payment

Preparation and verification

Delivery and your import

Where your responsibility starts