Migration Results

Migration Completed Successfully!

Duration

00:07:48

Tables Completed

13 / 13

Rows Copied

86

Errors

0

Table Results
Table Name Source Rows Rows Copied Rows Skipped Errors Duration Status
tblfeatureraces 0 0 0 0 00:00:29 Success
tblmeetings 0 0 0 0 00:00:29 Success
tblraces 1 1 0 0 00:00:38 Success
tblruns 10 10 0 0 00:01:27 Success
tblprerace_meetings 0 0 0 0 00:00:29 Success
tblprerace_races 0 0 0 0 00:00:35 Success
tblprerace_runners 0 0 0 0 00:01:15 Success
tbltsales_company 0 0 0 0 00:00:07 Success
tbltsales 0 0 0 0 00:00:08 Success
tbltsales_sessions 0 0 0 0 00:00:07 Success
tbltsales_lots 0 0 0 0 00:00:44 Success
tblstewards 0 0 0 0 00:00:40 Success
tbldividends 75 75 0 0 00:00:33 Success
Sync ID Mappings to Destination MySQL

Copies all ID mappings already stored in the local SQLite database into config_tables and config_id_mappings in the destination MySQL database. Use this if data was migrated before this feature was added, or after a partial run. Duplicate rows are silently skipped — safe to run multiple times.

Reset Migration History
Caution: Clearing history lets the next run re-copy those rows. If they already exist in the destination this will create duplicates. Only do this if you have already deleted the rows from the destination first.
Backfill NULL Foreign Keys Review Pending Mappings
Step 1 Find Matches for Manually-Added Records

If a parent record (e.g. a horse or meeting) was manually added to the destination database instead of being copied by this tool, it has no ID mapping. This scan uses the natural key columns you configured in the Field Mapping step to find it by business identity (e.g. meeting date + course + country + discipline). Matches are shown for your review — nothing is saved until you confirm each one.

Review & Confirm Matches
Step 2 Run Backfill

After confirming your ID mappings (Step 1), run backfill to fill in the NULL FK columns with the correct destination IDs. Only rows where the FK is still NULL are updated.

Parent ID mappings are searched across all migration sessions and all confirmed manual mappings. If the parent was migrated by the tool in any previous session, it will be found automatically — Step 1 is only needed for records added directly to the destination DB.

Repair Boolean Columns

Rows migrated before the boolean-conversion fix have tinyint(1) flag columns (e.g. is_jump, tab_status, is_checked) stuck at 0, because the source 'TRUE'/'FALSE' string was written directly into a numeric column and silently cast to 0 by MySQL. This re-reads the correct value from the source row (via this session's field mappings and ID mappings) and overwrites the destination column — including rows that are already (correctly) 0.

New Migration FK Patch Tool Home