EGKits Legacy Migrator
Enterprise Data Migration Platform
Securely migrate item codes, sent invoices, received invoices, and receipts from a legacy EGEInvoicing SQL Server database into an EGKits tenant (direct database or Secure Migration API).
At a glance
Publisher: IDSYSEG / EGKits
Windows 10 / Windows 11
MSI
.NET runtime included (self-contained)
What this tool does
Securely migrate item codes, sent invoices, received invoices, and receipts from a legacy EGEInvoicing SQL Server database into an EGKits tenant (direct database or Secure Migration API).
Compatibility
.NET runtime included (self-contained)
Key features
Direct database or Secure Migration API target modes
Dry-run validation before writing
Organisation mapping with registration-number and name suggestions
Resumable batch migration with per-batch transactions
Automatic reconciliation of document counts and totals
Quarantine reporting for rejected documents
Profiles, logs, and reports under AppData
System requirements
Windows 10 or later (x64)
Access to the legacy EGEInvoicing SQL Server database
EGKits tenant database connection or Secure Migration API credentials
Network connectivity to source and target systems
Installation
Before you install
Confirm you have SQL connectivity to the legacy database and the EGKits target (or API endpoint).
Identify the EGKits tenant identifier that must be stamped on migrated rows.
Plan a dry-run window before any production cutover.
Install
Download the official MSI from this page.
Run msiexec /i EGKitsLegacyMigrator.msi (or double-click the MSI).
Launch EGKits Migration Platform from the Start Menu.
After install
Open the app and create a connection profile for legacy and target databases.
Use Test connection / Test target before mapping.
Profiles and logs are stored under %APPDATA%\EGKits\LegacyMigrator.
Configuration
Load tenants from the platform registry database or paste a direct target connection string.
Map legacy organisation ids to EGKits CompanyCodes / Branches.
Review Options (placeholder catalogue rows, orphaned line-tax attachment) before a production run.
Troubleshooting
If a profile was copied from another PC, re-enter passwords (DPAPI is machine/user bound).
Unmapped organisations block documents — complete Mapping and re-run preflight.
Use Dry run and the failure report to fix data issues before a live Start.