For partners
For firms that migrate for a living
Every client migration you rebuild from scratch is margin you give away. Cloneto lets your team build each migration once, run it for every client inside that client's own environment, and show the client exactly where it stands.
Last updated
01 · The problem
Where partner margin goes
- Rebuilding the same packages for every client.
- Mapping workshops that run for weeks.
- Migrations that stall when the consultant running them leaves.
- Status updates written by hand.
02 · How it works
How partners use Cloneto
- 01
Build a Job Template once for each source and target you see often.
- 02
Instantiate it per client by binding their connectors and arguments.
- 03
Deploy per client: in their Azure subscription, on their servers, or hosted in-region.
- 04
Share a live dashboard instead of status emails.
- 05
After cutover, keep the client in sync with the same job on a schedule.
ClonetoTrey ResearchPartner workspace · 5 clients/All clients/RunsAll clients
Runs
| Status | Client · job | Records | ||||
|---|---|---|---|---|---|---|
| Running | Contoso BankAccounts and contacts to Dataverse · Run 148 | 31,840of 179,584 | ||||
| Running | Woodgrove BankCore banking to Dataverse · Run 61 | 412,906of 655,310 | ||||
| Failed | Tailspin ToysSalesforce to Dynamics 365 · Delta 4 | 1,288resumable | ||||
| Needs review | Northwind TradersMigration to Dynamics 365 · Rehearsal 2 | 17,520sandbox | ||||
| Completed | Adventure WorksGP to Business Central · Delta 2 | 6,214 | ||||
| Completed | Adventure WorksGP to Business Central · Rehearsal 3 | 312,776 | ||||
| Scheduled | Contoso BankNightly core-to-CRM sync | — | ||||
| 7 runs · 5 clients, each in its own deployment · 4 Job Templates, 2 of them reused across clients | ||||||
03 · Your team
One interface for the whole team
Every job, run and error lives in one control plane, so anyone on your team can pick up a migration when a colleague moves on.
04 · ClonePartner
Engineers behind you
When a job needs hands-on engineering, ClonePartner engineers can take it. For regulated clients, they support over a screen share without access to client systems or data.
Trust and compliance →05 · Who uses it
Who uses it
- Microsoft Dynamics 365 partners
- Business Central and Dynamics GP partners
- NetSuite partners
- CRM and helpdesk consultancies
- Software vendors who migrate their own customers
Used by a global banking software vendor on the Microsoft stack to move bank data into Dynamics 365, in place of SSIS packages.
Read the case study →06 · FAQ
Partner questions
Can we run Cloneto for many clients at once?
Yes. Each client can have its own isolated deployment and its own jobs, built from your shared templates.
Can our clients watch progress?
Yes. Each migration can have a live dashboard for the client.
What if a migration is beyond our team?
ClonePartner engineers can take it on.
How is Cloneto priced for partners?
Per client, with published prices: a one-time migration is $500 plus $1,000 per million records, capped at $10,000, and an ongoing sync is $200 a month plus $100 per million records, capped at $1,500 a month. From 10 clients a year, Partner volume pools your record volume across clients, with volume rates set on a call. Full details are on the pricing page.
The last migration you build from scratch.
Bring a real migration.
Thirty minutes with an engineer. Bring a source, a target and a sample of the data, and we'll draft the mapping and run it against a sandbox on the call.
Book a technical walkthrough