AWS Schema Conversion Tool vs Google Migrate to Containers

AWS Schema Conversion Tool (AWS SCT) converts database schemas between engines, including relational OLTP, data warehouse, and NoSQL schemas. If it cannot automate a conversion, it gives guidance for creating an equivalent schema in the target database. A project wizard estimates migration complexity for supported destinations and generates a report for comparing target options. For warehouse migrations to Amazon Redshift, it can manage data extraction agents; it can also create, run, and monitor AWS DMS endpoints and tasks. AWS SCT converts SQL embedded in C++, C#, Java, and other application code for users to review, edit, and save. Supported workload conversions include SSIS packages, Teradata workloads, and Apache Oozie workflows to specified AWS services. It is both a standalone, project-based application and a command-line tool. Planned converted schemas stay local until applied to the target. AWS SCT is free and supports 64-bit Microsoft Windows, Fedora Linux, and Ubuntu Linux. It also supports FIPS standards for connections to Amazon S3 or another AWS resource and is compliant with FedRAMP.

Google Migrate to Containers is a free, self-hosted tool for moving applications from virtual machines or servers into containers without rewriting or re-architecting them. Its local CLI copies a source VM file system, analyzes it, creates a migration plan, and generates deployment artifacts. It can optionally move data files to persistent volumes. Sources include VMware and Compute Engine VMs, and destinations include Google Kubernetes Engine, GKE Autopilot clusters, and Cloud Run. Supported workloads include Linux applications, IBM WebSphere, JBoss, Apache, Tomcat, WordPress, and Windows IIS applications. Linux workloads can be handled locally in offline mode or on a local network without runtime internet downloads. A local machine needs Docker and several gigabytes of storage. Google recommends assessing workload fit first. The console UI, migctl, and processing-cluster CRDs were discontinued in May 2024; Google directs users to the local CLI. Migration has no charge, while other Google Cloud services cost separately.