What's new in YugabyteDB Voyager

New features, key enhancements, and bug fixes

What follows are the release notes for the YugabyteDB Voyager v1 release series. Content will be added as new notable features and changes are available in the patch releases of the YugabyteDB v1 series.

v1.6.5 - February 13, 2024

New features

  • Support for live migration from PostgreSQL databases with the option of fall-forward, using which you can switch to a source-replica PostgreSQL database if an issue arises during migration TP .


  • The live migration workflow has been optimized for Importing indexes and triggers on the target YugabyteDB. Instead of creating indexes on target after cutover, they can now be created concurrently with the CDC phase of import-data-to-target. This ensures that the time consuming task of creating indexes on the target YugabyteDB is completed before the cutover process.

  • The --post-import-data flag of import schema has been renamed to --post-snapshot-import to incorporate live migration workflows.

  • Enhanced analyze schema to report the unsupported extensions on YugabyteDB.

  • Improved UX of yb-voyager get data-migration-report for large set of tables by adding pagination.

  • The YugabyteDB debezium connector version is upgraded to v1.9.5.y.33.2 to leverage support for precise decimal type handling with YugabyteDB versions and later.

  • Enhanced export data status command to report number of rows exported for each table in case of offline migration.

  • Reduced default value of --parallel-jobs for import data to target YugabyteDB to 0.25 of total cores (from 0.5), to improve stability of target YugabyteDB.

Bug fixes

  • Fixed a bug in the CDC phase of import data where parallel ingestion of events with different primary keys having same unique keys was leading to unique constraint errors.

  • Fixed an issue in yb-voyager initiate cutover to target where fallback intent is stored even if you decide to abort the process in the confirmation prompt.

  • Fixed an issue in yb-voyager end migration where the source database is not cleaned up if --save-migration-reports flag is set to false.

  • yb-voyager now gracefully shuts down all child processes on exit, to prevent orphan processes.

  • Fixed a bug in live migration where "\r\n" in text data was silently converted to "\n". This was affecting snapshot phase of live migration as well as offline migration with BETA_FAST_DATA_EXPORT.

v1.6.1 - December 14, 2023

Bug fixes

  • Fixed an issue that occurs in the CDC phase of live migration (including fall-back/fall-forward workflows), leading to transaction conflict errors or bad data in the worst case.
  • Fixed an issue where end migration fails when using dockerised yb-voyager.
  • Fixed an issue where export data from PostgreSQL fails when a single case-sensitive table name is provided to the --table-list argument.

v1.6 - November 30, 2023

New Features

  • Live migration

    • Support for live migration from Oracle databases (with the option of fall-back) TP , using which you can fall back to the original source database if an issue arises during live migration.

    • Various commands that are used in live migration workflows (including fall-forward) have been modified. YugabyteDB Voyager is transitioning from the use of the term "fall-forward database" to the more preferred "source-replica database" terminology. The following table includes the list of modified commands.

      Old command New command
      yb-voyager fall-forward setup ... yb-voyager import data to source-replica ...
      yb-voyager fall-forward synchronize ... yb-voyager export data from target ...
      yb-voyager fall-forward switchover ... yb-voyager initiate cutover to source-replica ...
      yb-voyager cutover initiate ... yb-voyager initiate cutover to target ...
    • A new command yb-voyager get data-migration-report has been added to display table-wise statistics during and post live migration.

  • End migration

    A new command yb-voyager end migration has been added to complete migration by cleaning up metadata on all databases involved in migration, and backing up migration reports, schema, data, and log files.


  • Boolean arguments in yb-voyager commands have been standardized as string arguments for consistent CLI usage. In all yb-voyager commands, there is no need to explicitly use = while setting boolean flags to false; a white-space would work (just like arguments of other types). As a side effect of this action, you cannot use boolean flag names without any value. For example, use --send-diagnostics true instead of --send-diagnostics. The boolean values can now be specified as true/false, yes/no, 1/0.
  • For yb-voyager export/import data, the argument --table-list can now be provided via a file using the arguments --table-list-file-path or exclude-table-list-file-path. The table-list arguments now support glob wildcard characters ? (matches one character) and * (matches zero or more characters). Furthermore, the table-list and exclude-table-list arguments can be used together in a command, which can be beneficial with glob support.
  • Object types in yb-voyager export schema can now be filtered via the arguments --object-type-list or --exclude-object-type-list.
  • In yb-voyager import-data, table names provided via any table-list argument are now by default, case-insensitive. To make it case-sensitive, enclose each name in double quotes.
  • The --verbose argument has been removed from all yb-voyager commands.
  • The --delete argument in yb-voyager archive-changes has been renamed to --delete-changes-without-archiving.
  • yb-voyager analyze-schema now provides additional details in the report, indicating indices that don't get exported, such as reverse indexes, which are unsupported in YugabyteDB.

Bug fix

Removed redundant ALTER COLUMN DDLs present in the exported schema for certain cases.

Known issues

  • Compared to earlier releases, Voyager v1.6 uses a different and incompatible structure to represent the import data state. As a result, Voyager v1.6 can't "continue" a data import operation that was started using Voyager v1.5 or earlier.

  • If you are using dockerised yb-voyager:

    • export schema and export data from Oracle database with SSL (via --oracle-tns-alias) fails. Use a non-docker version of yb-voyager to work around this limitation.

    • end migration command fails. This issue will be addressed in an upcoming release.

v1.5 - September 11, 2023

New feature

Note that as the feature in Tech Preview, there are some known limitations. For details, refer to Live migration limitations, and Live migration with fall-forward limitations.

Key enhancements

  • The yb-voyager export data and export schema commands now support overriding the pg_dump arguments internally. The arguments are present at /etc/yb-voyager/pg_dump-args.ini. Any additions or modifications to this file will be honoured by yb-voyager.
  • All yb-voyager commands that require a password now support providing passwords using environment variables such as SOURCE_DB_PASSWORD and TARGET_DB_PASSWORD. This addresses the security concern of a password being leaked via the ps command output. In addition, the password will not be present in any configuration or log files on the disk.

v1.4 - June 30, 2023

Key enhancements

  • The import data file command now supports importing multiple files to the same table. Moreover, glob expressions can be provided in the --file-table-map argument to specify multiple files to be imported into the same table.

  • In addition to AWS S3, import data file now supports directly importing objects (CSV/TEXT files) stored in GCS and Azure Blob Storage. You can specify GCS and Azure Blob Storage "directories" by prefixing them with gs:// and https://.

  • When using the accelerated data export, Voyager can now connect to the source databases using SSL.

  • The analyze-schema command now reports unsupported data types.

  • The --file-opts CLI argument is now deprecated. Use the new --escape-char and --quote-char options.

Bug fixes

  • Fixed the issue where, if a CSV file had empty lines, import data status would continue reporting the import status as MIGRATING even though the import was completed and successful.

  • yb-voyager now explicitly closes the source/target database connections when exiting.

  • The import data file command now uses tab (\t) instead of comma (,) as the default delimiter when importing TEXT formatted files.

Known issues

  • Compared to earlier releases, Voyager v1.4 uses a different and incompatible structure to represent the import data state. As a result, Voyager v1.4 can't "continue" a data import operation that was started using Voyager v1.3 or earlier.

v1.3 - May 30, 2023

Key enhancements

  • Export data for MySQL and Oracle is now 2-4x faster. To leverage this performance improvement, set the environment variable BETA_FAST_DATA_EXPORT=1. Most features, such as migrating partitioned tables, sequences, and so on, are supported in this mode. Refer to Export data for more details.

  • Added support for characters such as backspace(\b) in quote and escape character with --file-opts in import data file.

  • Added ability to specify null value string in import data file.

  • During export data, yb-voyager can now explicitly inform you of any unsupported data types, and requests for permission to ignore them.

Bug fixes

  • yb-voyager can now parse CREATE TABLE statements that have complex check constraints.

  • Import data file with AWS S3 now works when yb-voyager is installed via Docker.

v1.2 - April 3, 2023

Key enhancements

  • When using the import data file command with the --data-dir option, you can provide an AWS S3 bucket as a path to the data directory.

  • Added support for rotation of log files in a new logs directory found in export-dir/logs.

Known issues

  • 16658 The import data file command may not recognise the data directory being provided, causing the step to fail for Dockerized yb-voyager.

v1.1 - March 7, 2023

Key enhancements

  • When using the import data file command with CSV files, YB Voyager now supports any character as an escape character and a quote character in the --file-opts flag, such as single quote (') as a quote_char and backslash (\) as an escape_char, and so on. Previously, YB Voyager only supported double quotes (") as a quote character and an escape character.

  • Creating the Orafce extension on the target database for Oracle migrations is now available by default.

  • User creation for Oracle no longer requires EXECUTE permissions on PROCEDURE, FUNCTION, PACKAGE, and PACKAGE BODY objects.

  • The precision and scale of numeric data types from Oracle are migrated to the target database.

  • For PostgreSQL migrations, YB Voyager no longer uses a password in the pg_dump command running in the background. Instead, the password is internally set as an environment variable to be used by pg_dump.

  • For any syntax error in the data file or CSV file, complete error details such as line number, column, and data are displayed in the output of the import data or import data file commands.

  • For the export data command, the list of table names passed in the --table-list and --exclude-table-list are, by default, case insensitive. Enclose each name in double quotes to make it case-sensitive.

  • In the 1.0 release, the schema details in the report generated via analyze-schema are sent with diagnostics when the --send-diagnostics flag is on. These schema details are now removed before sending diagnostics.

  • The object types which YB Voyager can't categorize are placed in a separate file as uncategorized.sql, and the information regarding this file is available as a note under the Notes section in the report generated via analyze-schema.

Bug fixes

  • [765] Fixed function parsing issue when the complete body of the function is in a single line.
  • [757] Fixed the issue of migrating tables with names as reserved keywords in the target.