Last Updated: July 2026
Key Takeaways
The following covers what Microsoft Dynamics GP users need to know about using GP Integration Manager to move data from external sources into Dynamics GP efficiently:
- GP Integration Manager is a tool built into Microsoft Dynamics GP that moves data from external sources, such as spreadsheets or ODBC-connected databases, into GP without custom programming
- An integration is built from three components: a source (where the data comes from), a destination (the GP module receiving the data), and field mappings (which source columns connect to which GP fields)
- Integration Manager uses either an ODBC connection or a text/CSV file as its source; the source data must be clean and formatted correctly before the integration runs
- Transactions with header and line-level data, such as journal entries or purchase orders, require two coordinated queries with a defined relationship between them
- Errors are written to an exception log after each run; reviewing that log is the most important step after any import
If your team is copying data out of a spreadsheet and manually keying it into Microsoft Dynamics GP, there is a better path. GP Integration Manager is a tool built into Dynamics GP that lets you define how external data maps to GP fields, then run that import on demand. It handles the repetitive work. Your team reviews the results.
This is a practical walkthrough of how GP Integration Manager works, how to set up your first integration, and what to watch for when something doesn’t import the way you expected.
What Is GP Integration Manager and What Can It Do?
GP Integration Manager handles both master records and transactions. Master records include customers, vendors, items, and accounts. For transactions, you can import journal entries, payables invoices, receivables transactions, purchase orders, inventory adjustments, and more depending on which Integration Manager package your organization is licensed for.
How Do You Set Up a Source in GP Integration Manager?
Every integration in GP Integration Manager starts with a source, which is where the data lives before it comes into GP. Integration Manager supports two primary source types: text files (comma-delimited or tab-delimited) and ODBC data sources.
For most users, a CSV file is the easiest starting point. You export data from your external system, save it as a CSV, and point Integration Manager to that file. The file needs a header row with column names, and the data needs to be clean before you import it. Dates must be formatted consistently. Required fields cannot be blank. Numeric fields cannot contain text characters.
If you’re pulling from a database or a system that supports ODBC connections, such as Excel with an ODBC driver or a SQL Server database, you can connect Integration Manager directly to that source. This approach is more powerful for ongoing imports because the source data stays live and you don’t have to manually export a file each time.
Once you’ve defined your source, Integration Manager lets you preview the data before you map anything. Do NOT skip this step – it’s easier to catch formatting problems before you run the integration than to chase them through an error log after the fact.
How Do You Map Fields from Your Source to Dynamics GP Destinations?
Once you define your source, then you add a destination. The destination is the GP module you’re importing into. In the Integration Manager window, you click Add Dest, expand the Microsoft Dynamics GP eConnect node, and select the appropriate module such as Payables Transaction Entry, GL Transaction, or Item Master.
Once the destination is added, you open the field mapping window. This is where you connect each column in your source data to the corresponding field in GP. Some fields are required, meaning the integration will fail without them. GP Integration Manager flags required fields, so you can see immediately which ones you need to account for.
For fields where the value is always the same, such as a batch ID or a document type, you can use a constant instead of mapping from the source. This is useful for keeping your source file clean and letting Integration Manager handle the static values.
Important Note: If you’re importing something that has a header and line items, such as a purchase order with multiple line entries, you need to set up two separate queries. One query handles the header-level data. The second handles the line-level data. You then define a relationship between the two queries using a shared key field, typically a document number or reference ID. Integration Manager uses that relationship to group the right lines under the right header during the import.
How Do You Run an Integration in Dynamics GP Integration Manager?
Once your source and destination are configured and your fields are mapped, you’re ready to run the integration. In the Integration Manager window, select your integration from the list and click Run. Integration Manager will prompt you to confirm and then begin processing records.
As it runs, Integration Manager processes each record from your source and attempts to create or update the corresponding GP record. Records that pass validation are imported. Records that fail, due to a missing required field, a duplicate key, or a data type mismatch, are written to an exceptions log.
When the run completes, review the exceptions log before you assume the import is finished. The log tells you exactly which records failed and why. Most errors fall into a small number of categories: a required field that was blank in the source, a value that doesn’t match GP’s expected format, or a duplicate record that already exists in the system. Fixing the source data and re-running the integration for the failed records is usually straightforward once you know what went wrong.
After a successful import, it’s good practice to verify the results directly in GP. Pull up a few imported records, confirm the values look right, and check that the batch posted correctly if you were importing transactions.
What Are the Most Common GP Integration Manager Errors and How Do You Fix Them?
We see the most Integration Manager errors come down to source data problems, not configuration problems. The integration is built correctly. The data it’s being asked to process isn’t.
Common issues are:
- Missing required fields
- Date format mismatches
- Account numbers that don’t exist in GP
- Duplicate document numbers
Integration Manager validates each record against GP’s business rules before importing it, which means any record that wouldn’t pass manual data entry won’t pass an integration either.
Before you run any integration on a live company, test it against a backup or a test company first. This is especially important for transaction imports. A journal entry that posts with incorrect amounts requires a reversing entry to fix. Catching the problem in a test environment costs you nothing. Catching it in production costs you time and creates cleanup work.
CAL’s team has built and supported GP integrations across a wide range of industries and data sources. If you’re working through a complex integration scenario or running into errors you can’t resolve, our GP integration specialists can help you work through it.
Frequently Asked Questions: GP Integration Manager
What is GP Integration Manager used for in Microsoft Dynamics GP?
GP Integration Manager is a tool included with Microsoft Dynamics GP that automates data imports from external sources into GP modules. It supports both master record imports, such as customers, vendors, and items, and transaction imports, such as journal entries, payables invoices, and purchase orders. Users define a source, map fields to a GP destination, and run the integration on demand without writing custom code or manipulating GP’s database directly.
What file formats does GP Integration Manager support as a source?
Integration Manager supports text files (comma-delimited or tab-delimited CSV) and ODBC data sources, including Excel spreadsheets connected via ODBC and SQL Server databases. For simple one-time imports, a clean CSV file with a header row is the most straightforward option. For recurring imports from a live system, an ODBC connection allows Integration Manager to read directly from the source without a manual export step.
What should you do when GP Integration Manager shows errors after running an integration?
After each integration run, review the exceptions log to identify which records failed and why. Most errors are caused by source data problems: missing required fields, incorrect date formats, account numbers that don’t exist in GP, or duplicate document numbers. Correct the source data for the failed records and re-run the integration for those records only. For complex transactions, always test the integration against a test company or a restored backup before running it in your live GP environment.
Need Help with a GP Integration?
Integration Manager handles straightforward imports well. For more complex scenarios, including multi-source integrations, ongoing automated imports, or preparing your data for a migration to Acumatica or Microsoft Dynamics 365 Business Central, contact CAL Business Solutions to talk through your options.
Also worth reading: Stop Re-Keying Data: Eliminate Manual Data Entry in Dynamics GP for a look at the full range of tools available for getting data into GP.
CAL Business Solutions is a Microsoft Dynamics GP, Acumatica, and Microsoft Dynamics 365 Business Central implementation partner serving distribution, manufacturing, brick & block, and professional services businesses across the United States. Our team has supported GP customers with integrations, data migrations, and system implementations for over 40 years.
