Pricing
Pay once for a migration. Pay monthly for a sync.
Cloneto is priced per client. A one-time migration is a single charge that covers every rehearsal, delta run and the final cutover. A nightly or other ongoing sync is a monthly charge for as long as it runs. Each is a base fee plus a rate per million records, with a cap, and one line you can put on the client's statement of work.
Last updated · Prices in US dollars, excluding tax
How pricing works
-
01
Per client, not per server.
Each client can have its own deployment and its own license. Your templates are reused across all of them.
-
02
Sized by records, not by runs.
Rehearse and re-run as often as you need. The price comes from the source record count, agreed up front, not from the number of runs.
-
03
Building templates is free.
Build and test Job Templates against your own sample data at no charge. The charge starts with the first run against a client's environment, sandbox or production.
Prices per client
A base fee plus a rate per million source records, with a cap. A migration is charged once. A sync is charged each month it runs.
One-time migration
Charged once, per client
$500 + $1,000 per million records
Capped at $10,000
One client's migration from one source system into one destination. Covers six months from the first run against the client's environment, sandbox or production.
| Records | Price |
|---|---|
| 300,000 | $800 |
| 1 million | $1,500 |
| 5 million | $5,500 |
| 20 millionat the cap | $10,000 |
| Over 20 million | Talk to us |
- Unlimited rehearsals and delta runs
- Bulk load, delta runs and the final cutover
- Live progress dashboard for the client
- Exception report at every stage
Ongoing sync
Per month, per client
$200/month + $100 per million records kept in step
Capped at $1,500 a month
One charge covers every scheduled and webhook-triggered sync job for one client, for as long as they run.
| Records | Per month |
|---|---|
| 300,000 | $230 |
| 1 million | $300 |
| 5 million | $700 |
| 20 millionat the cap | $1,500 |
| Over 20 million | Talk to us |
- Any number of runs, on a cron schedule or a webhook
- Only changed records reprocessed
- Run history and per-record errors
- The same job you used for the migration
Partner volume
For partners with many clients
10+ clients a year
Volume rates set on a call
If you run migrations or syncs for 10 or more clients a year, your record volume is pooled across all of them and priced at volume rates, which we set with you on a call.
- From 10 clients a year
- Record volume pooled across clients
- Volume rates set with you on a call
- Everything in the standard plans
Per-million rates are prorated in steps of 100,000 records: the record count is rounded up to the next 100,000. For example, 4.32 million records are priced as 4.4 million, so the migration is $500 + $4,400 = $4,900.
Estimate a client
Every row in every source table or object in scope. Rounded up to the next 100,000.
Priced as {{ billed }} records
One-time migration
{{ migPrice }}
{{ migNote }}
Ongoing sync
{{ syncPrice }} /month
{{ syncNote }}
Talk to us
Over 20 million records, we price the migration and sync with you.
Book a technical walkthrough →Enter the number of source records to see the price.
Add-on: hosted in-region. If the client needs Cloneto hosted for them in a particular region, rather than in their own subscription or on their servers, hosting is an add-on to the standard prices above, quoted by region.
Ask for a quote →How the record count is set
- What a record isEvery row in every source table or object in scope, counted at the source. That includes activities, notes, attachments, and link or intersect tables.
- Agreed up frontYou or the client count the source records, for example at the first full rehearsal, and we agree the count before the migration starts. The only call Cloneto makes out of the client's environment is a license check that carries no data, so the count comes from you, not from Cloneto.
- Rounded up to the next 100,000The per-million rate is prorated in steps of 100,000 records, so 250,000 records are priced as 300,000.
- Trued up at cutoverIf the scope grows, you pay for the extra records at the same rate at cutover. The cap still applies.
- One migrationOne source system into one destination for one client. Two source systems are two migrations.
- Six months per migrationThe migration fee covers six months from the first run against the client's environment, sandbox or production: unlimited rehearsals, delta runs and the cutover. For longer projects, extensions are available by the month. A later re-migration for the same client is a new migration.
- Sync record countSet by the number of records the sync keeps in step, not the number that change each night, and checked again once a year.
Included with every client
- Deployment where the client needs itIn the client's Azure subscription or on their servers. Only a license check leaves.
- AI mapping and failure explanationsDrafts the field mapping, flags bad source data and explains failed runs.
- The run engineMapping store, no duplicates on re-run, resume after failure, streaming for large datasets.
- Your whole teamNo per-seat charge. Single sign-on when the client requires it.
- Support from ClonePartner engineersHelp with deployment, templates and failed runs. For regulated clients, over a screen share without access to client systems or data.
When you want engineers to run it
If a migration is beyond your team's time or experience, ClonePartner engineers can build the template and run it for you. Engineer-led delivery is quoted per project by ClonePartner.
Talk to an engineer →Pricing questions
What counts as a record?
Every row in every source table or object in scope, counted at the source, including activities, notes, attachments, and link or intersect tables. For a migration, each record is counted once, however many rehearsals and delta runs you do. For a sync, the price is set by the number of records the sync keeps in step, not the number that change each night.
How is the price worked out?
Each price is a base fee plus a rate per million records, with a cap. A migration is $500 plus $1,000 per million records, capped at $10,000. A sync is $200 a month plus $100 per million records, capped at $1,500 a month. The record count is rounded up to the next 100,000, so 250,000 records are priced as 300,000. Over 20 million records, talk to us.
What does the one-time migration fee cover?
One source system into one destination for one client, for six months from the first run against the client's environment, sandbox or production: unlimited rehearsals, delta runs and the final cutover. Two source systems are two migrations. For longer projects, extensions are available by the month. A later re-migration is a new migration.
How is the record count checked?
You or the client count the source records, for example at the first full rehearsal, and we agree the count before the migration starts. Cloneto does not meter records remotely: its only outbound call is a license check that carries no data. If the scope grows, you pay for the extra records at the same rate at cutover.
Who pays, us or our client?
Either. The partner can buy the license and include it in the client's statement of work, or the client can buy it directly.
How does Partner volume work?
From 10 clients a year, your record volume is pooled across clients and priced at volume rates, which we set with you on a call.
Do we pay for Azure on top?
When Cloneto runs in the client's Azure subscription, the client pays Microsoft for the resources it uses. The executor scales to zero between runs, so the standing cost is the control plane. Hosting in-region is an add-on to standard pricing, quoted by region.
What if the client needs a sync after the migration?
Keep the same job and put it on a schedule. The monthly sync charge starts when the first scheduled run goes live, and the record count is checked again once a year.
Price your next client migration.
Thirty minutes with an engineer. Bring a source, a target and a rough record count, and we'll draft the mapping on the call and work out the price with you.
Book a technical walkthrough