Last updated: November 10, 2026
When the person who knows your Dynamics GP setup leaves, the data stays and the working knowledge goes. A one-page continuity checklist covers the close steps, reports, integrations, and admin access, and you can start it this week.
TL;DR: One 2026 study ranks controllers as the hardest finance role to recruit, so waiting to find a replacement isn’t a plan. Write a one-page continuity sheet for your Dynamics GP setup, name a backup for each close step, and settle what your partner covers and what stays in-house.
Picture a Tuesday in the second week of the month. Your controller, who has run close in GP for years, has given two weeks’ notice. The data isn’t going anywhere. What’s less certain is who knows which batch has to post before which, why one account exists at all, which reports were built by hand years ago, and who holds the admin login to the server underneath.
That’s a calmer problem than it sounds. A written page, a named backup, and a clear line between what your partner covers and what stays in-house go a long way.
Argus Consulting Group is a Dynamics GP partner in Pasadena, California, founded in 1989, with GP experience since 1993. Relying on one power user is one of the problems that sends finance teams looking for a GP partner in the first place. This post covers what the hiring data says, what actually walks out the door, a checklist you can use, and where a partner fits.
How Hard Is It to Replace a Controller Right Now?
Hard enough to plan around. The Controllers Council’s 2026 Corporate Finance & Accounting Talent Study found 44% of respondents naming controllers and assistant controllers as the hardest finance positions to recruit, and the Council says controllers have held that top spot for four years running.
| Source | What it reports | What to keep in mind |
|---|---|---|
| Controllers Council, 2026 Corporate Finance & Accounting Talent Study | 44% named controllers and assistant controllers hardest to recruit. Bookkeeper, accountant, and financial reporting roles came second at 34%. | The pages we read don’t show sample size or company size. |
| Controllers Council infographic | 46% of respondents report minor shortages and 15% report significant ones. | Same limits as above. |
| CFO Dive, July 31, 2026 | Shortage looks over at larger firms. An AICPA director says many small and midsize firms still report trouble hiring qualified people. | Covers accounting firms and the profession, not corporate finance departments. |
CFO Dive also reports that the Bureau of Labor Statistics counted 1.45 million accountants and auditors in May 2025, down from 1.58 million a year earlier. A Hofstra accounting professor quoted in the same piece says smaller firms are adopting AI more slowly than large ones, which raises their need for headcount.
None of the sources we read gives a time-to-fill for a company your size. Plan for a gap, not for a date.
On the GP side, we couldn’t find a count of experienced GP administrators or consultants. One recruiter writing on DynamicsFocus in March 2026 argues that many experienced GP people have moved to other platforms or retired and that companies migrating off GP will compete for a small pool. He cites no data, and he runs a recruiting firm. Treat it as one person’s view.
What Walks Out the Door With Your GP Expert?
The ledger stays. The knowledge around it doesn’t.
A Dawgen Global piece from August 30, 2026 breaks that knowledge into layers. The procedural layer is how month-end really runs, including the workarounds and spreadsheets that bridge gaps in the accounting package, which the author says are rarely written down anywhere and which a successor won’t find by opening the system. The contextual layer is the reasons, like why an account exists or why one customer has different terms. Then come relationships, like which bank officer answers quickly. The author calls a short handover a demonstration rather than a transfer.
Riveron’s 2021 guidance on turnover adds a plainer problem. Files saved on a departed CFO’s laptop and nowhere else.
In a GP environment, that tends to look like this.
- The order of operations for close, including which batches post before others
- Why your account framework or posting setup looks the way it does
- Which reports are custom, who built them, and where they’re saved
- Integrations that run on a schedule, and what a failure looks like when one does
- Who holds the sa login, the SQL logins, and the admin rights inside GP
Access deserves its own look. Sikich’s GP security guidance, written in 2020, says finance and accounting staff shouldn’t have the sa password for daily use, and that GP users shouldn’t share passwords. Shared logins hide who did what and make it harder to cut off access when someone leaves.
A trade-press guide for people who inherit GP administration (undated) says backing up the database isn’t enough. It lists custom forms, custom reports, Integration Manager databases, and the notes share as things to back up too. It also points to Help, then About, inside GP as a quick way to see which products are installed.
What Goes on a One-Page GP Continuity Checklist?
Nine rows, one page. The owners below are suggestions, not requirements.
| Item | What to write down | Suggested owner |
|---|---|---|
| Month-end close | The steps in order, who does each, and the deadlines | Controller, plus one named backup |
| GP users and security roles | Who has which role and who can add users | Finance lead |
| Admin and SQL access | Who holds sa, SQL, and GP admin logins, and where they’re stored | President or finance lead |
| Backups | What’s backed up, how often, and who has restored one | Partner, hosting provider, or IT |
| Installed products and customizations | The Help, About list, plus add-ons, modified forms, and reports | Partner and finance |
| Integrations | What feeds GP, on what schedule, and what failure looks like | Finance and partner |
| Custom reports | Names, purpose, and where they’re saved | Finance |
| Vendor bank changes and payment release | Who can change a bank account and who approves a payment | President or finance lead |
| Outside contacts | GP partner, bank, payroll provider, and auditor | Finance lead |
If an outside provider hosts your GP environment, the server logins sit with them. Put that provider and a contact name on the sheet. For more on that setup, see GP cloud hosting.
How Do You Start Without Stopping the Close?
Keep it small. CLA’s August 12, 2026 guidance on finance continuity opens with one question, “What can’t stop?” It suggests mapping deadlines for the next 30, 60, and 90 days and confirming who holds system access and approval authority. It also says a useful process guide doesn’t need to be long, and it starts with bank reconciliations, payroll, the month-end checklist, and covenant reporting.
For a GP shop, that looks like this.
- This week, write down the close steps in the order they happen. Rough is fine.
- Name a backup for each step. One name per step.
- Confirm the access list against the table above, and remove anyone who no longer needs a login.
- Have the backup run one reconciliation from the written steps while the expert watches. Fix whatever the steps left out.
- Put the sheet somewhere other than one person’s laptop.
CLA’s guidance also covers what to do after someone has already left. Secure access and files in the first week, assign temporary owners for must-run work, and tell outside parties like auditors or lenders. A sheet written before that day makes the first week much shorter.
What Can a GP Support Partner Cover, and What Can’t It?
A partner covers the system. You cover the decisions.
A support partner can answer how-do-I questions, find what’s installed and customized, fix reports and integrations, and keep GP updated. Argus’s annual GP support packages include end user support, system upgrades, and custom reporting. Our clients tell us they value getting complete answers from their primary consultant without a routing queue, which matters on the day your expert is gone and the question is urgent.
A partner can’t approve a payment, hold your signing authority, or know why your close runs in a certain order unless someone tells them, and it doesn’t know the Friday-afternoon workaround that lives in one person’s head either. That part stays with your team.
We support GP, so of course we’d say a partner helps. If you have a full-time GP administrator with a trained and documented backup, you may need less than this section suggests. For companies without an IT department, a GP support relationship is one way to keep a second set of eyes on the system, and it works best when the continuity sheet already exists to hand over. If the person leaving is your partner and not your employee, start with what to do when your GP partner retires.
Is a Departure the Moment to Rethink the Setup?
It can be. CLA warns against rehiring back into the same inefficiencies, and the same goes for GP. A departure shows what the setup depends on, and some of that dependence is a workaround that a configuration change could remove, which is a better thing to learn in October than in the middle of a January close.
That’s the argument for optimizing the GP you already run before deciding anything bigger. Microsoft’s lifecycle page lists December 31, 2029 as the end of GP support, which leaves time to choose. If a move to Business Central is on your list, it’s a separate decision with its own timeline, and the same continuity sheet carries over to the new system. A new platform doesn’t remove key-person risk by itself.
If you’d like help building the sheet or checking your GP access list, start with a free assessment. We lay out options, and you decide.
Questions Finance Teams Ask About Losing a GP Expert
How long does it take to replace a controller?
None of the sources we read gives a time-to-fill for a company your size. The Controllers Council study ranks controllers hardest to recruit for four years running, so plan an interim path before you need one.
Should we hire another GP expert or lean on a partner?
It depends on how much of the work is GP knowledge and how much is your company’s own rules. A partner covers the first. Someone on staff has to own the second.
What should an employee hand over before their last day?
Written steps, access, and a witnessed run. CLA’s list for the first week is to identify critical deadlines, secure access and files, and assign temporary owners for must-run work, and Dawgen’s point about a handover being a demonstration is the reason to ask for the written version too.
Do we need a big documentation project?
No. CLA says a useful process guide doesn’t need to be long, and it recommends starting with the highest-disruption work like bank reconciliations, payroll, and the close checklist. One page that people can actually follow beats a binder.
Should finance staff have the sa password?
Not for daily use, according to Sikich’s 2020 GP security guidance. It suggests having a database administrator, or a GP user with specific SQL roles, handle user setup instead. Whoever holds the sa login should be written on the continuity sheet.
Does moving to Business Central fix key-person risk?
No. A new system still needs documented close steps, an access list, and a named backup. If one person is the only one who knows how things run today, that dependence moves with you unless you write it down first, so the continuity sheet is worth building before any migration conversation gets serious.