---
title: "import data reference"
url: "https://docs.yugabyte.com/stable/yugabyte-voyager/reference/data-migration/import-data/"
---

# import data reference

YugabyteDB Voyager import data reference

yb-voyager import data

The following page describes the usage of the following import commands:

- [import data](#import-data "import data") (and import data to target)
- [import data status](#import-data-status "import data status")
- [get data-migration-report](#get-data-migration-report "get data-migration-report")
- [import data to source](#import-data-to-source "import data to source")
- [import data to source-replica](#import-data-to-source-replica "import data to source-replica")

## import data

For offline migration, [Import the data](/stable/yugabyte-voyager/migrate/migrate-steps/#import-data "Import the data") to the YugabyteDB database.

For [live migration](/stable/yugabyte-voyager/migrate/live-migrate/#import-data-to-target "live migration") (with [fall-forward](/stable/yugabyte-voyager/migrate/live-fall-forward/#import-data-to-target "fall-forward") and [fall-back](/stable/yugabyte-voyager/migrate/live-fall-back/#import-data-to-target "fall-back")), the import data command is an alias of `import data to target` which [imports the data](/stable/yugabyte-voyager/migrate/migrate-steps/#import-data "imports the data") from the `data` directory to the target database, and starts ingesting the new changes captured by `export data` to the target database.

### Syntax

Syntax for import data is as follows:

```text
Usage: yb-voyager import data [ <arguments> ... ]
```

Syntax for import data to target is as follows:

```text
Usage: yb-voyager import data to target [ <arguments> ... ]
```

### Arguments

The following table lists the valid CLI flags and parameters for `import data` command.

When run at the same time, flags take precedence over configuration flag settings.

CLI flag

Config file parameter Description 

--batch-size

```yaml
import-data:
  batch-size:
```

Size of batches in the number of rows generated for ingestion during import data.  
Default: 20000 rows  
Example: `yb-voyager import data ... --batch-size 20000` 

--disable-pb

```yaml
import-data:
  disable-pb:
```

Use this argument to disable progress bar or statistics during data import.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

--enable-upsert

```yaml
import-data:
  enable-upsert:
```

Enable UPSERT mode on target tables while importing data.  
Note: Ensure that tables on the target YugabyteDB database do not have secondary indexes. If a table has secondary indexes, setting this flag to true may lead to corruption of the indexes.  
Default: false  
Usage for disabling the mode: `yb-voyager import data ... --enable-upsert false`  
Accepted parameters: true, false, yes, no, 0, 1 

--table-list

```yaml
import-data:
  table-list:
```

Comma-separated list of names of source database tables whose data is to be imported. Table names can also be glob patterns containing wildcard characters, such as an asterisk (\*) (matches zero or more characters) or question mark (?) (matches one character). To use a glob pattern for table names, enclose the list in single quotes ('').  
For example, `--table-list '"Products", order*'`.  
This argument is unsupported for live migration. 

--exclude-table-list

```yaml
import-data:
  exclude-table-list:
```

Comma-separated list of names of source database tables for which data needs to be excluded during import. Table names follow the same convention as `--table-list`.  
This argument is unsupported for live migration. 

--table-list-file-path

```yaml
import-data:
  table-list-file-path:
```

Path of the file containing the list of names of source database tables (comma separated or line separated) to import. Table names use the same convention as `--table-list`. 

--exclude-table-list-file-path

```yaml
import-data:
  exclude-table-list-file-path:
```

Path of the file containing the list of names of source database tables (comma separated or line separated) to exclude while importing data of those exported tables. Table names follow the same convention as `--table-list`. 

--adaptive-parallelism

```yaml
import-data:
  adaptive-parallelism:
```

Adjust parallelism based on the resource usage (CPU, memory) of the target YugabyteDB cluster. Choose from the following modes:

- `balanced` (Default): Run with moderate thresholds. Recommended when other workloads are running on the cluster.
- `aggressive`: Run with maximum CPU thresholds for better performance. Recommended when no other workloads are running on the cluster.
- `disabled`: Disable adaptive parallelism.

--adaptive-parallelism-max

```yaml
import-data:
  adaptive-parallelism-max:
```

Number of maximum parallel jobs to use while importing data when adaptive parallelism is enabled. By default, voyager tries to determine the total number of cores `N` and use it as the maximum parallel jobs. 

--parallel-jobs

```yaml
import-data:
  parallel-jobs:
```

Number of parallel jobs to use while importing data. Depending on the YugabyteDB database configuration, the value of `--parallel-jobs` should be tweaked such that at most 50% of target cores are utilised.  
Default: If yb-voyager can determine the total number of cores N in the YugabyteDB database cluster, it uses N/2 as the default for `import data` and N/4 for `import data to target`. Otherwise, it defaults to twice the number of nodes in the cluster. 

--skip-replication-checks

```yaml
import-data:
  skip-replication-checks:
```

It is NOT recommended to have any form of replication (CDC/xCluster) running on the target YugabyteDB cluster during data import as it may lead to a rapid increase in disk use. If detected, data import is aborted. Use this flag to turn off the checks and continue importing data.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

--truncate-tables

```yaml
import-data:
  truncate-tables:
```

Truncate tables on target YugabyteDB database before importing data. This option is only valid if `--start-clean` is set to true.  
Default: false 

--target-db-type

```yaml
import-data:
  target-db-type
```

Target database type to import into.  
Accepted values: yugabytedb (default), yugabytedb-amp (more details coming soon) 

--use-public-ip

```yaml
import-data:
  use-public-ip:
```

Use the node public IP addresses to distribute `--parallel-jobs` uniformly on data import.  
Default: false  
**Note** that you may need to configure the database with public IP addresses by setting [server-broadcast-addresses](/stable/reference/configuration/yb-tserver/#server-broadcast-addresses "server-broadcast-addresses").  
Example: `yb-voyager import data ... --use-public-ip true`  
Accepted parameters: true, false, yes, no, 0, 1 

--target-endpoints

```yaml
import-data:
  target-endpoints:
```

Comma-separated list of node's endpoint to use for parallel import of data  
Default: Use all the nodes in the cluster. For example: "host1:port1,host2:port2" or "host1,host2". Note: use-public-ip flag will be ignored if this is used. 

--on-primary-key-conflict

```yaml
import-data:
  on-primary-key-conflict:
```

Action to take on primary key conflict during data import.  
Accepted parameters:

- `ERROR` (Default): Import in this mode fails if any primary key conflict is encountered, indicating such conflicts are unexpected.
- `IGNORE`: Skips rows that have an existing primary key allowing the import to continue for the remaining data.

--error-policy-snapshot

```yaml
import-data:
  error-policy-snapshot:
```

Specifies how to handle errors when processing and importing rows to the target YugabyteDB database during the snapshot phase. Errors can arise from reading data from file, transforming rows, or ingesting them into YugabyteDB.  
Accepted parameters:

- `abort` (Default) - Immediately aborts the process.
- `stash-and-continue` - Stashes the errored rows to a file and continues the import.

--max-retries-streaming

```yaml
import-data:
  max-retries-streaming:
```

Maximum number of retries for failed event batch during live migration.  
Default: 15 

--use-partition-root

```yaml
import-data:
  use-partition-root:
```

For partitioned tables during live migration, controls whether CDC data is imported via the root table or child partitions only:

- `true` (default): Import CDC data only via the root table. Refused when the primary key is defined only on the partitions and not on the root; re-run with `false`.
- `false`: Import CDC data only via child partitions. Voyager reports an error when the leaf partitions have inconsistent primary keys.

**Note**: Supported only for YugabyteDB target [v2025.2.3.0](/stable/releases/ybdb-releases/v2025.2#v2025.2.3.0) and later.  
Default: true  
Accepted values: true, false, yes, no, 0, 1 

--cdc-partition-key

```yaml
import-data:
  cdc-partition-key:
```

Global strategy for all tables on how CDC events are partitioned across parallel channels. Strategy is one of the following:

- `auto` (default): Automatically pick `pk` or `table` per table (for example, expression unique-index tables use `table`).
- `pk`: Partition CDC events by primary key.
- `table`: Partition CDC events by table (all events for a table share one channel).

--cdc-partition-key-overrides

```yaml
import-data:
  cdc-partition-key-overrides:
```

Per-table CDC partition-key overrides in the form `schema.table:strategy`, separated by ';'. Strategy is one of the following:

- `pk`: Partition CDC events by primary key. Example: `sales.events:pk`
- `table`: Partition CDC events by table (all events for a table share one channel). Example: `public.orders:table`
- `(col1,col2)`: Partition CDC events by the given column values (immutable columns), in the form `(col1,col2)`. Example: `public.payments:(customer_id,region)`

Unlisted tables keep the global `--cdc-partition-key`. For information on how to choose a strategy, see [Improve import CDC streaming performance](/stable/yugabyte-voyager/reference/performance/#improve-import-cdc-streaming-performance "Improve import CDC streaming performance").

-e, --export-dir

```yaml
export-dir:
```

Path to the export directory. This directory is a workspace used to store exported schema DDL files, export data files, migration state, and a log file. 

--send-diagnostics

```yaml
send-diagnostics:
```

Enable or disable sending [diagnostics](/stable/yugabyte-voyager/reference/diagnostics-report/ "diagnostics") information to Yugabyte.  
Default: true  
Accepted parameters: true, false, yes, no, 0, 1 

-l, --log-level

```yaml
log-level:
```

Log level for yb-voyager.  
Accepted values: trace, debug, info, warn, error, fatal, panic  
Default: info 

--log-max-size-mb

```yaml
log-max-size-mb:
```

Maximum size in MB of a yb-voyager log file before it is rotated. Also applies to the Debezium log file during live migration.  
Default: 200 

--log-max-backups

```yaml
log-max-backups:
```

Maximum number of rotated log files to retain. Older files are deleted. Use -1 to retain all rotated log files.  
Default: 10 

--target-db-host

```yaml
target:
  db-host:
```

Domain name or IP address of the machine on which target database server is running.  
Default: "127.0.0.1" 

--target-db-name

```yaml
target:
  db-name:
```

Target database name.  
Default: yugabyte 

--target-db-password

```yaml
target:
  db-password:
```

Password to connect to the target YugabyteDB database. Alternatively, you can also specify the password by setting the environment variable `TARGET_DB_PASSWORD`. If you don't provide a password via the CLI during any migration phase, yb-voyager will prompt you at runtime for a password. If the password contains special characters that are interpreted by the shell (for example, # and $), enclose the password in single quotes. 

--target-db-port

```yaml
target:
  db-port:
```

Port number of the target database server.  
Default: 5433 

--target-db-schema

```yaml
target:
  db-schema:
```

Schema name of the target database. MySQL and Oracle migrations only. 

--target-db-user

```yaml
target:
  db-user:
```

Username of the target database. 

[--target-ssl-cert](/stable/yugabyte-voyager/reference/yb-voyager-cli/#yugabytedb-options "--target-ssl-cert")

```yaml
target:
  ssl-cert:
```

Path to a file containing the certificate which is part of the SSL `<cert,key>` pair. 

[--target-ssl-key](/stable/yugabyte-voyager/reference/yb-voyager-cli/#yugabytedb-options "--target-ssl-key")

```yaml
target:
  ssl-key:
```

Path to a file containing the key which is part of the SSL `<cert,key>` pair. 

[--target-ssl-crl](/stable/yugabyte-voyager/reference/yb-voyager-cli/#yugabytedb-options "--target-ssl-crl")

```yaml
target:
  ssl-crl:
```

Path to a file containing the SSL certificate revocation list (CRL). 

--target-ssl-mode

```yaml
target:
  ssl-mode:
```

Specify the SSL mode for the target database as one of `disable`, `allow`, `prefer` (default), `require`, `verify-ca`, or `verify-full`. 

[--target-ssl-root-cert](/stable/yugabyte-voyager/reference/yb-voyager-cli/#yugabytedb-options "--target-ssl-root-cert")

```yaml
target:
  ssl-root-cert:
```

Path to a file containing SSL certificate authority (CA) certificate(s). 

--start-clean — Starts a fresh import with data files present in the `data` directory.  
If the target YugabyteDB database has non-empty tables, you are prompted to continue the import without truncating those tables; if you go ahead without truncating, then yb-voyager starts ingesting the data present in the data files in upsert mode.  
**Note** that for cases where a table doesn't have a primary key, duplicate data may be inserted. You can avoid duplication by excluding the table using `--exclude-table-list`, or by truncating those tables manually before using the `start-clean` flag.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

-h, --help — Command line help. 

-y, --yes — Answer yes to all prompts during the export schema operation.  
Default: false 

-c, --config-file — Path to a [configuration file](/stable/yugabyte-voyager/reference/configuration-file "configuration file"). 

--run-guardrails-checks

```yaml
import-data:
  run-guardrails-checks:
```

Run guardrails checks during migration.  
Default: true  
Accepted values: true, false, yes, no, 0, 1  
**Note**: Setting this flag to false is unsafe, as it skips critical pre-migration validations (such as source/target database permissions, binary dependencies, and version compatibility) and may lead to migration failures or data issues. Leave the default (true) unless you have a specific reason to disable checks.

### Example

#### Offline migration

An example for offline migration is as follows:

Configuration file:

```yaml
yb-voyager import data --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager import data --export-dir /dir/export-dir \
        --target-db-host 127.0.0.1 \
        --target-db-user ybvoyager \
        --target-db-password 'password' \
        --target-db-name target_db \
        --target-db-schema target_schema \
        --parallel-jobs 12
```

#### Live migration

An example for all live migration scenarios is as follows:

Configuration file:

```yaml
yb-voyager import data to target --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager import data to target --export-dir /dir/export-dir \
        --target-db-host 127.0.0.1 \
        --target-db-user ybvoyager \
        --target-db-password 'password' \
        --target-db-name target_db \
        --target-db-schema target_schema \
        --parallel-jobs 12
```

## import data status

For offline migration, get the status report of an ongoing or completed data import operation. The report contains migration status of tables, number of rows or bytes imported, and percentage completion.

### Syntax

```text
Usage: yb-voyager import data status [ <arguments> ... ]
```

### Arguments

The following table lists the valid CLI flags and parameters for `import data status` command.

When run at the same time, flags take precedence over configuration flag settings.

CLI flag

Config file parameter Description 

-e, --export-dir

```yaml
export-dir:
```

Path to the export directory. This directory is a workspace used to keep the exported schema, data, state, and logs. 

-h, --help — Command line help. 

-y, --yes — Answer yes to all prompts during the import data operation.  
Default: false 

--output-format — Format for the status report.  
Accepted parameters:

- `json`: Generate a JSON format output file.
- `table` (Default): Output the report to the console.

-c, --config-file — Path to a [configuration file](/stable/yugabyte-voyager/reference/configuration-file "configuration file").

### Example

Configuration file:

```yaml
yb-voyager import data status --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager import data status --export-dir /dir/export-dir
```

## get data-migration-report

**Note** that this command is applicable for Live migrations only.

Provides a consolidated report of data migration per table among all the databases involved in the live migration. The report includes the number of rows exported, the number of rows imported, change events exported and imported (INSERTS, UPDATES, and DELETES), and the final row count on the database.

### Syntax

```text
Usage: yb-voyager get data-migration-report [ <arguments> ... ]
```

### Arguments

The following table lists the valid CLI flags and parameters for `get data-migration-report` command.

When run at the same time, flags take precedence over configuration flag settings.

CLI flag

Config file parameter Description 

-e, --export-dir

```yaml
export-dir:
```

Path to the export directory. This directory is a workspace used to store exported schema DDL files, export data files, migration state, and a log file. 

-l, --log-level

```yaml
log-level:
```

Log level for yb-voyager.  
Accepted values: trace, debug, info, warn, error, fatal, panic  
Default: info 

--log-max-size-mb

```yaml
log-max-size-mb:
```

Maximum size in MB of a yb-voyager log file before it is rotated. Also applies to the Debezium log file during live migration.  
Default: 200 

--log-max-backups

```yaml
log-max-backups:
```

Maximum number of rotated log files to retain. Older files are deleted. Use -1 to retain all rotated log files.  
Default: 10 

--source-db-password

```yaml
source:
  db-password:
```

Password to connect to the source database. If you don't provide a password via the CLI during any migration phase, yb-voyager will prompt you at runtime for a password. Alternatively, you can also specify the password by setting the environment variable `SOURCE_DB_PASSWORD`. If the password contains special characters that are interpreted by the shell (for example, # and $), enclose it in single quotes. 

--source-replica-db-password

```yaml
source-replica:
  db-password:
```

Password to connect to the source-replica database. Alternatively, you can also specify the password by setting the environment variable `SOURCE_REPLICA_DB_PASSWORD`. If the password contains special characters that are interpreted by the shell (for example, # and $), enclose it in single quotes. 

--target-db-password

```yaml
target:
  db-password:
```

Password to connect to the target YugabyteDB database. Alternatively, you can also specify the password by setting the environment variable `TARGET_DB_PASSWORD`. If you don't provide a password via the CLI during any migration phase, yb-voyager will prompt you at runtime for a password. If the password contains special characters that are interpreted by the shell (for example, # and $), enclose the password in single quotes. 

-h, --help — Command line help. 

--output-format — Format for the status report.  
Accepted parameters:

- `json`: Generate a JSON format output file.
- `table` (Default): Output the report to the console.

-c, --config-file — Path to a [configuration file](/stable/yugabyte-voyager/reference/configuration-file "configuration file").

### Example

Configuration file:

```yaml
yb-voyager get data-migration-report --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager get data-migration-report --export-dir /dir/export-dir
```

## import data to source

**Note** that this command is applicable for Live migrations only.

Imports data to the source database, and streams new changes from the YugabyteDB database to the source database.

### Syntax

```text
Usage: yb-voyager import data to source [ <arguments> ... ]
```

### Arguments

The following table lists the valid CLI flags and parameters for `import data to source` command.

When run at the same time, flags take precedence over configuration flag settings.

CLI flag

Config file parameter Description 

--parallel-jobs

```yaml
import-data-to-source:
  parallel-jobs:
```

Number of parallel jobs to use while importing data.  
Default: 16(Oracle) 

--max-retries-streaming

```yaml
import-data-to-source:
  max-retries-streaming:
```

Maximum number of retries for failed event batch during live migration.  
Default: 15 

--use-partition-root

```yaml
import-data-to-source:
  use-partition-root:
```

For partitioned tables during live migration, controls whether CDC data is imported via the root table or child partitions only:

- `true` (default): Import CDC data only via the root table.
- `false`: Import CDC data only via child partitions.

Default: true  
Accepted values: true, false, yes, no, 0, 1 

-e, --export-dir

```yaml
export-dir:
```

Path to the export directory. This directory is a workspace used to store exported schema DDL files, export data files, migration state, and a log file. 

--send-diagnostics

```yaml
send-diagnostics:
```

Enable or disable sending [diagnostics](/stable/yugabyte-voyager/reference/diagnostics-report/ "diagnostics") information to Yugabyte.  
Default: true  
Accepted parameters: true, false, yes, no, 0, 1 

-l, --log-level

```yaml
log-level:
```

Log level for yb-voyager.  
Accepted values: trace, debug, info, warn, error, fatal, panic  
Default: info 

--log-max-size-mb

```yaml
log-max-size-mb:
```

Maximum size in MB of a yb-voyager log file before it is rotated. Also applies to the Debezium log file during live migration.  
Default: 200 

--log-max-backups

```yaml
log-max-backups:
```

Maximum number of rotated log files to retain. Older files are deleted. Use -1 to retain all rotated log files.  
Default: 10 

--source-db-password

```yaml
source:
  db-password:
```

Password to connect to the source database. 

-h, --help — Command line help for import data to source. 

--start-clean — Starts a fresh import with exported data files present in the export-dir/data directory.  
If any table on YugabyteDB database is non-empty, it prompts whether you want to continue the import without truncating those tables.  
Note that for the cases where a table doesn't have a primary key, this may lead to insertion of duplicate data. To avoid this, exclude the table using the --exclude-file-list or truncate those tables manually before using the start-clean flag.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

-y, --yes — Answer yes to all prompts during the migration.  
Default: false 

-c, --config-file — Path to a [configuration file](/stable/yugabyte-voyager/reference/configuration-file "configuration file"). 

--run-guardrails-checks

```yaml
import-data-to-source:
  run-guardrails-checks:
```

Run guardrails checks during migration.  
Default: true  
Accepted values: true, false, yes, no, 0, 1  
**Note**: Setting this flag to false is unsafe, as it skips critical pre-migration validations (such as source/target database permissions, binary dependencies, and version compatibility) and may lead to migration failures or data issues. Leave the default (true) unless you have a specific reason to disable checks.

### Example

Configuration file:

```yaml
yb-voyager import data to source --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager import data to source --export-dir /dir/export-dir \
        --source-db-password 'password'
```

## import data to source-replica

**Note** that this command is applicable for Live migrations only.

Imports data to the source-replica database, and streams new changes from the YugabyteDB database to the source-replica database.

### Syntax

```text
Usage: yb-voyager import data to source-replica [ <arguments> ... ]
```

### Arguments

The following table lists the valid CLI flags and parameters for `import data to source-replica` command.

When run at the same time, flags take precedence over configuration flag settings.

CLI flag

Config file parameter Description 

--batch-size

```yaml
import-data-to-source-replica:
  batch-size:
```

Size of batches in the number of rows generated for ingestion when you import data to source-replica database.  
Default: 10000000 (Oracle) or 100000 (PostgreSQL) 

--disable-pb

```yaml
import-data-to-source-replica:
  disable-pb:
```

Use this argument to disable progress bar or statistics during data import.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

--parallel-jobs

```yaml
import-data-to-source-replica:
  parallel-jobs:
```

The number of parallel batches issued to the source-replica database.  
Default: 16 (Oracle); or, if yb-voyager can determine the total number of cores N, then N/2, otherwise 8 (PostgreSQL) 

--truncate-tables

```yaml
import-data-to-source-replica:
  truncate-tables:
```

Truncate tables on target YugabyteDB database before importing data. This option is only valid if `--start-clean` is set to true.  
Default: false 

--max-retries-streaming

```yaml
import-data-to-source-replica:
  max-retries-streaming:
```

Maximum number of retries for failed event batch during live migration.  
Default: 15 

-e, --export-dir

```yaml
export-dir:
```

Path to the export directory. This directory is a workspace used to store exported schema DDL files, export data files, migration state, and a log file. 

--send-diagnostics

```yaml
send-diagnostics:
```

Enable or disable sending [diagnostics](/stable/yugabyte-voyager/reference/diagnostics-report/ "diagnostics") information to Yugabyte.  
Default: true  
Accepted parameters: true, false, yes, no, 0, 1 

-l, --log-level

```yaml
log-level:
```

Log level for yb-voyager.  
Accepted values: trace, debug, info, warn, error, fatal, panic  
Default: info 

--log-max-size-mb

```yaml
log-max-size-mb:
```

Maximum size in MB of a yb-voyager log file before it is rotated. Also applies to the Debezium log file during live migration.  
Default: 200 

--log-max-backups

```yaml
log-max-backups:
```

Maximum number of rotated log files to retain. Older files are deleted. Use -1 to retain all rotated log files.  
Default: 10 

--source-replica-db-host

```yaml
source-replica:
  db-host:
```

Domain name or IP address of the machine on which source-replica database server is running.  
Default: 127.0.0.1 

--source-replica-db-name

```yaml
source-replica:
  db-name:
```

Name of the database in the source-replica database on which import needs to be done. 

--source-replica-db-password

```yaml
source-replica:
  db-password:
```

Password to connect to the source-replica database. Alternatively, you can also specify the password by setting the environment variable `SOURCE_REPLICA_DB_PASSWORD`. If you don't provide a password via the CLI or environment variable during any migration phase, yb-voyager will prompt you at runtime for a password. If the password contains special characters that are interpreted by the shell (for example, # and $), enclose the password in single quotes. 

--source-replica-db-port

```yaml
source-replica:
  db-port:
```

Port number of the source-replica database server.  
Default: 1521 (Oracle) 

--source-replica-db-schema

```yaml
source-replica:
  db-schema:
```

Schema name of the source-replica database. 

--source-replica-db-sid

```yaml
source-replica:
  db-sid:
```

Oracle System Identifier (SID) that you wish to use while importing data to Oracle instances. Oracle migrations only. 

--source-replica-db-user

```yaml
source-replica:
  db-user:
```

Username to connect to the source-replica database. 

--source-replica-ssl-cert

```yaml
source-replica:
  ssl-cert:
```

Source-replica database SSL Certificate path. 

--source-replica-ssl-crl

```yaml
source-replica:
  ssl-crl:
```

Source-replica database SSL Root Certificate Revocation List (CRL). 

--source-replica-ssl-key

```yaml
source-replica:
  ssl-key:
```

Source-replica database SSL key path. 

--source-replica-ssl-mode

```yaml
source-replica:
  ssl-mode:
```

One of `disable`, `allow`, `prefer`(default), `require`, `verify-ca`, or `verify-full`. 

--source-replica-ssl-root-cert

```yaml
source-replica:
  ssl-root-cert:
```

Source-replica database SSL Root Certificate path. 

--oracle-home

```yaml
source-replica:
  oracle-home:
```

Path to set $ORACLE\_HOME environment variable. `tnsnames.ora` is found in `$ORACLE_HOME/network/admin`. Oracle migrations only. 

[--oracle-tns-alias](/stable/yugabyte-voyager/reference/yb-voyager-cli/#ssl-connectivity "--oracle-tns-alias")

```yaml
source-replica:
  oracle-tns-alias:
```

TNS (Transparent Network Substrate) alias configured to establish a secure connection with the server. Oracle migrations only. 

--start-clean — Starts a fresh import with data files present in the `data` directory.  
If the target YugabyteDB database has any non-empty tables, you are prompted to continue the import without truncating those tables; if you proceed without truncating, then yb-voyager starts ingesting the data present in the data files in non-upsert mode.  
**Note** that for cases where a table doesn't have a primary key, duplicate data may be inserted. You can avoid duplication by excluding the table using `--exclude-table-list`, or by truncating those tables manually before using the `start-clean` flag.  
Default: false  
Accepted parameters: true, false, yes, no, 0, 1 

-h, --help — Command line help for import data to source-replica. 

-y, --yes — Answer yes to all prompts during the migration.  
Default: false 

-c, --config-file — Path to a [configuration file](/stable/yugabyte-voyager/reference/configuration-file "configuration file").

### Example

Configuration file:

```yaml
yb-voyager import data to source-replica --config-file <path-to-config-file>
```

CLI:

```sh
yb-voyager import data to source-replica --export-dir /dir/export-dir \
        --source-replica-db-host 127.0.0.1 \
        --source-replica-db-user ybvoyager \
        --source-replica-db-password 'password' \
        --source-replica-db-name source_replica_db \
        --source-replica-db-schema source_replica_schema \
        --parallel-jobs 12
```