/
/
Sign off a customer migration with only real differences listed
For IT and finance teams who want migrated customers compared between Dynamics GP and Business Central, by asking their AI assistant.
On this page
Connector
Connect Microsoft Dynamics GP, pick your AI tool and paste the prompt.
The problem
Hundreds of false differences bury the real ones
Proving a customer migration from Dynamics GP to Business Central means checking names, terms, limits, salespeople, contacts and holds customer by customer. GP pads IDs and phone numbers, so a naive comparison flags hundreds of false differences.
Without PopdockAI
- Export customers from both systems
- Strip padding from IDs and phone numbers
- Compare terms, limits and holds field by field
- Wade through renamed terms reported hundreds of times
With PopdockAI
- IDs are matched regardless of case and padding
- Phones are compared on digits only and holds against blocks
- A terms renaming is reported once as a mapping
- Missing and post go-live customers are listed, with nothing changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Confirm that Dynamics GP customers were migrated to Business Central with matching master data, for customer `{customer-id}` or, if that is empty, every active GP customer.
**Step 1: Read the GP customers**
Call `dynamics-gp-get-rm-customer` with `inactive` set to false, and with `customer-id` set to `{customer-id}` when it is given. Use a `max-records` large enough for the whole customer list (for example 5000). If exactly `max-records` rows come back, say the list may be truncated.
**Step 2: Read the BC customers**
Call `business-central-get-customer`, with `customer-number` set to `{customer-id}` when it is given, otherwise for the full list with the same `max-records`.
Match GP `customer-id` to BC `customer-number`. Compare them trimmed and case-insensitive: GP pads IDs with trailing spaces and BC stores them in upper case.
**Step 3: Compare each matched pair**
* customer-name vs name
* payment-terms-id vs payment-terms-code
* credit-limit-amount vs credit-limit
* salesperson-id vs salesperson-code
* city and state
* main-email-address vs email
* phone-1 vs phone-number, comparing digits only (GP stores phones as padded digit strings with an extension)
* hold = true in GP vs a non-blank blocked value in BC
**Step 4: Report**
Start with counts: matched with no differences, matched with differences, in GP but missing from BC, in BC with no GP match. Then a table of the differences (customer, field, GP value, BC value). List the missing customers separately. List the BC-only customers last and describe them as probably created after go-live, not as errors.
**Rules & Guidelines:**
* `dynamics-gp-get-rm-customer` is on the dynamics-gp server. `business-central-get-customer` is on the business-central server.
* This prompt is read-only. Do NOT call `business-central-create-customer`, `business-central-update-customer`, `dynamics-gp-rm-customer-add` or `dynamics-gp-rm-customer-update`.
* If either system has more than one company, ask the user which GP company and which BC company to use before the first call, and pass them as `company`.
**Validation:**
* If GP returns no customers, stop and ask the user to confirm the GP company. If BC returns none, report that the customer migration has not run yet.
* Payment terms are often renamed during migration ("Net 30" becomes "30 DAYS"). When a whole set of customers differs the same way, report the pairing once as a mapping rather than once per customer.
* Treat a difference in case or surrounding spaces only as a match.Who it's for
One answer, three teams that use it
Migration leads
Sign off customers with confidence
Counts, real differences and missing customers give you the evidence for a migration sign-off.
Reconcile all active customers between Dynamics GP and Business Central and summarize what differs.
ERP administrators
Check one customer after a complaint
When a customer's terms or limit look wrong, compare that one record across both systems in a single request.
Compare customer FABRIKAM01 between Dynamics GP and Business Central.
Credit controllers
Make sure holds came across
GP holds are compared with Business Central blocks, so customers you stopped stay stopped after go-live.
Are all customers on hold in Dynamics GP blocked in Business Central?
How it works
What PopdockAI does when you ask
You name a customer or check every active one, and your AI assistant compares Dynamics GP with Business Central and filters out the formatting noise. Neither system is changed.
01
Ask
You name a customer or check every active one.
02
Match
It reads both systems and matches IDs regardless of case and padding.
03
Compare
It compares names, terms, limits, salespeople, contacts and holds.
04
Report
You get counts, differences, missing customers and new ones since go-live.
What PopdockAI provides
The tools behind the answer
Ready made tools for Microsoft Dynamics GP and one secure connection to your AI tool. No code, no exports.
microsoft-dynamics-gp-get-rm-customer
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Sign off the migration on real differences
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
