Reusable Legal Data Migration Tool

@WOFZahid

About the onsite rule: the build itself doesn't need your real client data. I'd build and test it remotely against a trial install of the competitor app with dummy matters. Then your team runs the exe in the Sydney office using the guide. No client file leaves your building. I'd look at the app's local data store first. Most of these apps keep matters in a local SQL Server, SQL CE or Access database, with documents in matter folders on disk. Reading those directly is faster and more accurate than clicking through screens. At 1,000 matters with up to 1,000 docs each, UI scraping alone would take days per run. So I'd use FlaUI only for fields that exist on screen and nowhere else. I've done this before. I rescued a legacy Windows app whose vendor had vanished. I decompiled the binary, mapped its SQL Server Compact database and moved all the data to SQLite, then to a central database. Stack: C# on .NET 8, FlaUI, CsvHelper, MsgReader for emails and Serilog for the log. You get three CSVs (clients, matters, document manifest) linked by ID, plus the document folder. Each run writes to a new dated folder, so nothing is overwritten unless you allow it. Turnaround is 3 daysk once I have the app installed with dummy data. Which app is it, and are the matter folders stored locally or on a network share?

@arturg6

Hello, Artur G , .NET and Windows data-processing developer from Warsaw, Poland. "three distinct data sets" - you need a repeatable migration utility that extracts customers, transactions and linked documents while preserving relationships and producing import-ready manifests. I can build the Windows utility in C#/.NET with structured extraction, CSV generation, document copying, duplicate-safe reruns, logging and validation. For up to 1,000 matters and potentially hundreds of documents per matter, I would use a staged extraction pipeline so a single inaccessible record does not stop the migration. The output can maintain stable IDs and document paths for SILQ import. I would first map the competitor application's accessible UI/export/local artefacts on a controlled test machine, then build the reusable extractor around the confirmed access method. Full source code, build instructions and a dummy-data validation run can be included. Can you provide remote access to a test Windows machine running the competitor application, or is physical Sydney attendance mandatory? Looking forward to working with you.

@corpmember29

Hello, CLOSED WINDOWS APP DATA EXTRACTION + MIGRATION — I CAN BUILD A RE-RUNNABLE WINDOWS TOOL THAT EXTRACTS CUSTOMERS, TRANSACTIONS AND DOCUMENTS WHILE PRESERVING ALL RELATIONSHIPS. I went through your requirements and understand the tool must work only through the authorised desktop application/environment, without source-code or backend access. I have 12 years of development experience and can build this as a portable Windows utility using C#/.NET with UI automation and file-system/data-store inspection where legitimately accessible. My approach: • Automate authorised login and navigation through the desktop application • Extract all available customer and matter fields into structured CSV • Maintain customer/matter/transaction relationships and unique references • Capture linked DOC/DOCX/PDF/email and other attachments with original paths/names • Generate a document manifest linking every file to its customer/matter • Handle 1,000+ matters and large document volumes with resumable processing • Add duplicate protection so reruns do not overwrite existing exports • Detailed success/skipped/error logs for every record and document • Provide dummy-data sample exports, source code, build instructions and user guide I can first validate the application’s accessible UI/data stores onsite in Sydney and then finalize the extraction method based on what is legitimately exposed by the installed client Thanks, Christina

@longngoc2307

Hi, there. "REUSABLE LEGAL DATA MIGRATION TOOL" - you need a Windows utility that can reliably extract clients, matters, transactions and related documents from a closed desktop application while preserving relationships for SILQ import. I can build this in C#/.NET as a reusable Windows tool around the authorised application session, using UI automation and accessible local/export artefacts where available rather than depending on source-code or backend access. The extraction layer would normalize customer and matter relationships, collect document files into controlled folders, generate CSV manifests, prevent accidental overwrites, and provide detailed logging for captured, skipped and failed records. I would also structure the tool so the same workflow can be rerun for future migrations and provide the executable, source, build instructions, sample outputs and user guide. Given the sensitive data, I can work within the agreed onsite Sydney environment and authorised access only. Can you provide the competitor application name/version and a test machine with dummy data for the initial extraction assessment? Looking forward to working with you.

@Georgeoustar

Hi there! I understand your core need is a reliable, reusable Windows tool for onsite extraction of customer, transaction, and document data from a closed competitor’s desktop application—preserving data relationships for smooth migration into SILQ. My background in .NET/C# desktop automation, data extraction, and reverse-engineering uniquely positions me for this challenge. I’ll leverage robust libraries such as FlaUI or UIAutomation for interface-driven data extraction, with SharpZipLib and CsvHelper for handling file and CSV outputs. The tool will maintain referential integrity between clients, matters, and documents, with manifest files and comprehensive logging for full transparency. The portable executable will support re-runs without overwriting unless authorized, and the process will be fully documented for your team. Having tackled similar closed-system migrations, I’m confident in delivering a secure, auditable solution that meets your requirements. For clarity: Are there any specific security or audit requirements during the onsite extraction? Do you already know which file formats or subfolder structures are most commonly used by the competitor’s application? Best Regards, George

@gopisoft

Hi, I need to understand the app from where the data is required to be extracted. Happy to meet you at your CBD office if that helps to understand the app and underlying tech. I have over 20 years of experience with data projects and initiatives and will be able to create the required application in a quick time. Thanks, looking forward to hear from your side.

@TechWagger2026

Hello, This is a strong fit for a controlled Windows migration utility where the priority is accurate extraction, preserved relationships, document integrity, and repeatable runs rather than simply scraping what is visible on screen. I would approach this by first profiling the competitor application in the authorised onsite environment to determine the most reliable accessible source: UI automation, built-in exports, local databases/files, or a combination. The extraction layer would capture customers, transactions/matters, and associated documents while maintaining stable IDs and relationships between records and document paths. For the document migration, I would build a manifest-driven process that preserves filenames and source relationships, supports DOC/DOCX, PDF, email and other available formats, and handles large matter volumes without loading everything into memory. The tool would include validation, duplicate-safe reruns, structured logging, skipped/error reporting, and a clear output structure ready for SILQ import. **Software expertise:** Python, Windows desktop automation, SQL/local data stores, CSV processing, filesystem/document extraction, logging, validation, portable executables and migration tooling. Regards, Arun

@jonasdedzo

Hello, I can build a reusable C#/.NET Windows migration utility for authorised extraction from the competitor desktop application, with all sensitive processing performed onsite in your Sydney office. I’ll map the available UI/export/local artefacts and create a controlled workflow for customers, matters/transactions, and associated documents. CSV outputs will preserve relationships through stable IDs, while documents are stored in a structured folder with a complete manifest. The tool will support up to 1,000 matters and high document volumes, with validation, detailed logging, error handling, duplicate/re-run protection, and explicit overwrite controls. You’ll receive a portable Windows executable, full source code, build instructions, user guide, and dummy-data sample exports demonstrating the required structure. I’ll keep the architecture reusable for future SILQ migrations. Budget: 6,850 AUD | Timeline: 12 days Milestones — 6,850 AUD / 12 days M1 — 2,000 AUD / 3 days: Application assessment, data mapping and extraction prototype. M2 — 3,000 AUD / 6 days: Customer/matter/transaction extraction, documents, CSV/manifest, logging and re-run protection. M3 — 1,850 AUD / 3 days: Validation, SILQ-ready testing, executable, documentation and handover.

@rockfortglobal

Hi My name is Param Ramanan form Rockfort Global based out of Adelaide. I am submitting a "placeholder bid" as we need a lot quest questions answered. Please google the name of our company or my name for more information. I request you to please connect with on the freelancer chat so we can discuss your needs further. Kind Regards Param Ramanan