/
/
Bring the customers your migration missed into Business Central
For IT and finance teams who want active Dynamics GP customers missing from Business Central created there, by asking their AI assistant.
On this page
Connector
Connect Microsoft Dynamics GP, pick your AI tool and paste the prompt.
The problem
Customers the migration missed
After moving from Dynamics GP to Dynamics 365 Business Central, some active customers never made it across. Finding them means comparing two lists whose IDs differ in case and padding, then keying each one in by hand.
Without PopdockAI
- Export customers from both systems
- Match IDs that differ in case and spacing
- Key each missing customer into Business Central
- Forget that open GP balances do not move with them
With PopdockAI
- IDs are matched regardless of case and spacing
- IDs too long for Business Central are set aside
- Customers with a GP balance are flagged
- Only confirmed customers are created, and each is read back
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find active Dynamics GP customers that do not exist in Business Central and create them in BC after the user confirms, for customer `{customer-id}` or, if that is empty, every active GP customer, creating at most `{max-creates}` customers (default 25).
**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.
**Step 2: Find the gaps in BC**
Call `business-central-get-customer` for the same scope and match GP `customer-id` to BC `customer-number`, trimmed and case-insensitive. Keep the GP customers with no match.
Set aside, and do not create, any customer whose trimmed customer-id is longer than 20 characters (the BC limit). Flag, but still offer, any customer whose GP customer-balance is not zero: creating the customer does not bring its open balance across.
**Step 3: Confirm with the user**
Show the list of customers to create (customer-id, customer-name, city, state, customer-balance) and the set-aside list. Ask the user to confirm. Do not create anything until they say yes. If they name a subset, create only that subset.
**Step 4: Create each confirmed customer**
Call `business-central-create-customer` once per customer with:
* number = the trimmed GP customer-id
* display-name = customer-name
* address-line-1 = address-1, city = city, state = state, postal-code = zip
* phone-number = phone-1 as digits only, with any trailing zero-padded extension removed
* email = main-email-address
* credit-limit = credit-limit-amount
If a create fails, report the error for that customer and continue with the rest. Stop after `{max-creates}` creates.
**Step 5: Confirm**
Call `business-central-get-customer` with `customer-number` for each created customer and confirm it exists. Report: created and confirmed, failed with the error, set aside with the reason.
**Rules & Guidelines:**
* `dynamics-gp-get-rm-customer` is on the dynamics-gp server. `business-central-get-customer` and `business-central-create-customer` are on the business-central server.
* `business-central-create-customer` is the ONLY write this prompt may make, and only after Step 3's confirmation. Do NOT call `business-central-update-customer`, `dynamics-gp-rm-customer-add` or `dynamics-gp-rm-customer-update`, and never write to GP.
* 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 nothing is missing, say every active GP customer already exists in BC and stop.
* The create tool cannot set payment terms or the customer posting group. Tell the user to set both in BC for every new customer before posting to it, and list the GP payment-terms-id and customer-class for each so they know what to choose.Who it's for
One answer, three teams that use it
Migration leads
Close customer gaps after go-live
Missing customers are found and created in a batch, with the setup left to finish listed for each.
Which active Dynamics GP customers are missing from Business Central? Create the first 20 after I review.
ERP administrators
Fix one missing customer fast
When an order fails because the customer is not there, bring that one customer across in a single request.
Customer FABRIKAM01 is in Dynamics GP but not Business Central. Create it there.
Accounts receivable
Know which balances still need moving
Customers with an open GP balance are flagged, so you know which balances to bring across separately.
Find GP customers missing from Business Central and tell me which ones still have a balance in GP.
How it works
What PopdockAI does when you ask
You name one customer or check every active one, and your AI assistant finds the Dynamics GP customers missing from Business Central. Nothing is created until you confirm, and only Business Central is written to.
01
Ask
You name one customer or let it check every active one.
02
Compare
It matches Dynamics GP and Business Central IDs regardless of case and spacing.
03
Confirm
You review the missing customers, with balances and long IDs flagged.
04
Create
It creates them in Business Central and reads each one back.
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
Every active customer in Business Central
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)
