A migration means handing someone a copy of your customer records, which is not a small thing to ask. This page says how the connections are made, where the data runs, what is kept once the migration is done, and what we do not claim. If your reviewer needs something that is not here, ask and we will answer it.
Every connection is made over OAuth, so you sign in at the application itself and grant Migratez access. You can withdraw that access from either application at any time, without asking us.
The tokens the two applications issue us are encrypted before they are written to the database, not only while they travel. One that cannot be decrypted is refused outright rather than passed on as an empty credential, so the problem surfaces as a connection to remake rather than as an unexplained failure later on.
It is granted read access and nothing else, and Migratez never writes to it. That is the shape of the connection, not a promise about how we behave once we have it.
It is connected second, with read and write access, because your records have to be written there and the fields that hold them have to exist first.
These are the providers that handle any part of it, and what each one is for. Each processes data on our behalf and under our instructions.
Hosting and managed databases, in the United States. This is where the service runs and where your data sits while we move it.
Sign-in and reCAPTCHA. Sign-in is passwordless, so there is no password to store.
Product analytics.
Invoicing and payment. Skydo receives your billing details and none of the data we migrate for you. There is no card form on Migratez, so your card and bank details never reach us.
The copy of your records we work from is never held next to another customer's, and it is purged when the migration finishes, however it finishes. What stays behind is the record of what was written where, because that is what lets you undo the migration afterwards. When you ask us to erase your data, that whole database is dropped, rather than rows being cleared out of one shared with everybody else.
DigitalOcean backs the databases up once a day and keeps seven days of them, and a restore can go back to a chosen point inside that window. That is also the honest answer to how long an erasure takes to finish: the database is dropped from the running service when you ask, and the last copy of it ages out of the backups within the week.
There is no second copy running alongside the first. Recovering from a failure means restoring from a backup rather than switching across to a standby, which is a real difference and one worth knowing before you decide.
If a breach affects your personal data, we will tell you within 72 hours of becoming aware of it, at the address on your account.
If the records you are moving belong to your own customers, your contracts with them probably require one before you can hand that data to anybody. Ask at support@migratez.com and we will send it over.
Migratez holds no SOC 2 report, no ISO 27001 certificate, and no compliance badge of any kind, so none is shown here. Our providers hold their own certifications, and those are theirs rather than ours to display. Migratez is one person today, and every migration is run by hand. What you are trusting is that person and the way this is built, rather than an audit someone else signed. If that is the wrong trade for your data, it is better to know it here than to find out later.
Next step
Connect the app you are leaving with read-only access and see your real record count and price. It reads, it writes to neither system, and nothing moves until you ask for it.