Run, Save, and Automate DBConvert Jobs

Use this guide once source and target connections are ready.

Visual of a DBConvert job workflow from configuration and review to run, save, and schedule

What each table copies

Choose the tables on Tables & mapping. New tables in the source: Include / Skip decides whether later runs include tables added to the source. Include takes all tables except those you untick; Skip keeps only your saved selection.

Table defaults sets what every selected table copies: its structure, its rows, its indexes and its foreign keys.

If target table exists decides what happens to a table that is already in the destination: drop and recreate it, empty it first, or add the rows to it. The list on the left shows each table as a new table or as one that replaces an existing table.

Match source updates existing destination tables to the source: column types, indexes, foreign keys. Server destinations add their own options, such as the MySQL engine and character set.

Supported CHECK constraints and Access validation rules are transferred with table structure. Review the log for rules that were omitted or that existing rows violate. See Validation rules.

A setting changed on one table wins over the default. More in Table options.

The Table defaults panel: what each table copies, what happens to an existing table, and the MySQL table options

Names and types for all tables

Naming rules writes every destination name the same way: its case, characters to replace, a prefix or a suffix. The list on the left shows the names as they will be.

Type mapping lists every source type in the job, how many columns have it, and the destination type it becomes. Change a type here and it changes in every table.

A type set on one column wins over Type mapping. More in Job options.

The Type mapping panel: each source type with its column count and the destination type it becomes

Warnings before the run

The line under the table list checks every selected table against the destination. It names the table and the column that would fail or lose data, before anything runs.

A column the check flags carries a mark. Lossy: the destination type cannot hold every value, for example a time zone offset. Reserved: the name is a reserved word in the destination.

Fix it by changing the column's type or name, or leave it if the loss is acceptable. The list of warnings is in Pre-migration checks.

Run again, and on a schedule

For SQL Server, PostgreSQL and Oracle sources, Setup can select several schemas in one job. See Source schemas and destination layout.

A job saves itself as you work. Jobs in the left rail lists them; open one and run it again.

Select a job and expand Job file to see the file a run uses, read-only, with Copy. See Where jobs are stored.

On Execution, review the connections, selected tables and destination actions, then start the run. Starting or scheduling checks the tables again; fix blocking issues before continuing.

The operation log groups table messages separately from the run's closing result. Tick Technical details for diagnostic messages. The log has one scroll area. Large-table progress shows rows written, transfer speed and estimated time remaining.

The result shows whether the run completed, completed with warnings, finished with errors, failed or was cancelled. Review skipped objects, failed tables and rejected rows before using the destination. Starting another run clears the previous result.

Schedule… on Execution runs the job daily, weekly or monthly in the background. It runs with the app closed, as long as you are logged in to Windows.

A run that drops or changes destination data says so in orange on Execution before you start it.

To run a job from a script, see Command-line mode.

The Schedule dialog: how often the job runs and when it starts

Continue with the reference docs or start the tool

The screens here are the 2026 interface. If your converter predates it, the guide for the previous interface is still up.