Skip to content
Legal

Last updated September 13, 2026

Privacy Policy

Migratez is a data migration service operated by Upper Cap Software Solutions LLP. This policy explains what data we handle when you use the service at app.migratez.com, and how we treat it. It covers both the account you create with us and the data we read and write on your behalf while we move it from one application into another.

Before you connect an application

  • The source is read-only. Your first connection is to the system you are leaving. Migratez reads it to count records and inspect custom-field usage, but never writes back to it.
  • The assessment writes to neither system. It uses what it reads to show your price and prepare the migration plan before anything moves.
  • The destination is connected afterwards. It needs read and write access because, once you approve the migration, Migratez sets up the fields your data needs and writes the migrated records there.
  • Connecting does not start a migration. You see the plan before any records are moved, and the migration starts only when you ask for it.

What we collect

  • Your account. Sign-in is passwordless, with Google or a code we email you, so we never ask for or store a password. We hold your email address and the record of the migrations you set up.
  • The applications you connect. Connections use OAuth or an API key, so we hold the access tokens or key needed for the connection, not application passwords. The source is only ever read and is never written to; the destination is granted read and write, because that is where your records and the fields they need are written.
  • Your migration data. The records, fields, history, and attachments we move for you, handled for as long as the migration can still be run or undone.
  • Payments and support. You are invoiced, and payment is handled by Skydo. There is no card form on Migratez, so your card and bank details never reach us. We keep the messages you send support.
  • Usage data. Basic technical data such as your IP address, browser, and the pages you visit, used to keep the service secure and working.

How we use it

We use your data to assess your source and show you what will move, to run the migration you chose, to let you undo it, to take payment, and to support you. We do not sell your data, and we do not use the contents of your records to advertise.

Who we share it with

We use a few providers to run Migratez, and they process data on our behalf and under our instructions: DigitalOcean for hosting and managed databases, Google for sign-in and reCAPTCHA, PostHog for product analytics, and Skydo to invoice and take payment. Skydo receives your billing details, and none of the data we migrate for you.

Migratez is operated from India, but the service and the data it moves run on DigitalOcean in the United States. Where we transfer personal data across borders we rely on appropriate safeguards such as standard contractual clauses.

Cookies

We use essential cookies to keep you signed in. Where we use analytics or anti-abuse tools such as PostHog or reCAPTCHA, those set their own cookies.

How long we keep it

We keep your account data while your account is active. We handle your migration data only while a migration can still be run or undone, and our backups are kept for seven days before they age out. When you ask us to delete your data, or close your account, we remove it.

Your rights

You can revoke either application's connection from that application at any time. You can ask us what personal data we hold about you and ask us to correct or delete it, and you can complain to a data protection authority. Write to support@migratez.com and we will respond within 30 days.

Security

Connections use OAuth or, for Freshsales, an API key and account address. We never handle your application passwords. OAuth tokens are encrypted before storage. Freshsales API keys are stored as connection data without that application-level encryption. Data is encrypted in transit, we ask the destination for only what a migration needs where the application lets us choose, and the source is never written to.

Each migration runs in a database created for it, so the copy of your records we work from is never held next to another customer's. That copy 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, we drop that whole database rather than clearing rows out of a shared one.

No system is completely secure, but these are the measures we take. If a breach affects your personal data, we will tell you within 72 hours of becoming aware of it.

Changes and contact

If we change this policy we will update the date above, and for a material change we will let you know. Questions about this policy or your data go to support@migratez.com. We reply within about two business days.