10 Best Cloud Migration Tools in 2026

Summary

  • Moving servers into one cloud: start with that provider's own free tool, Azure Migrate, AWS Transform MGN or Google Cloud Migration Center.
  • Changing database engines with little downtime: AWS Database Migration Service, Google Cloud Database Migration Service or Azure Database Migration Service.
  • Moving SaaS and database data into a warehouse, and keeping it in sync after cutover: Skyvia or Fivetran.
  • Loading into BigQuery, or replicating SAP and mainframe changes: BigQuery Data Transfer Service or Qlik Talend Cloud.

The cutover is booked and the old contract ends a month later. And the 40 tables that change every minute? Nobody has tested them yet. That’s typically when a team starts looking at cloud migration tools, which is late. A tool built for servers knows nothing about Salesforce objects. A SaaS pipeline won’t convert an Oracle schema. Pick for the wrong layer and the dry run is where you learn it.

So we sorted this list by what each tool moves. Three of them move whole servers. Three handle database engines, and the last four deal with app and warehouse data. For each tool you’ll see how it keeps the outage short, what the bill is based on, how long you get it free during the migration, and the first limit you’re likely to run into.

We took every price and limit from the vendors’ own pricing pages and documentation.

How we chose and checked these tools

The deciding question is the migration layer. Put simply: what does the tool move, and how does it keep up with changes made while the move is underway? Plenty of projects span two layers, so knowing which tool handles which saves a bad surprise.

  • Servers and applications: entire virtual or physical machines, copied block by block and started up again in the cloud.
  • Databases: the engines themselves. Expect a full load first, change data capture (CDC) running until cutover, and schema conversion whenever the engine changes.
  • App and warehouse data: records pulled from SaaS apps, files and databases into a warehouse or another app, and frequently kept in sync once the move is done.

There’s also a difference between native and third-party tools. Azure, AWS and Google provide migration services for moving workloads into their own clouds. Those are usually the first ones to check for server and database moves. Third-party tools become more useful when data crosses cloud platforms, comes from SaaS applications, or needs to keep flowing after the migration.

Within a layer, every tool faced identical questions. Does the source stay live during the move? How are schemas created or converted? What does the bill count, and how long is the free window? How is it deployed? We read every vendor’s pricing page and documentation as seen from the US, and prices and plan limits are accurate as of November 10, 2026.

We make Skyvia, one of the four data tools here. It was judged on the same fields as every other tool, limitations included.

Some names are missing on purpose. Matillion and Informatica are ETL platforms, and our ETL tools list covers them. Datadog, Dynatrace and AppDynamics monitor workloads instead of moving them, and Device42 or CAST stop at assessment. OpenText Migrate and RiverMeadow rehost servers on enterprise quotes, while the cloud providers’ own tools are free for the migration window. MigrationWiz and AvePoint handle mailboxes and documents. VMware HCX only moves vSphere workloads into VMware-based clouds.

The 10 best cloud migration tools

Best for server moves to Azure: Azure Migrate

Discovery, assessment, the move itself: in Azure Migrate, Microsoft keeps all three under one roof. First comes a small appliance on your network, and it counts every VMware, Hyper-V and physical server it finds. Then each machine gets graded for readiness, size, cost and what it depends on. After that, servers get replicated into Azure, while SQL Server databases are handed to Azure Database Migration Service. There’s also an Azure Copilot migration agent (in preview since March 2026) that answers planning questions about the inventory and the business case.

  • Best for: teams on the Microsoft stack that are shifting servers, SQL Server databases and web apps to Azure.
  • Migration layer: servers and applications. Agentless VMware replication leans on VMware snapshots and changed block tracking, with delta cycles between 1 and 12 hours apart and one final delta at migration. Physical servers and VMs from other clouds take the agent-based route through a replication appliance.
  • Pricing: discovery, assessment and the business case are free. Every machine gets 180 free days of server migration, and after that a replicated instance runs $25 a month. Storage, transactions and data transfer during replication are billed as usual.
  • Deployment: an Azure portal service plus an on-premises appliance (a VM) for discovery and agentless replication.
Azure Migrate assessment showing application readiness, recommended migration paths, and estimated cloud costs

Strengths

  • The assessment and the business case, which sets on-premises costs against Azure costs, cost nothing.
  • With a scale-out appliance, Azure Migrate can replicate up to 500 VMs per vCenter at once, compared with 300 using a single appliance. It also supports data disks up to 32 TB.

Limitations

  • Workloads land in Azure only. VMs from AWS or Google Cloud migrate as physical servers through the agent-based path.
  • Existing VM snapshots block agentless replication, and it clashes with snapshot-based backup tools that run at the same time.

Best for rehosting servers into AWS: AWS Transform MGN

Since June 2026, AWS Application Migration Service goes by AWS Transform MGN and sits inside AWS Transform. It turns physical, virtual or cloud servers into Amazon EC2 instances using continuous block-level replication. You launch test instances first. Per AWS, the switch itself usually takes minutes.

  • Best for: putting servers on EC2 as they are, from VMware vSphere, Hyper-V, bare metal or another cloud.
  • Migration layer: servers and applications. The AWS Replication Agent on each source server copies disk blocks nonstop, so the source keeps running until cutover.
  • Pricing: the first 90 days (2,160 hours) of replication per server are free. After that it’s $0.042 per server-hour, about $30 a month, in every supported Region. The replication infrastructure and the EC2 and EBS behind test and cutover instances are billed separately, free period included.
  • Deployment: a managed AWS service, with an agent on every source server and a staging subnet in your account; VPN, Direct Connect or VPC peering for private connectivity.
AWS Transform MGN migration dashboard showing server lifecycle, data replication status, and readiness for testing

Strengths

  • Test launches leave the source alone, so rehearse the cutover as many times as you want.
  • You get two ways in, agentic rehosting through AWS Transform or the self-directed MGN console, and switching between them doesn’t cost you progress.

Limitations

  • New deployments can’t use agentless replication anymore (October 2026), which means every source server needs the agent.
  • The free 2,160 hours start ticking when the agent is installed, not at cutover. Long test cycles eat them up.

Best for planning VM moves into Google Cloud: Google Cloud Migration Center

Migration Center does the groundwork: discovery, total cost of ownership (TCO) estimates, assessment and migration planning. The actual move goes to Google’s execution tools. For virtual machines that’s Migrate to Virtual Machines, which replicates VMs into Compute Engine; databases go to Database Migration Service.

  • Best for: teams moving VMware, AWS or Azure virtual machines into Compute Engine.
  • Migration layer: servers (virtual machines). Migrate to Virtual Machines snapshots each disk once, then sends only the changed blocks, every two hours by default, while the source keeps running. At cutover it stops the source VM, runs a final replication and creates the production instance.
  • Pricing: the cost estimate and the assessment in Migration Center are free, and so is Migrate to Virtual Machines for migrations into Google Cloud. What you do pay for is the Compute Engine VMs (test clones included), storage and network. New Google Cloud accounts get $300 in free credit, a one-time trial allowance.
  • Deployment: Google Cloud console services; a discovery client or the offline mcdc command-line tool for inventory, and a Migrate Connector appliance (4 CPUs, 16 GB of RAM) in vSphere.
Google Cloud Migration Center showing discovered assets, total cores, memory and the operating system split

Strengths

  • Discovery and TCO assessment are free, and the mcdc tool can build an offline assessment without uploading data to Google Cloud.
  • Test clones let you boot the migrated VM in Compute Engine before cutover.

Limitations

  • The VM part is handled by Migrate to Virtual Machines, which accepts sources on vSphere, AWS, Azure and Google Cloud VMware Engine. What about physical boxes, or a hypervisor other than vSphere on premises? Google sends you to third-party tools for those.
  • No vCenter linked mode support in the Migrate Connector, so you install one per vCenter.

Best for keeping a database live while it moves to AWS: AWS Database Migration Service

With AWS Database Migration Service (DMS), relational, NoSQL and warehouse databases land in AWS on the same engine or a new one. Pick a full load, ongoing change data capture or both; meanwhile the source keeps serving traffic until the job finishes. AWS calls the result near-zero downtime.

  • Best for: database moves into AWS that can’t take much downtime, with or without an engine change.
  • Migration layer: databases. Full load plus CDC, and DMS creates target tables and primary keys if they’re missing. When the engine changes, DMS Schema Conversion converts tables, views, stored procedures and functions (rules first, generative AI where the rules fall short) on paths into PostgreSQL from Oracle, SQL Server, Db2 LUW, Db2 for z/OS and SAP ASE.
  • Pricing: on-demand replication instances bill by the hour. DMS Serverless is billed at $0.087 an hour per DMS capacity unit (DCU), Single-AZ in US East (Ohio), where 1 DCU is 2 GB of RAM, and homogeneous data migrations are billed at $0.08 per migration hour. The only Schema Conversion cost is its S3 storage. Inbound data transfer to DMS is free, and new AWS accounts can put Free Tier credits toward it.
  • Deployment: AWS runs it for you, on replication instances you pick or on Serverless, single or multiple Availability Zones; sources may be on-premises, on EC2, on RDS or at another cloud provider.
AWS DMS monitoring showing two completed full-load tasks with their throughput charts in rows and bandwidth

Strengths

  • Schema conversion costs nothing, and generative AI helps on five paths into PostgreSQL.
  • Data validation spots mismatches, and data resync repairs them for Oracle and SQL Server sources going to PostgreSQL (engine 3.6.1 or later).

Limitations

  • AWS DMS also supports on-premises database targets, but at least one endpoint must run on AWS. Schema Conversion is designed for supported AWS database and warehouse targets, including Aurora, RDS and Redshift.
  • Homogeneous migrations pick up schema changes during ongoing replication on MySQL only. On other engines, a new source table means a restart.

Best for database moves into Cloud SQL or AlloyDB: Google Cloud Database Migration Service

Google Cloud Database Migration Service is serverless (no machines for you to set up). A continuous job starts with a snapshot. After that, changes keep flowing while people still use the old database, right up until the new one is promoted. Changing engines? Engine switches go through a conversion workspace, where Gemini proposes the converted procedures, triggers and functions.

  • Best for: keeping MySQL, PostgreSQL or SQL Server on its engine in Cloud SQL, or taking Oracle and SQL Server over to PostgreSQL.
  • Migration layer: databases. Four routes exist. MySQL lands in Cloud SQL for MySQL; PostgreSQL in Cloud SQL for PostgreSQL or AlloyDB; SQL Server in Cloud SQL for SQL Server; Oracle or SQL Server in Cloud SQL for PostgreSQL or AlloyDB. Continuous jobs pair a snapshot with CDC. One-time jobs mean downtime.
  • Pricing: a same-engine move adds no Database Migration Service fee, so the destination instance is the only bill. Cross-engine jobs bill per GiB processed. Engine changes cost money, though. Expect $2.00 per GiB of change data capture for the first 2,500 GiB a month in us-central1 (the rate drops after that), and $0.40 per GiB of backfill once the monthly free allowance runs out.
  • Deployment: nothing to host, since Google Cloud runs the whole thing.
Google Cloud Database Migration Service console showing database migration jobs with running and completed statuses

Strengths

  • Same-engine moves cost nothing beyond the target database.
  • Gemini-assisted conversion for engine changes has been generally available since September 2025.

Limitations

  • Targets are Google Cloud managed databases only, and Oracle can only go to PostgreSQL.
  • Cross-engine CDC bills every GiB for as long as the job runs. A long parallel run gets expensive fast.

Best for SQL Server, MySQL or PostgreSQL headed to Azure: Azure Database Migration Service

You start Azure Database Migration Service jobs from the portal, PowerShell or the Azure CLI; the infrastructure behind them is Microsoft’s job. Online migrations keep the outage to the cutover itself. Those are available for Azure SQL Managed Instance, SQL Server on Azure VMs, the flexible servers for MySQL and PostgreSQL, and Azure Cosmos DB. Guides that begin in Azure Data Studio are outdated now, because its migration extension was retired on February 28, 2026.

  • Best for: teams taking SQL Server, MySQL, PostgreSQL or MongoDB databases onto Azure’s managed services.
  • Migration layer: databases. For SQL Server going to Managed Instance or an Azure VM, the service keeps restoring full and log backups up to cutover. Each engine gets its own method. Azure SQL Database receives a logical copy of the tables, MySQL replicates through the binlog, PostgreSQL starts from pg_dump and pg_restore before applying changes, and MongoDB lands in Azure Cosmos DB.
  • Pricing: charged by the vCore-hour. The Standard tier (1, 2 or 4 vCores) handles offline migrations and is free. Online migrations need Premium (4 vCores), which is free for 183 days from each service’s creation and then $0.37 an hour.
  • Deployment: a managed Azure service; SQL Server migrations also need a self-hosted integration runtime on a machine you provide.
Azure Database Migration Service showing a completed migration with source, target and schema deployment status

Strengths

  • Offline migrations on the Standard tier cost nothing, and each new Premium service gets its own 183 free days.
  • SQL Server, MySQL (Amazon RDS, Aurora and Cloud SQL sources too), PostgreSQL and MongoDB all fit in a single service.

Limitations

  • With Azure SQL Database as the target, it’s offline only, which means the outage starts together with the migration.
  • The tooling moved around. The Azure Data Studio extension is gone and the classic service’s SQL Server scenarios ended on March 15, 2026, which makes older walkthroughs obsolete.

Best for no-code moves of SaaS and database data: Skyvia

Skyvia is the no-code cloud data platform we build. Apps, databases, warehouses, file storages: 200+ connectors cover them. Replication is the piece for a move that later becomes a sync. Skyvia builds the target tables, loads the data once, and from then on fetches just the records that are new or changed. Moving between apps (say, a Salesforce org-to-org copy or a sandbox) is a separate job. For those you use Import.

One example is a hotel management company’s migration from a legacy CRM to HubSpot. The team had to deal with duplicate contacts, email records stored across several tables, and HubSpot API limits. Skyvia was used to prepare and map the data, load it into HubSpot, and check the results after the move.

  • Best for: teams that want SaaS or database records in a warehouse or another app with no code, and maybe a sync once cutover is done.
  • Migration layer: SaaS app and database records. Destinations? BigQuery, Snowflake, Redshift, Azure Synapse, Databricks, or a database of your choice. SQL Server sources use Change Tracking, and other sources load new and changed records incrementally by timestamp.
  • Pricing: priced by records written per month, with unlimited users. The Free plan covers 10K records a month with daily runs. Look at the same volume, 5M records a month: Basic is $79 billed annually ($99 billed monthly) with one run a day, and Standard is $159 billed annually ($199 billed monthly) with hourly runs. Minute-level runs come with Professional, from $399 billed annually or $499 billed monthly for 10M records.
  • Deployment: Skyvia is cloud-hosted, and an on-premises Agent reaches databases behind your firewall by calling out over HTTPS on port 443 (no inbound ports needed).
Skyvia Replication from Salesforce to SQL Server with incremental updates and target table creation enabled

Strengths

  • Replication, import, sync and automation share one connection, so the first load and every sync after it sit together.
  • Try the move on real records with the free plan, then choose a paid tier.

Limitations

  • Native change capture exists for SQL Server only, through Change Tracking. Everything else loads incrementally by timestamp. Once a minute is the fastest schedule, and only on Professional.
  • New fields in a source go unnoticed until you refresh the metadata, so build that step into your plan.

Best for maintained connectors at enterprise scale: Fivetran

Into a warehouse or lake, Fivetran brings SaaS apps, databases and files, and its Standard plan already carries 700+ managed connectors. Each new database connection copies the selected data in full first; from there it looks for changes on a schedule. Destination schemas and tables? Fivetran creates them for you. It also merged with dbt Labs, a deal that closed on June 1, 2026.

  • Best for: teams who’d rather pay for maintained connectors, during the warehouse migration and in the sync afterward.
  • Migration layer: app, database and file data, at scale. Changes come from each database’s own logs. That means the binary log on MySQL and MariaDB, Change Tracking or CDC on SQL Server, logical replication on PostgreSQL, and Fivetran’s Binary Log Reader on Oracle. For Teleport Sync, a read-only SQL connection is enough.
  • Pricing: billed by monthly active rows (MAR). The Free plan covers 500,000 MAR a month. Standard is usage-based with an estimator rather than a list price, and since January 1, 2026 each connection with 1 to 1M MAR pays a $5 base charge a month. Initial syncs and re-syncs don’t count toward MAR, and each new connection gets 14 days of free use.
  • Deployment: managed SaaS; Hybrid Deployment on Enterprise and Business Critical runs pipelines inside your network.
Fivetran schema change settings showing options to allow all changes, allow new columns, or block schema changes

Strengths

  • The historical load is free, so a migration’s first full copy never shows up on the bill.
  • Schema settings per connection decide whether new tables and columns flow through automatically.

Limitations

  • Oracle counts as an enterprise database connector, and you’ll only find it on Enterprise and Business Critical.
  • Standard caps out at 15-minute syncs. For 1-minute syncs you need Enterprise or Business Critical.

Best for bringing SaaS and warehouse data into BigQuery: BigQuery Data Transfer Service

BigQuery Data Transfer Service is Google’s managed scheduler for loading data into BigQuery. Setup happens in the console, through the bq tool or by API, and when something is missing, a backfill fills the gap. Warehouse migrations from Amazon Redshift and Teradata are covered too. Third-party connectors such as Salesforce, ServiceNow, MySQL, PostgreSQL and Oracle have reached general availability.

  • Best for: teams gathering Google marketing data, object storage, SaaS apps or a second warehouse in BigQuery.
  • Migration layer: app and warehouse data, into BigQuery only. Every transfer runs on a schedule, either as a full load or incrementally. The incremental kind relies on a timestamp column to append or upsert rows; there’s no log-based CDC here.
  • Pricing: no orchestration charge for Google sources (Google Play aside), object storage or the warehouse migration connectors. Paid connectors are metered at $0.06 per slot-hour in us-central1. Google suggests budgeting for up to 20 slot-hours per hour of transfer runtime, or roughly $1.20 an hour in us-central1. That’s a planning estimate, not a billing cap. Loading into native tables is free, and merges bill at standard BigQuery rates.
  • Deployment: a fully managed Google Cloud service; the transfer runs in the destination dataset’s location.
BigQuery Data Transfer Service configuration showing a Google Ads data transfer and its destination dataset

Strengths

  • No orchestration fee applies to warehouse migrations from Redshift and Teradata, or to Google sources.
  • Incremental upserts went GA for Salesforce in July 2026 and for PostgreSQL and ServiceNow in October 2026.

Limitations

  • It only loads into BigQuery; nothing goes back out.
  • Incremental transfers can’t sync deletes, and Google’s data delivery SLO covers Google Cloud sources only.

Best for SAP, mainframe and hybrid change capture: Qlik Talend Cloud

One Qlik Talend Cloud subscription covers data movement, log-based change data capture, transformation and data quality. Starting with Standard, you host a Data Movement gateway yourself, and it streams CDC continuously from the databases behind your firewall. The full load creates the target tables. After that, you decide per change type whether a schema change gets applied, ignored or paused.

  • Best for: hybrid estates where changes in on-premises databases, SAP or the mainframe have to reach the cloud.
  • Migration layer: app and database data moving into cloud warehouses and data platforms, including Snowflake, BigQuery, Redshift and Databricks. Tasks can start with a full load and continue with change data capture through the Data Movement gateway. Real-time SAP and mainframe sources require Enterprise.
  • Pricing: a capacity subscription metered on data moved, plus job executions and duration on Premium and Enterprise. Qlik’s own AWS Marketplace listing starts Starter at $6,000 a year on a 12-month contract, for up to 50 GB moved a month, and other editions are quoted. A 14-day free trial needs no credit card.
  • Deployment: Qlik Cloud SaaS; from Standard, a customer-hosted gateway and hybrid or client-managed deployment.
Qlik Talend Cloud replication pipeline configured to move PostgreSQL data into Snowflake

Strengths

  • Continuous log-based CDC runs through the gateway, real-time SAP and mainframe sources on Enterprise included.
  • You can configure schema evolution per change type: apply, ignore, suspend the table or stop the task.

Limitations

  • Starter replicates every six hours by default and has no low-latency CDC, and transformations begin at Premium.
  • CDC into landing doesn’t carry deletes. The Reload and compare mode does, with full loads.

What changed for cloud migration tools in 2026

Plenty of comparisons still describe these products as they looked in 2024. Here’s what’s different now.

  • AWS renamed Application Migration Service to AWS Transform MGN in June 2026. The APIs, replication engine, pricing, and free period didn’t change. Agentless replication, however, is no longer available for new deployments as of October 2026.
  • AWS retired DMS Fleet Advisor on May 20, 2026. DMS Schema Conversion now also works from an offline SQL Server source, and AI agents can drive it through AWS’s MCP server (July 2026).
  • Azure’s database tooling moved. Azure Data Studio and its migration extension were retired on February 28, 2026, and the classic Database Migration Service’s SQL Server scenarios ended on March 15, 2026.
  • Azure Migrate added the Azure Copilot migration agent in March 2026, still in preview, to answer questions about inventory, readiness and the business case.
  • BigQuery Data Transfer Service got incremental transfers, generally available for Salesforce since July 2026 and for PostgreSQL and ServiceNow since October 2026.
  • Ownership changed. On the ownership side, Informatica has belonged to Salesforce since November 18, 2025, and Fivetran closed its merger with dbt Labs on June 1, 2026.

Which cloud migration tool fits which move

  • Servers into one cloud: go with the provider’s tool (Azure Migrate, AWS Transform MGN, or Google Cloud Migration Center). During the migration window you don’t pay for the tool, only for the infrastructure on the other side.
  • Oracle or SQL Server into AWS with little downtime: AWS Database Migration Service, plus Schema Conversion at no charge for the new engine.
  • MySQL or PostgreSQL into Cloud SQL on the same engine: Google Cloud Database Migration Service, where the target instance is the whole bill.
  • SQL Server into Azure SQL Managed Instance: Azure Database Migration Service, Microsoft’s own option. One thing to check before setting a cutover date: does your target support online migration?
  • SaaS apps and databases into a warehouse, no code, then a sync: Skyvia, billed by records, with a free plan for testing.
  • Many sources into a warehouse with maintained connectors: Fivetran, since the historical load costs nothing and only later changes are billed.
  • Google sources, storage or another warehouse into BigQuery: BigQuery Data Transfer Service.
  • SAP or mainframe changes into the cloud: Qlik Talend Cloud on the Enterprise edition.

Most projects end up with tools from two layers. A server or database service does the move itself, and a data tool looks after the apps that keep writing after cutover. 

Thoroughly validate all tools and their licensing requirements for both pre- and post-migration activities.” 

Sauveer Ketan, cloud solutions architect 

Why does that advice matter here? Because the free windows end: 180 days per machine on Azure Migrate, 90 days per server on AWS Transform MGN, 183 days per Premium service on Azure Database Migration Service. 

ToolMigration layerChange captureWhat you pay forFree option
Azure MigrateServers and applicationsSnapshot and changed block replication$25 a month per replicated instance after the free period180 days per machine
AWS Transform MGNServers and applicationsContinuous block-level replication$0.042 per server-hour after the free period90 days (2,160 hours) per server
Google Cloud Migration CenterServers (VMs)Changed blocks every 2 hours by defaultTarget Compute Engine resourcesDiscovery, assessment and migration tooling free
AWS Database Migration ServiceDatabasesFull load plus CDCInstance hours, $0.087 per DCU-hour (Serverless), $0.08 per migration hour (homogeneous)AWS Free Tier credits
Google Cloud Database Migration ServiceDatabasesSnapshot plus CDC$2.00 per GiB of CDC (cross-engine, first tier)Same-engine migrations
Azure Database Migration ServiceDatabasesBackup restore, binlog replication, CDC$0.37 an hour (Premium) after 183 daysStandard tier for offline migrations; Premium 4-vCore free for 183 days
SkyviaApp and warehouse dataChange Tracking for SQL Server, timestamp-based for othersRecords written per month: Basic for 5M records $79 billed annually, $99 billed monthlyFree plan, 10K records a month
FivetranApp and warehouse dataNative database logsMonthly active rows, plus $5 per connection with 1 to 1M MARFree plan, 500,000 MAR a month
BigQuery Data Transfer ServiceApp and warehouse dataScheduled full or incremental loads$0.06 per slot-hour for paid connectorsGoogle sources, storage and migration connectors
Qlik Talend CloudApp and warehouse dataLog-based CDC through a gatewayData moved: Starter $6,000 a year for 50 GB a month14-day trial

A cutover checklist and reconciliation query

Copy this list into your runbook and write an owner’s name beside each line.

  • Freeze schema changes on the source from the final test run until cutover.
  • Run a full test migration against a copy of production data, because a sample won’t do.
  • Write down each table’s row count and its most recent change timestamp, on both sides.
  • Match records by primary key, and note anything missing, extra or changed.
  • Throw your heaviest reports and queries at the target and time them.
  • Leave replication lag for last, right before you flip the switch. If it hasn’t dropped to almost nothing, wait.
  • Keep the source read-only until reconciliation comes back clean.
  • Settle the rollback trigger before go-live, whether that’s a specific error or a delay long enough to send traffic back.

Row counts alone can lie. Picture a customers table with five rows on each side, where one record never made it across, an extra one showed up in the target, and two have timestamps that don’t agree. Counts match, data doesn’t. Put a snapshot of the source table next to the target and run this query to list every difference (it’s standard SQL, and we ran it in SQLite):

SELECT
  COALESCE(s.id, t.id) AS id,
  CASE
    WHEN t.id IS NULL THEN 'missing in target'
    WHEN s.id IS NULL THEN 'extra in target'
    ELSE 'changed since load'
  END AS issue
FROM source_customers AS s
FULL OUTER JOIN target_customers AS t ON s.id = t.id
WHERE t.id IS NULL
   OR s.id IS NULL
   OR s.updated_at IS DISTINCT FROM t.updated_at
ORDER BY id;

A plain <> misses what IS DISTINCT FROM catches: it treats two empty timestamps as equal and an empty one against a value as different. If your tables have no change timestamp, swap updated_at for a hash of the row. An empty result means the record IDs and change timestamps match. It doesn’t prove every field is identical, so check the values that matter most separately before cutover. For the planning side, see our data migration plan guide, and for Salesforce moves, our guide to Salesforce data migration. Data migration solutions that work beyond a single cloud provider are compared in our review.

FAQ for Cloud Migration Tools

Loader image

AWS sorts them into discovery and planning, business case, application mobility and data mobility tools. For the move itself, AWS Transform MGN rehosts servers and AWS Database Migration Service moves databases, with Schema Conversion covering engine changes. On top of that, AWS Transform adds agentic help for migration and modernization. 

Usually not, if servers or databases are going into that provider’s own cloud. The native tools cover those, and several are free for the migration window. Bring in a third-party tool if your data sits in SaaS apps, if it’s crossing to another cloud or into an app, or if the migration needs to keep running as a scheduled sync after cutover. 

Migration is a one-time job. You move to a new system, and it’s over at cutover. Integration keeps data flowing between systems on a schedule. When the old system keeps running for months after the move, you pay for both systems, so the ongoing sync needs a line in the budget. 

Want app or database data in a warehouse, or moved between two SaaS apps? Try Skyvia’s free plan, run the first load with Replication, and keep it syncing on a schedule until cutover. 

 

Share

Nata Kuznetsova

Nata Kuznetsova is a seasoned writer with nearly two decades of experience in technical documentation and user support. With a strong background in IT, she offers valuable insights into data integration, backup solutions, software, and technology trends.

One platform for all your data work

One platform for all your data work

Integration, automation, live data access, and backup. No code, 200+ connectors.

Start free