Dynamics GP 18.9 Upgrade Checklist for Finance Teams Without an IT Department

Last updated: November 5, 2026

TL;DR: GP 18.9 is an all-inclusive update from Microsoft with no big security requirement changes, so the risk sits around Dynamics GP (SQL Server, Windows Server, add-ons, integrations) and not inside it. Confirm your build, check the servers, back up every database, test a copy with live data, and have finance run its own script before anyone touches production.

Somebody told you the Dynamics GP 18.9 upgrade is just an install. Maybe it is. Nobody said who signs off, though, or who tests the check run, or what happens to the integration that feeds payables every night. Nobody. That’s the gap this checklist fills.

Microsoft’s own upgrade checklist is 12 steps, and it reads like a task list for an administrator. Your situation is different. You’re a finance lead or a president, there’s no IT department behind you, and the person who knows the system may be one resignation away from taking that knowledge out the door. So the checklist below has an owner column. Some steps belong to your GP partner or hosting provider. Some belong to finance. A few belong to both, and those are the ones that get skipped.

You’ll also find the platform dates that sit outside GP’s own calendar, a finance test script you can hand to your controller, and a straight answer on when an upgrade isn’t what you need, which sometimes is never.

What’s Actually in Dynamics GP 18.9?

GP 18.9 is Microsoft’s October 2026 update. Microsoft calls it all-inclusive and says there are no big security requirement changes with this release.

That’s the reassuring part. The announcement post doesn’t list features at all, though. It points to a What’s New page, detailed documentation, and a feature blog series, and when we tried the What’s New page on October 28, it wouldn’t load. No confirmed list yet.

Rand Group, another GP partner, published a preview on September 24, 2026 that lists what’s planned. Planned, not confirmed.

• Management Reporter and Microsoft Edge get compatibility updates.
• Voided payables checks and invoices get reason codes.
• SmartList records when each list was last used and who changed it.
• Cancel a purchase order and its workflow closes on its own.
• Workflow approvers get more ways to be notified.

Fixes ride along too. That void item touches a control point, so it earns a spot on the finance test script further down.

Should You Upgrade Now or Wait?

Waiting a few weeks after any release is normal. Rushing isn’t. Which one fits depends on two clocks, the one your add-on vendors keep and the one your finance team keeps. Both matter.

Add-ons first. The upgrade planning post lists ISV solutions, integrations, and modified dictionaries among the areas to validate, and one add-on that isn’t ready for 18.9 can stall the whole project.

Then there’s the finance calendar. October through January is year-end, 1099, and W-2 season, and a version change in the middle of it takes attention that’s already spoken for. That’s busy season.

On the other side of the ledger sit the server dates in the next sections. Staying within one release of current also keeps the upgrade path short, because Microsoft’s upgrade page says the only supported path is from the release one year back, which is why a company that skips a year ends up planning a stepped, multi-stage project instead of a single upgrade.

GP support ends December 31, 2029 (Pacific time), according to Microsoft’s lifecycle page. That leaves room to plan. No fire drill here. Our post on the Argus 10-Year Commitment covers what comes after.

Can Your Version Upgrade Straight to 18.9?

Supported upgrades come from the release one year back, which for 18.9 means 18.8. Rand Group names 18.7.1756 as the earliest supported starting build, and Microsoft hasn’t published its own 18.9 number where we could find it. Treat that as a lead.

Microsoft’s upgrade page hasn’t caught up with 18.9 at all. Its newest listed release is 18.8, and for that release it gives two different starting points, 18.7.1756 in the table and 18.6.1685 in a tested-path example. Two numbers, one page.

Where you’re starting	What to expect
On 18.8	The straight path, per Microsoft’s one-release-back rule
On 18.7.1756 or later	A supported starting point, per Rand Group
Anything older	Plan a stepped upgrade through an intermediate release, and ask your partner to confirm the path in writing

Argus’s GP version history page is a handy reference if you’re trying to place your release on the timeline. Your actual build number lives in GP itself, so check every environment. Test too.

Will Your SQL Server and Windows Server Work With GP 18.9?

SQL Server 2025, 2022, and 2019 are the versions Microsoft lists for GP 18.9 and later. SQL Server 2016 support ended July 14, 2026, and Windows Server 2016 extended support ends in January 2027. Who in your company knows which versions you’re on today?

SQL Server 2017 is the murky one. The cheat sheet at the top of Microsoft’s system requirements page leaves it off for 18.9 and later, while a table lower on the same page still lists it for 18.8.1941 and later. Microsoft’s page contradicts itself here, so confirm your SQL Server 2017 status with your partner.

Windows Server has its own wrinkle. The same page says that since the move to TLS 1.3 in release 18.8, some Web Client issues may occur on Windows Server 2016, and it recommends moving to a newer version. Windows Server 2022 needs GP 18.5.1556 or later, and Windows Server 2025 needs 18.7.1756 or later.

Platform date	What happens
July 14, 2026	SQL Server 2016 support ended (Dynamics Communities, Sept. 18, 2026)
January 2027	Windows Server 2016 extended support ends (Microsoft lifecycle)
December 31, 2029	GP support ends, per Microsoft’s lifecycle page

Those platform clocks run separately from GP’s own calendar. Easy to miss. If another provider hosts your GP environment, the server side is theirs to track, and cloud hosting is worth asking about before you pick an upgrade date. Ask for the SQL Server and Windows Server versions. Get it in writing.

What’s on the Upgrade Checklist, and Who Owns Each Step?

Microsoft publishes a 12-step upgrade checklist that runs from verifying system security to identifying the sources of errors. The table below folds that list, plus the 18.9 planning post, into what a finance team has to manage. The owner column is the part Microsoft’s list leaves out.

Phase	Step	Owner
Before	Confirm the version and build in every environment	Partner or IT
Before	Check SQL Server and Windows Server against Microsoft’s requirements	Hosting provider or IT
Before	Back up the DYNAMICS database and every company database	Partner or IT, with finance confirming the backup exists
Before	List every add-on, integration, modified dictionary, VBA project, and custom report	Finance names them, partner inventories them
Before	Get each add-on vendor to confirm 18.9 support	Partner, with finance holding the vendor list
Test	Upgrade a copy of production using current data	Partner or IT
Test	Run the finance test script	Finance
Go-live	Pick a date outside month-end close and year-end	Finance decides
Go-live	Install the update, then update Web Services and Web Client	Partner or IT
After	Check workstations, integrations, Management Reporter, reports, and templates	Shared
After	Sign off	Finance

Two rows need more room. Microsoft’s planning post says Web Services and Web Client have to be updated after the install, which is easy to forget when the server side looks finished, and integrations such as eConnect and Integration Manager sit on the same validate list for a reason, since a broken nightly import can surface later as a payables batch that never arrived.

Registration keys are a small contradiction. The planning post says new keys aren’t expected unless Microsoft announces otherwise, while the older checklist still lists getting new keys as a step. Ask before you assume.

What Should Finance Test Before Go-Live?

Run these on the test copy, with production data, before anyone schedules the real thing, because a technical pass only tells you the install worked and only finance can say the books still behave. Don’t skip the boring ones.

• Post a journal entry, then reverse it.
• Take a payables batch from entry through to a printed check, then void a test check. If 18.9 adds void reason codes, see what the prompt looks like and who can bypass it.
• Receive a purchase order. Cancel a different one and watch whether its workflow closes.
• Reconcile a month in Bank Reconciliation.
• Open the SmartLists you actually rely on.
• Run your month-end Management Reporter statements and compare the totals to production, penny for penny.
• Run the three or four reports your executives ask for by name.
• Trigger every integration that feeds GP, whether that’s expense import, payroll, or a bank file.
• Log in as someone with limited access and confirm the security roles still behave.

Penny for penny sounds fussy. It’s how you catch a rounding or mapping change before the board does. Keep the printouts.

How Long Does a GP Upgrade Take, and What Does It Cost?

Nobody can price your upgrade without seeing your system. Microsoft doesn’t set what a partner charges, and the hours depend on the size and shape of your environment. Hours follow complexity.

Cost drivers are knowable, though, and they come down to how many companies sit in your GP install, how far behind your current version is, how many modified dictionaries, add-ons, and integrations need testing, whether SQL Server or Windows Server is changing at the same time, and how many workstations need the new client.

Your annual enhancement plan matters here. If it’s current, the new version itself is generally covered, but the install and testing hours are service work, so confirm the terms with your partner.

Only a test upgrade on a copy gives an honest time estimate. Quoting downtime before that test is guessing.

When Is an Upgrade Not the Answer?

Sometimes the upgrade is fine and the problem is somewhere else. If your reports can’t be trusted, or your team keys the same data twice, version 18.9 won’t change either one. Version numbers don’t fix habits.

In one Argus engagement, a client was using about 30% of what GP offers. A newer version would have given them a newer copy of the same underused system. That’s the case for looking at GP optimization before spending on a bigger move, and it’s why Argus talks about optimizing before migrating.

Argus sells optimization and migration work, so weigh that. If your reports are right, your team’s hours are reasonable, and your partner picks up the phone, a plain upgrade on a sensible schedule is all you need.

And if the real question is whether to stay on GP or move, Business Central migration is a separate decision with a separate timeline. Microsoft’s current GP support date leaves room to make it calmly. Upgrading commits you to nothing.

What to Do Next

Pick an owner for each row in the checklist, ask your add-on vendors and your server provider the two questions above, and schedule the test upgrade before you schedule the real one. Run the finance script. Keep the results.

If you want a second set of eyes before you choose a date, a free assessment is a low-pressure way to see what your GP setup needs, whether that’s an upgrade, optimization, or a longer look at your options. You can also call (626) 403-9744.

Questions Finance Teams Ask About the 18.9 Upgrade

Is the GP 18.9 upgrade free?

Generally yes for the software itself, if your annual enhancement plan is current. Installing and testing it is service work your partner bills separately, so confirm the terms before you budget.

Will we need new registration keys?

New keys aren’t expected unless Microsoft announces otherwise, according to its upgrade planning post. The older upgrade checklist still lists getting keys as a step, so check before go-live.

Can we stay on Windows Server 2022?

Windows Server 2022 works with GP 18.5.1556 or later, according to Microsoft’s requirements page, so an 18.9 upgrade doesn’t force a server change there. Windows Server 2016 is the one to watch, since Microsoft ties it to Web Client issues since 18.8 and ends its extended support in January 2027.

Will our add-ons still work?

Not until the vendor says so. Ask each one in writing whether it supports 18.9, because Microsoft’s planning post lists ISV solutions among the areas to validate.

How much downtime should we plan for?

You’ll know after the test upgrade on a copy of production, and not before. Database size and the number of companies drive the number, and a guess made without those two facts is just a guess.

Does upgrading change the 2029 date?

It doesn’t. Microsoft’s lifecycle page lists December 31, 2029 (Pacific time) as the end of GP support, and the 18.9 announcement doesn’t mention changing it. An upgrade keeps you current, and the question of what comes after is a separate plan you can make on your own timeline.