Last updated: October 20, 2026
If your Dynamics GP partner retired, don’t panic and don’t sign with the first firm that calls. Inventory what you have, collect a handoff package, keep the system running, and interview replacements before you choose.
TL;DR. A retiring partner takes more than a phone number with them. They take the history of your system, the reasons behind your setup, and the quick fixes nobody wrote down. Your first job is to capture that knowledge before it walks out. Your second is to find a replacement who can take it over without disrupting your close. Move deliberately, but don’t wait for a failure to force the issue.
Picture the email. It arrives on an ordinary Tuesday, your GP partner is retiring after many years, and there’s a name for a transition contact. You finish reading and realize you don’t know who else understands your system. Not one person. Familiar? Our Dynamics GP support team takes over from retiring partners, and a lot of our clients came to us this way.
Here’s the order we’d work in. Start at the top.
The first week: change nothing
Resist the urge to fix things. Stabilize first. Fixes come later.
Don’t upgrade. Don’t restructure security. Don’t start a Business Central project just because the system feels orphaned, since you’ll make better choices once you know what you actually have and the current system is still running your payables and your close.
What you do need is a list of who can still help. Write down your internal GP super-users, your IT contact, the retiring partner’s transition contact, and anyone who touches the server. If a name isn’t on that list, nobody owns it. Nobody.
Ask for a handoff package
A retiring partner usually wants to help. Give them something specific to hand over. “Send me everything” gets you nothing useful.
Ask for these ten items. In writing.
- Your GP version and the date of the last tax update installed.
- A list of modules in use, and where your registration keys live.
- Server and SQL Server details, including where backups go.
- The date of the last backup test that restored successfully.
- Your user list and security roles.
- Every customization and third-party add-on, with who owns each license.
- Every integration and scheduled job, including the ones that run overnight.
- Custom reports and any custom SQL.
- Open issues and anything half-finished.
- The status of your Microsoft support plan and how it’s administered.
Number four deserves a second look. A backup nobody has restored is a hope, not a backup. Test it.
Number ten has a catch. Reseller blogs describe changing your partner of record through Microsoft’s portal, but we couldn’t find a Microsoft page that lays out the current steps, and at least one of those posts describes menus from a Microsoft portal that has since been retired, so ask your new partner to walk you through the current process before you assume it works the way an older post says.
Why this matters for controls, not just convenience
If the system touches your financial reporting, knowledge of how it works is a control question. A summary of the COSO Internal Control Framework published by IFAD says organizations should commit to retaining competent people and “develop contingency plans for assignments of responsibility important for internal control.” That’s a secondary summary, not the framework itself. The point holds. When one person holds the knowledge, you have a single point of failure.
We see the same pattern at clients. A Southern California holding company came to us after the person who set up their GP system was long gone, and the reports were homegrown, undocumented, and passed along by word of mouth, so the team running them didn’t know how. They were seven or eight versions behind. We took them from version 10 to the current 18.x release.
None of that was a software failure. It was a knowledge failure. Plain and simple.
Choosing a replacement
The retirement is also a chance to ask whether your current setup still fits. Use it.
Microsoft’s own partner directory says you can browse it or contact Microsoft to find a partner, but the page offers no filter for Dynamics GP, so don’t expect it to do the vetting for you. Ask for references. Ask who would actually do the work, and whether that’s the person you’d be calling when you need a quick answer on the last day of the month, because that’s the call that tests a partner.
A 2024 Dynamics Communities customer survey, with just 74 respondents, found that 60.81% of them prefer partners for GP support. That’s a small sample, so treat it as directional. It still fits what we hear. People want a human who knows their system, and who picks up the phone when the close is due and something looks wrong.
One more question matters. Can this partner support GP today and handle a Business Central migration later? If you hire a GP-only firm now and migrate in a few years, you’ll be teaching a new team your business all over again.
A sensible first 90 days
A new partner needs a runway to learn your system without breaking your close, and you need one to learn what the new relationship feels like before you commit to anything bigger.
Days 1 to 30. Collect the handoff package, confirm that backups actually restore, and map every integration and scheduled job so nothing surprises you later, with no changes at all unless something is broken.
Days 31 to 60. Run one full month-end close with your new partner watching, fix the first few pain points that surface during it, and write down everything you learn along the way. Everything.
Days 61 to 90. Update the documentation, review what’s unsupported or outdated, and build a roadmap. That roadmap should cover your timeline against Microsoft’s GP support, which ends December 31, 2029, with security updates running to April 30, 2031 per Microsoft’s GP documentation.
The first 30 days feel slow. They’re the reason the next 60 go well.
Is this the moment to migrate?
Maybe. But the retirement isn’t a reason on its own. Microsoft stopped selling new GP subscriptions to new customers on April 1, 2026, and in the same 2024 survey, 57% of respondents had no plans to move off GP within three years. Decide on your business needs, not on the email in your inbox, and take the planning window Microsoft’s dates give you. If a partner is already pushing you toward a move, read what to do when your GP partner pushes a migration.
Argus has committed to supporting Dynamics GP through 2036 under the Argus 10-Year Commitment, and we handle migrations in-house when you’re ready.
Questions about a retired Dynamics GP partner
What should I do first when my GP partner retires?
Change nothing at first, and collect information instead. Get a transition contact, list who still understands the system internally, and ask the retiring partner for a written handoff package covering versions, modules, customizations, integrations, backups, and your support plan status.
What should a retiring partner hand over?
Ask for your GP version and last tax update, module and registration key details, server and backup information, user security roles, customizations and add-ons, integrations and scheduled jobs, custom reports, open issues, and the status of your Microsoft support plan.
Will I lose Microsoft support when my partner retires?
That depends on how your plan is administered, so confirm it with your new partner and Microsoft before assuming either way. We couldn’t find a current Microsoft page that explains the process, and older reseller posts may be out of date.
How do I find a new Dynamics GP partner?
Start with references from people running GP at companies like yours, since Microsoft’s partner directory has no GP filter. Ask who does the work, how fast they answer, and whether they can also handle a Business Central migration later.
Should I migrate to Business Central because my partner retired?
Not automatically, because a retirement is a staffing event rather than a software deadline. Microsoft’s GP support ends December 31, 2029, so you have a planning window, and a stable GP environment with a new partner gives you room to decide properly.
Need someone to pick up where your partner left off?
Tell us what your partner handed over, and what they didn’t. We’ll tell you what’s at risk and what to fix first, with no pressure to change platforms. Then you decide. Start with a Free Business Assessment, or call (626) 403-9744.