From the Microsoft Dynamics GP blogs: Upgrade planning; Signs your GP database needs attention

In this week's Microsoft Dynamics GP blogs: 

• GP Upgrade 2026: The database upgrade, modified dictionary upgrade, upgrade troubleshooting
• 5 signs your GP database needs attention

Microsoft Dynamics GP Upgrade 2026 – the database upgrade, modified dictionary upgrade, upgrade troubleshooting

In a series of recent posts on the Dynamics GP Support and Services Blog, Angela Eckman walked users through upgrading Microsoft Dynamics GP databases, moving customized forms and reports to the new version, and dealing with failed upgrades. Much of the advice comes down to being prepared before making changes to a live system.

The database upgrade

Eckman wrote that one of the biggest parts of a Dynamics GP upgrade is moving the system and company databases to the new version. She recommended running a test upgrade first to uncover problems before touching the production system.

She noted that a test run can help IT teams determine whether their version of SQL Server will work with the new release and whether there are any problems with the upgrade path. It can also give them a better idea of how long the upgrade will take and how much downtime to expect.

Before getting started, companies should also check Microsoft's upgrade instructions and review any known issues. Older features or modules can sometimes cause problems if they haven't been updated to work with the new version.

Eckman added that companies should make backups before beginning the upgrade. That includes the Dynamics GP system database, company databases, and any customized forms and reports.

Modified dictionary upgrade

Eckman noted one important step that's often overlooked during upgrades: modified forms and reports dictionaries. Companies that have customized Dynamics GP forms or reports need to take some additional steps.