Tool 2
Project Tools
The working environment for delivery: where the migration is run, extraction rules are built, loads are generated and documentation comes out finished. It covers everything from reading the source database to handing over the files with their validation alongside.
Automatic source tracing
The tool walks the load rules and traces, field by field, where each value came from — descending through subqueries, aliases and intermediate tables to the source or to the mapping filled in during the project. It becomes one document per project: the migration data dictionary, delivered to the client.
Visual rule building
An editor with boxes and links built by dragging column onto column, choosing the join type and descending into subqueries; a grid defines the output, with aliases, filters, grouping and ordering. Anyone who prefers to write it out can — and both sides stay in sync.
Test before writing
The rule runs and shows its result before being applied to the client’s database. Finding out it was wrong after running it is exactly the rework the tool exists to prevent.
Validation that comes with it
Every dataset generated comes with its matching reconciliation worksheet, with formulas and automatic refresh. It is not possible to generate the load without generating its proof.
Blockers that do not get lost
Whatever was flagged as blocking a record comes back flagged in the regenerated worksheets. Nobody re-checks from scratch on every round.
Destructive actions with measured impact
Before deleting or recreating anything, the tool states the size of the possible damage. Confirming blind is not an option.
Long jobs do not freeze the screen
Heavy generation runs in the background, with visible progress and the option to cancel. The screen is never left mute and waiting.
Any readable source
If the data can be obtained, it can be migrated — through database access, export, text file or spreadsheet. When it does not arrive as a database, the tool itself builds the structure and loads the data before the migration begins.
What is learned on one source stays for the next
The extraction rules built for a source system are kept as that system’s library, not the client’s: every project feeds the set and improves the next one using the same source. That is how knowledge accumulates by design, without depending on someone remembering what was done last time.