For implementation partners

Keep the implementation relationship. Hand us the migration.

We run the migration inside your engagement, at a price set by the record count, with a named person on it, and we sell your client nothing else. You keep discovery, configuration, process design, adoption and the client. Bring it in when both of the client's CRMs are ones we publish.

Book a partner call Browse supported migrations

For Salesforce consultancies, HubSpot Solutions Partners, and the RevOps and CRM implementation firms that serve small and mid-sized businesses. Every published migration runs between two of Attio, Close, HubSpot, Pipedrive, Salesforce and Zoho, in either direction. There are 30 of them, each with its own page. If one of the client's CRMs is not among them, tell us what it is. That goes into what gets built next.

Your client stays your client

We sell the migration and nothing else.

The client relationship is yours. Migratez sells the migration and nothing beyond it: no implementation, no configuration and no process work, and we will not offer any of that to a client you brought us.

How we work together

Refer it, or run it at your margin.

Referral

For a migration you would rather not carry, or one outside your scope. You introduce the client and step back. They create the account, connect their own CRMs and get the plan and the price, 15% off because you sent them, without a single hour of yours in it. What you get is a client who arrives in the new CRM with their history intact, a named person to blame if not, and no migration on your books.

Co-delivery

For a migration that is part of your project. You hold the account, run the free assessment on the client's source, take the plan to the client and schedule the run around your cutover. We run the migration and report to you, and you stay the client's contact throughout. What you get is a scoped, priced, reversible step inside your engagement, billed to you and carried at your margin.

Who does what

You own the implementation. We own the migration.

You

Discovery

What the client has, what they need, and what the new CRM has to do for them.

CRM configuration

Objects, pipelines, users, permissions and automations in the destination.

Process design

How the client's team will work in the new CRM once the data is there.

Adoption

Training, rollout and the first weeks of use.

The client relationship

The contract, the conversations and the decisions. The client is yours.

Migratez

Source assessment

Every object's record count and every custom field's fill rate, from one read-only connection, with the price.

The plan

What travels and what each value becomes, what gets created in the destination and what the destination cannot hold, before anything is written.

The migration

The records, custom fields, history and relationships, run by a person and followed in the product.

Verification support

Answers while you check the destination, and one action that brings across what changed in the source since the main load.

Undo

One action takes the records we wrote back out again, in reverse, if the result is not right.

The workflow

Free assessment first, and you face the client throughout.

The co-delivery path, step by step, with the owner of each one. In a referral, the client takes the steps marked You and deals with us directly.

No.

Step

Who does it

01
Assessment
Connect the client's source with read-only access, or send its admin a connection link to do it. The assessment reports every object's record count and every custom field's fill rate, and shows the price. Nothing is written to either CRM. You stay client-facing. Nothing at this step needs us.
You
02
Scoping
Connect the destination and review the plan: what travels, what each value becomes, what gets created and what the destination cannot hold. We answer what the plan raises. You stay client-facing. You take the plan to the client, and we join a client call only if you ask.
You, with us
03
Migration
We run the migration and stay reachable while it runs. You and the client can follow the progress in the product. We write to you first if the run needs a decision. You decide what reaches the client.
Us
04
Verification
Check the destination against the plan. One action brings across what changed in the source since the main load, so both CRMs can stay live while you check. You stay client-facing. If the result is not right, we undo it, put it right and run again.
You, with us
05
Handoff
Cut the client over and carry on with configuration, process and adoption. Our part is done. You stay client-facing.
You

If something pauses, fails or is undone

A pause loses nothing. One action undoes it all.

Paused, no data lost

A stop, an error or an API limit pauses the run at its last checkpoint. It resumes where it left off and nothing is written twice. A pause that clears on its own needs nobody. One that needs a decision does, and you hear from us by email before anything else happens.

If it cannot complete

We tell you what stopped it and why, and agree with you whether to put it right and run again or to undo.

If it is undone

One action removes the records we wrote, in reverse. Fields created for the migration remain, empty, and shared catalogue data remains. We say so before an undo runs and again when it has finished.

Who hears it

In co-delivery, you, and you decide what reaches the client and when. In a referral, the client, and you as well if they have asked us to copy you.

How soon

Within about two business days, to you or to the client, whoever wrote. That is the one timing this page promises. How long an assessment or a migration takes depends on the record volume and on the two CRMs' API limits, so we do not put a number on either.

Client data and access

How the data is handled, where it runs and what is kept afterwards is on the security page, and this page does not restate it.

Read-only on the source. Never a password.

Who creates the account

Whoever will hold the migration. A migration lives in the account that created it, and an account is one email address with no shared seat, so settle this before the assessment: you in co-delivery, the client in a referral.

Who authorizes the connections

Someone with admin rights in the client's CRM, at that CRM's own sign-in screen, over OAuth. If that is not you, send them a connection link from the Connect screen: they authorize their own CRM without a Migratez account and without sharing a password, and they see nothing of the migration. Migratez never holds a password. The source is granted read-only access and is never written to. The destination is granted read and write access, because the fields the data needs are created there before any record is. A connection stays with the CRM account that first authorized it, and either grant can be withdrawn from the CRM at any time.

What you see

The account holder sees the assessment, the plan, the run's progress and the undo. If the client holds the account, you see what they choose to show you. Whoever authorizes a CRM through a connection link sees which app, why the access is needed, who asked, and that the link runs out. Nothing about the migration, the other CRM, the assessment or the price.

Paperwork

A data processing agreement is available on request, for whichever company is handing us the data. Ask for it before connecting a client's CRM.

What it costs

15% off the published price on every migration you bring.

The published tiers

One price, one time, set by the record count the assessment finds. From $799 for up to 20,000 records to $4,999 for up to 200,000, then $15 for every additional 1,000 records. Nothing recurs.

15% off, whoever pays

A migration that comes through you is 15% off the published tiers and the overage. In co-delivery it comes off our invoice to you, and you bill your client at whatever margin suits you. In a referral it comes off the client's invoice, so your introduction is worth something they can see. The introduction has to come from you, by email, before the client creates an account. It is a percentage on the invoice, not a code and not a second price list.

The assessment is free

It reads the source and writes nothing, and it is what lets you scope before you quote.

A 30-day money-back guarantee

From the day the migration is marked complete. We reverse the migrated data out of the destination and refund whoever paid: the client in a referral, you in co-delivery.

See every plan and work out a price. The guarantee's full terms are on the terms page.

Partner questions

What partners ask first.

01Does our client see Migratez?

That depends on how we work together. In a referral the client creates the account and uses the product themselves. In co-delivery you hold the account, and the client sees what you show them, which is usually the plan, because it is something concrete to review together. If the client's own admin has to authorize a CRM, they get a connection link: a Migratez page naming the app, why the access is needed and who asked, and nothing about the migration. The product carries the Migratez name either way.

02Who does the client pay?

Whoever holds the account. In a referral that is the client, who is invoiced at 15% off the published tiers because you introduced them, and deals with us directly. In co-delivery it is you: we invoice you at the same 15% off, and you bill your client at your own margin. Payment is invoiced rather than taken by card, and a refund under the guarantee goes to whoever paid.

03Can we run the assessment on a client's source before we quote?

Yes, and it is what the assessment is for. Create the account, connect the client's source with read-only access, and you get every object's record count, every custom field's fill rate and the price, without connecting the destination. It writes nothing. Someone with admin rights in the client's CRM has to sign in at its consent screen. If that is not you, send them a connection link and they authorize it themselves, without a Migratez account and without seeing the assessment.

04What if the destination cannot hold something?

The plan says so before anything is written. Where it makes sense we create a destination field for data with no native home. Where the destination cannot hold something at all, it is named on the plan, so you take it to the client with the price rather than discovering it in month two.

05Can we bring a pair you have not built?

Tell us the two CRMs. Every published migration runs between two of the CRMs we list, in either direction. A CRM outside that list has no connector yet, so nothing can be assessed or priced until it is built, and knowing what your clients use is what decides what gets built next.

06What do you need to sign a DPA?

An email to support@migratez.com saying which company is handing us the data, you or the client, and who signs for it. We send our data processing agreement back for signature. Ask before the first connection to a client CRM, not after.

Next step

Bring us the next migration on your books.

Book a call and bring the client's two CRMs. Or connect the client's source first and run the free assessment, so the call starts from the real record count and price.

Book a partner call Email about a client migration

Ready to scope one now? Create an account and connect the client's source. The assessment is free, read-only and does not move anything.