To move dynamics gp to business central without stopping AR, clean the open items first, load each invoice, credit and unapplied receipt as its own line, and reconcile the customer ledger to the GL control account before go-live. Run the whole sequence twice in a test tenant before anyone collects against it.
Most teams plan the GL and the chart of accounts and treat receivables as an afterthought. Then the first week on the new system arrives and collectors can’t tell which invoices are open. A good dynamics gp consultant will start with AR for exactly that reason.
This guide is for controllers and IT directors who need cash to keep coming in during the move.
Quick Answer A dynamics gp to business central migration keeps AR running when open invoices, credits and unapplied receipts are cleaned in GP, loaded as individual customer ledger entries, and reconciled to the GL control account before go-live. Test the load twice, cut over away from quarter end, and treat the first clean month-end close as the exit test.
AR is risky because every open item is a promise someone will pay, and a collector needs the right amount, due date and customer on each one. A GL balance that is off by a few dollars is an accounting problem. An invoice that arrives with the wrong remaining amount is a phone call to a customer who already paid.
There is also a structural reason. Most checks on a migration look at master data and GL balances. Microsoft’s built-in validation tests G/L accounts, bank accounts, customers, vendors and items, but open AR documents and customer balances are not on its list of tested entities. So you reconcile AR yourself.
The QServices Framework AR Cutover = Clean → Load → Reconcile → Cut over → Stabilize
Cleaning comes first because every later stage inherits whatever mess you carry in. Reconcile sits before cutover because a variance found in a test costs an hour, and one found after go-live costs a week of collections.
Microsoft’s Dynamics 365 blog says product support and updates for Dynamics GP end on 31 December 2029, moved from 30 September 2029 in a January 2025 notice. Security patches run to 30 April 2031. Older articles still quote September, so check the date before you build a plan. Our Dynamics GP end of life guide covers what that means for your team.
Per Microsoft Learn, outstanding receivables arrive at the amount remaining. A $1,000 invoice with $400 paid arrives as a $600 invoice. That is fine for collecting, but the original amount and earlier applications are not in the ledger entry. Detail can be copied into a read-only GP Historical Snapshot for reporting.
Key Insight The migration tool brings over what is owed, not how it got there. If an auditor or customer asks for the original invoice amount, the answer lives in the snapshot or in an archived GP, so decide where before you cut over.
Clean in GP, not in Business Central. Every fix made before extraction is a fix you make once, and every fix made after is a journal you have to explain.
Start with a list of what goes wrong most often:
Write off or settle what you can. Microsoft notes inactive customers are off by default in the migration tool, so a customer with a balance and an inactive flag can silently stay behind. Check it.
Dynamics GP unapplied cash migration deserves its own decision. Microsoft’s documentation describes no GP-specific handling for unapplied cash or customer credit balances, so confirm behavior in a test run rather than assuming. Posted cash receipts must also be deposited in GP before migrating, because undeposited receipts are not migrated.
Apply what you can now. Our guide to clearing an unapplied cash backlog walks through the usual causes, and the cash application process shows where matching breaks. Whatever remains should be a short list a person has reviewed and signed off on.
Real-World Scenario A typical case we see: a controller at a distributor with 3,400 open invoices finds 210 unapplied receipts, many over a year old, two days before the test load. In the naive approach they migrate everything, and collectors then dun customers who already paid. The Clean stage catches it: the team applies or documents each receipt first, and the load starts with a reviewed list rather than a surprise.
There are two routes, and most teams use the tool for master data and balances, then journals for anything that needs adjusting. A person reviews each batch before anything posts.
| Approach | Best for | Honest downside |
|---|---|---|
| Migration tool | Customers, open receivables, GL history by period | Open items arrive at remaining amounts, so original invoice detail is lost from the ledger |
| Journal load | Opening balances with each invoice as its own line | Slower to prepare and more manual effort |
| Historical snapshot | Read-only AR detail for reporting | Cannot be applied against; collectors work from the live entries |
To migrate customer balances to Business Central, choose all or active customers, then map each customer class posting account to a Business Central customer posting group. Migrated transactions auto-post in batches by type. You can turn auto-posting off and adjust the data first, which we recommend for the final test.
For Business Central opening balances for customers loaded by journal, Microsoft says to use journals rather than writing ledger entries directly. Load each open invoice, credit memo and unapplied receipt as its own line so later payments apply to the original invoice. Practitioner guides suggest a clearing account on the GL side. That is advice, not a standard, so test it.
Never run the cloud migration into a production tenant already in use.
Standards & References
- Microsoft Learn: Migrate data to Business Central: replication, change tracking and data upgrade steps
- Microsoft Learn: Manage receivables: customer ledger entries, applying payments and aging reports
Cutover week is where a plan meets collectors. Practitioners advise avoiding go-live at quarter or year end, and we agree. Pick a window right after a close.
This is the dynamics gp to business central cutover checklist we use for AR:
Capture a pre-cutover DSO baseline now. No source we found quantifies how migration moves it, and you will want a number to compare. Our DSO formula guide shows how to calculate it consistently.
Key Insight After a successful data upgrade, replication cannot be rerun from an earlier version. Treat step 4 as a one-way door and finish your reconciliation before you walk through it.
The first month is about proof. Controllers should expect to reconcile daily in week one, then weekly.
Use a three-way tie-out. The Aged Accounts Receivable (Excel) report is Microsoft’s recommended aging report, and it reconciles the customer subledger to the GL receivables account when direct posting is disabled. Customer Trial Balance shows opening balances, period activity and closing balances. Customer – Detail Trial Balance confirms every entry for a customer is accounted for.
Bring open items and a limited history. Microsoft calls limiting the GL years a best practice, since history arrives as summary transactions by period. Years marked historical in GP arrive as open in Business Central and must be closed there. Use the snapshot for detail you may need.
Exit test: the first clean month-end close, with AR tying to the GL and no unexplained items.
We start with the Clean stage, because AR problems are cheapest to fix in GP. The same team that builds the migration runs the cutover with you.
We treat this as part of wider ERP modernization, and a business central partner should be able to show you each deliverable above. Where we add AI agents for matching and follow-ups, your team approves anything that posts money or changes a system.
Implementation Checklist
- Customer classes mapped to Business Central posting groups
- Inactive customers with open balances reviewed
- Posted cash receipts deposited in GP
- Unapplied receipts applied or documented
- Two test migrations completed with auto-posting off
- Customer ledger total equals GL control account
- Pre-cutover DSO baseline recorded
- Go-live date set outside quarter end
AR does not have to stop when you move. Clean first, reconcile twice, and cut over right after a close. Plan your ERP move with a team that starts with receivables.
Written by Rohit Dabra
Co-Founder and CTO, QServices IT Solutions Pvt Ltd
Rohit Dabra is the Co-Founder and Chief Technology Officer at QServices, a software development company focused on building practical digital solutions for businesses. At QServices, Rohit works closely with startups and growing businesses to design and develop web platforms, mobile applications, and scalable cloud systems. He is particularly interested in automation and artificial intelligence, building systems that automate routine tasks for teams and organizations.
Clean the open items in GP, then replicate into a test tenant with auto-posting off. Microsoft’s tool brings open receivables at the amount remaining. If you need each invoice as its own line, load opening balances by journal. Reconcile the customer ledger to the GL control account before go-live.
Microsoft documents no GP-specific handling for unapplied cash, so confirm it in a test migration. Posted receipts must be deposited in GP first, because undeposited receipts are not migrated. Apply or document unapplied receipts before the final load.
It depends on modules, companies, open transactions, history and customizations. Partner estimates range from a few months to well over a year. Plan for at least two full test migrations of AR before go-live, and book your partner early because capacity tightens as 2029 approaches.
Bring open items plus a limited number of GL years. Microsoft calls limiting years a best practice. Keep detailed AR history in the read-only GP Historical Snapshot or an archive instead of the live ledger.
Start with an AR cleanup list and a pre-cutover DSO baseline. Then run a test migration into a separate tenant and compare the customer ledger, GL control account and aged receivables. Our team can run that first step with you before you commit to a go-live date.
Moving from Dynamics GP to Business Central? Learn how to clean, load and cut over open invoices and balances so your AR team keeps collecting.
Reduce DSO without adding headcount. Six fixes ranked by effort, from same-day cash application to cleaner invoices and faster dispute resolution.
Learn to read an EDI 820 segment by segment, match it to the invoices it pays, and post it cleanly in SYSPRO, Epicor or Business Central.
Copilot Studio agents can read remittances, take orders from email and triage tickets. See what each needs from your ERP and where a person approves.
Get a free remittance advice template, learn what a good one includes, and see how 200 customer formats hit your AR team. Download the template today.
When PDF text extraction drops the spaces between words, AI agents can’t find facts that are right there. How we found it in Azure AI Foundry and fixed it.
Moving from Dynamics GP to Business Central? Learn how to clean, load and cut over open invoices and balances so your AR team keeps collecting.
Reduce DSO without adding headcount. Six fixes ranked by effort, from same-day cash application to cleaner invoices and faster dispute resolution.
Learn to read an EDI 820 segment by segment, match it to the invoices it pays, and post it cleanly in SYSPRO, Epicor or Business Central.
Copilot Studio agents can read remittances, take orders from email and triage tickets. See what each needs from your ERP and where a person approves.
Get a free remittance advice template, learn what a good one includes, and see how 200 customer formats hit your AR team. Download the template today.
When PDF text extraction drops the spaces between words, AI agents can’t find facts that are right there. How we found it in Azure AI Foundry and fixed it.
Earning Global Recognition: A Testament to Quality Work and Client Satisfaction. Our Business Thrives on Customer Partnership
Founder and CEO
Chief Sales Officer
Join our live webinar on Sept 24 and see five
ways to automate meetings, approvals, and
document search with tools already in your
tenant.
