Start with the required outcome
A cheap option becomes expensive when every audit request turns into a restore project. Write down the expected service before comparing quotes:
- Which companies, modules, years and custom tables must be retained?
- Who needs access, and do they know Dynamics GP?
- Do users need search, filtered queries, documents or only raw records?
- Which totals must reconcile before decommissioning?
- How often will auditors, tax teams and customer service ask for history?
- Does the company want recurring hosting, or a file it owns?
Cost categories by approach
ERPDataArchive pricing
Each tier includes two extraction runs within 12 months, reconciliation, permanent reader and export access for the included modules, 12 months of email support and the contractual 30-day refund terms. Standard filtered CSV and XLSX exports are included. Destination-specific ERP mappings are optional.
A five-year worksheet
Use actual supplier and internal labor numbers. For each option, total:
- 01Initial discovery, extraction, mapping and verification.
- 02Five years of infrastructure, licenses, backups and monitoring.
- 03Annual access/support charges.
- 04Expected hours per audit, tax request and customer dispute.
- 05Recovery testing and incident response.
- 06Exit cost if the chosen vendor or format must be replaced.
Do not assign internal labor a value of zero. A controller waiting two days for an MSP to restore a database during an audit is a real operating cost even if no separate invoice arrives.
Questions that expose hidden charges
- ✓Is reading still possible after subscription or support ends?
- ✓Are all companies and modules included?
- ✓How are unknown custom tables handled?
- ✓Are test and final extraction runs both included?
- ✓Does the quote include reconciliation or only row export?
- ✓Are CSV, XLSX, PDF, batch documents and audit packages extra?
- ✓Can the customer query the data with external tools?
- ✓Who pays to export everything if the vendor relationship ends?