.NET
.NET integration experience in VAST includes a Windows application that reads a restored QuickBooks company-file copy through QBSDK. The exporter supplies source material for the ongoing migration.
Where the engineering matters
A migration adapter needs a clear boundary around the system it reads. The exporter is read-only and bound to the intended source copy, with provenance supporting subsequent identity mappings and reconciliation.
Work represented in the portfolio
- Windows-based QuickBooks extraction tooling
- QBSDK integration with a restored company-file copy
- Read-only source access and provenance
- Exported inputs for staged destination processing
This is a specific integration-runtime contribution within VAST, not a claim that the entire migration is a single .NET application. The larger VAST case study explains imports, CRM relationships, and the remaining reconciliation work.
.NET integration experience: planning a similar project
The runtime choice follows the integration boundary. In VAST, a Windows application communicates with a restored QuickBooks company-file copy and produces inputs for later processing. That is the .NET contribution documented here. For a comparable project, clarify the required desktop environment and intended source before estimating the adapter; destination imports and reconciliation are separate parts of the migration.
For a new project or changes to an existing system, explore custom API integration services.