Reusable Legal Data Migration Tool

I need a robust Windows-based utility that can pull three distinct data sets—Customer information, Transaction records, and all related Documents and attachments—from a competitor’s desktop application. I have no access to their source code or backend, so the tool will have to work purely through the installed client (for example, by reading local data stores, export functions, or other accessible artefacts). =========================================== Security Due to the sensitive nature of the client data being extracted this needs to be done onsite in our Sydney NSW CBD office. =========================================== Core requirements Automate extraction from a competitor’s Windows desktop application through an authorised user-interface login, without source-code or backend access. Export client and matter data in CSV or a similar reusable format. Export matter data including matter number, description and linked client information. Export client details including name, address and phone number. Export associated documents from matter subfolders, including DOCX, DOC, PDF, email and other file formats. Handle typical migrations of up to 1,000 matters, with approximately 5 to 1,000 documents per matter. Make the capability suitable to rerun for subsequent customer migrations into SILQ. Technical expectations The output must keep relationships intact (e.g., customer IDs linking to their transactions and document paths). Documents themselves should be saved to a designated folder with a CSV manifest referencing each file. Error handling and logging are essential so I can see exactly what was pulled or skipped. Deliverables 1. Final Windows capable executable (no installer required if a portable app is easier). Doesn't need to be Win32 just needs to be able to run on a Windows computer. 2. Full source code with concise build instructions. 3. A step-by-step user guide that shows how to run the tool and interpret the logs/output. 4. Sample exports generated from dummy data, demonstrating correct CSV structure and document capture. Acceptance criteria • Running the tool on a test machine produces three CSVs (customers, transactions, document-manifest) and a folder of extracted documents. • All fields present in the competitor app’s UI are captured accurately. • Re-running the tool does not overwrite existing exports unless I explicitly allow it. • No manual tweaking is required before the data is ready for SILQ import. If you’ve tackled reverse-engineering, Windows desktop automation, or data scraping from closed systems, this should feel familiar. Let me know any SDKs or libraries you plan to use and your estimated turnaround, and we can get started.