<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA["Dynamics GP End of Life 2029: A Practical Migration Roadmap to Business Central]]></title><description><![CDATA["Dynamics GP End of Life 2029: A Practical Migration Roadmap to Business Central]]></description><link>https://alphavima365.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6a5e1010be019cc793a9af56/8bb047d0-0ce8-41c8-9d3b-e0c7d2dfe6d5.png</url><title>&quot;Dynamics GP End of Life 2029: A Practical Migration Roadmap to Business Central</title><link>https://alphavima365.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 18:01:06 GMT</lastBuildDate><atom:link href="https://alphavima365.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Dynamics GP End of Life 2029: A Practical Migration Roadmap to Business Central]]></title><description><![CDATA[GP support ends Dec 2029. A practical, community-informed roadmap to migrate to Business Central — what breaks and how to plan for it.]]></description><link>https://alphavima365.hashnode.dev/dynamics-gp-end-of-life-2029-a-practical-migration-roadmap-to-business-central</link><guid isPermaLink="true">https://alphavima365.hashnode.dev/dynamics-gp-end-of-life-2029-a-practical-migration-roadmap-to-business-central</guid><category><![CDATA[Microsoft]]></category><category><![CDATA[Business Central]]></category><category><![CDATA[ERP Software]]></category><category><![CDATA[Dynamics 365]]></category><category><![CDATA[SaaS]]></category><category><![CDATA[Cloud Computing]]></category><dc:creator><![CDATA[Alphavima Technologies]]></dc:creator><pubDate>Mon, 20 Jul 2026 14:59:29 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a5e1010be019cc793a9af56/bf297e60-f7be-45a8-b7ef-bbcf7daddf49.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Dynamics GP has a firm expiration date now: mainstream support ends <strong>December 31, 2029</strong>, and security patches stop entirely on <strong>April 30, 2031</strong>. That sounds far away. But if you spend ten minutes in r/DynamicsGP or r/Dynamics365 right now, you'll see the mood is a lot less relaxed than the calendar suggests.</p>
<p>Controllers, IT managers, and consultants are all asking a version of the same question:</p>
<blockquote>
<p>"How bad is this actually going to be, and when should we start?"</p>
</blockquote>
<p>Having read through a stack of these threads (the honest ones, not the vendor pitches), here's the pattern I noticed: <strong>the deadline isn't the hard part. The hard part is that most teams underestimate what a GP-to-BC move actually involves.</strong> That mismatch - expectation vs. reality - is where projects go sideways.</p>
<p>This post is my attempt to organize what real GP users are actually saying into something you can use to plan your own move.</p>
<hr />
<h2>Why "migration" is the wrong word</h2>
<p>Almost every experienced voice in these threads said some version of the same thing. One comment stuck with me:</p>
<blockquote>
<p>"Moving off of GP to another tool is not a migration, it's an implementation. ERP implementations are never easy."</p>
</blockquote>
<p>That distinction isn't just semantics - it changes how you should budget and staff the project. If your leadership team is picturing a weekend cutover with a script that copies your data across, they're going to be blindsided later.</p>
<p>Set this expectation on day one:</p>
<ul>
<li><p>This is a full implementation project, not a data copy job.</p>
</li>
<li><p>It touches finance, reporting, payroll, and end-user workflows - not just the database.</p>
</li>
<li><p>Realistic timelines run <strong>12–18 months</strong> from decision to go-live once you include planning, cleanup, testing, and training.</p>
</li>
</ul>
<hr />
<h2>The 5 things that actually break during a GP → BC move</h2>
<p>Forget the marketing checklists. Here's what real migration stories keep flagging as the friction points:</p>
<ul>
<li><p><strong>Chart of accounts &amp; segments.</strong> GP's segmented account structure has no direct 1:1 match in Business Central, which uses <em>dimensions</em> instead. You can't copy this over - you have to redesign how you track cost centers, departments, and locations.</p>
</li>
<li><p><strong>Custom reports.</strong> Anything built in Management Reporter, FRx, or SmartList does not transfer. It has to be rebuilt in Jet Reports or Power BI. This is the most underestimated line item in almost every migration budget - a decade of "just one more custom report" requests adds up fast.</p>
</li>
<li><p><strong>Payroll.</strong> Business Central doesn't include native payroll in most regions. If you run GP payroll, you need a third-party add-on selected and implemented as part of the same project - not bolted on afterward.</p>
</li>
<li><p><strong>Historical data depth.</strong> Full transaction history rarely migrates cleanly beyond a certain point. Most successful projects bring over clean master data plus <strong>1–3 years</strong> of transactional history, and keep the old GP database in read-only mode for older audit/tax lookups.</p>
</li>
<li><p><strong>Third-party ISV add-ons.</strong> Whatever GP add-ons you depend on almost certainly won't carry over directly. The good news: most popular GP ISV tools have equivalents on Microsoft AppSource for BC - but you need to identify these early, not discover the gap during UAT.</p>
</li>
</ul>
<hr />
<h2>The part nobody budgets for: change management</h2>
<p>One thread had a genuinely painful story about voided checks and workflow confusion after a system switch - a good reminder that even a technically clean migration can still trip over the human side.</p>
<p>Teams that handled this well, based on what people shared, all did roughly the same three things:</p>
<ul>
<li><p>Ran GP and BC <strong>in parallel</strong> for a few weeks before full cutover, so users could validate their own transactions in both systems.</p>
</li>
<li><p>Identified internal <strong>"super users"</strong> early and trained them ahead of everyone else.</p>
</li>
<li><p>Avoided going live during <strong>month-end or year-end close</strong> - obvious in hindsight, painfully common in practice.</p>
</li>
</ul>
<hr />
<h2>Should you migrate now, or wait?</h2>
<p>This came up in nearly every thread, and the answer - even from people not trying to sell anything - was consistent:</p>
<table>
<thead>
<tr>
<th>Situation</th>
<th>Recommendation</th>
</tr>
</thead>
<tbody><tr>
<td>Heavily customized GP setup, still running fine</td>
<td>No panic - but start planning now</td>
</tr>
<tr>
<td>Approaching a hardware/OS refresh or GP version limits</td>
<td>Move sooner rather than later</td>
</tr>
<tr>
<td>Waiting until 2028–2029 to start</td>
<td>Risky - consultant availability and migration tooling will get tighter as the deadline nears</td>
</tr>
</tbody></table>
<p>The practical middle ground most consultants suggested: <strong>start your assessment and planning phase now</strong>, even if the actual technical migration doesn't begin for another year.</p>
<hr />
<h2>A realistic 90-day starting checklist</h2>
<p>Before any data migration work begins, focus on groundwork:</p>
<ul>
<li><p>Run a proper <strong>gap analysis</strong> between your current GP configuration and BC's out-of-box functionality.</p>
</li>
<li><p>Catalogue <strong>every custom report and third-party add-on</strong> currently in use - nothing should be discovered mid-project.</p>
</li>
<li><p>Decide how much <strong>historical transaction data</strong> you actually need live in BC vs. what can stay archived in read-only GP.</p>
</li>
<li><p>Identify your <strong>internal super users</strong> who will validate the new system and train colleagues later.</p>
</li>
</ul>
<p>Get these four things right before signing a statement of work with any implementation partner, and you'll save more time and money than any amount of technical cleverness during the actual migration.</p>
<hr />
<h2>Where to go deeper</h2>
<p>This post deliberately focused on the community-sourced planning mindset - the stuff most vendor content skips. For the harder numbers (realistic cost ranges by company size, which GP versions support Microsoft's built-in migration tool vs. need a manual approach, and how BC handles multi-company scenarios), we've laid it out in detail in our <a href="https://alphavima.com/blog/dynamics-gp-to-business-central-migration/">Dynamics GP to Business Central migration guide</a>.</p>
<p>If you're past the research stage and thinking about actually scoping a project, our <a href="https://alphavima.com/services/erp-consulting/">ERP consulting and Business Central implementation services</a> page walks through how we structure these engagements - including the gap-analysis phase discussed above.</p>
<p>And since custom report rebuilding is consistently one of the most underestimated parts of these projects, it's worth seeing how Business Central's native Power BI integration compares to what most GP shops are used to - covered on our <a href="https://alphavima.com/services/data-engineering-services/">data engineering and reporting services page</a>.</p>
<hr />
<h2>FAQ</h2>
<p><strong>When does Dynamics GP officially lose support?</strong> Mainstream support ends December 31, 2029. Security patches continue until April 30, 2031.</p>
<p><strong>Is this a migration or a full implementation?</strong> Functionally, it's an implementation — expect chart-of-accounts redesign, report rebuilding, and change management, not just a one-time data transfer.</p>
<p><strong>Can I keep historical GP data accessible after moving to BC?</strong> Yes. Most companies migrate 1–3 years of transactional history into BC and keep the old GP database in read-only mode for older lookups.</p>
<p><strong>What's the biggest thing teams underestimate?</strong> Custom report rebuilding (Management Reporter, FRx, and SmartList reports don't transfer) and the change management effort for end users.</p>
<hr />
<p>If you're mapping out a GP-to-Business-Central transition and want a second opinion on scope or timeline before committing to a project plan, <a href="https://alphavima.com/book-a-call/">Alphavima</a> offers a free consultation to walk through your specific GP setup.</p>
]]></content:encoded></item></channel></rss>