Define the job before choosing the tool
"Export the GP data" can mean four very different things:
- 01A business user needs a customer or transaction list in Excel.
- 02An analyst needs joined data for a one-time question.
- 03A migration team needs repeatable source files with control totals.
- 04The company needs all required history to remain usable after GP and SQL Server are retired.
One export method rarely handles all four well.
SmartList and Excel
SmartList is usually the best first choice for a familiar operational list while GP remains live. Users can select columns, apply restrictions and export to Excel without writing SQL.
Its limitations appear when the question crosses modules, requires record notes or must be repeated after GP is gone. Large results can also become slow or awkward, and a folder of independent spreadsheets does not prove that all required tables were preserved.
SQL queries and database views
Direct SQL gives a skilled analyst control over joins, filters and volume. It is appropriate for defined migration extracts and complex analysis when the query has been reviewed.
Dynamics GP stores business concepts across work, open and history tables. Character fields are often padded, date sentinels need handling, document type codes need labels, and originating versus functional currency amounts must remain distinct. A query that returns rows can still omit part of the business record.
Integration Manager, eConnect and migration tools
These tools are designed around moving data into or between operational systems. They can be useful for destination loading and supported business objects. They do not automatically create a permanent, easy-to-query historical environment, and they should not be evaluated as though loading and archiving were the same job.
Consultant CSV extraction
A consultant can export selected tables or entities into CSV files. CSV is portable and easy to inspect. It loses database relationships, data types, indexes and a consistent query interface unless those are rebuilt elsewhere.
Ask for a manifest containing source table, filters, extraction time, row count, file checksum and control totals. Without it, future users cannot tell whether a file is complete or how it was produced.
Purpose-built archive export
A complete archive copies the agreed scope into a documented database, adds human labels and relationships, indexes searchable fields, and compares the result with the source. Users can then create smaller CSV, XLSX and PDF outputs whenever a specific need arises.
ERPDataArchive supports two export levels:
- Standard migration extracts: choose fields, filters and date ranges; preview counts and totals; export typed CSV/XLSX plus a manifest.
- Target-specific mapping package: apply named destination fields and agreed transformations, starting with Business Central. This is an add-on because mapping is project-specific.
Export checklist
- ✓Identify every company, module and third-party table in scope.
- ✓State whether work, open and history records are included.
- ✓Preserve original and functional currency amounts separately.
- ✓Keep source keys and provenance alongside friendly fields.
- ✓Use real dates and numeric cell types in XLSX output.
- ✓Record the filters and query used to produce each extract.
- ✓Include row counts, totals and checksums in a manifest.
- ✓Test that another person can answer the intended question from the output.