Not ready to leave GP? You don't have to.
Dynamics GP has run your finances for fifteen years and it still works. Microsoft's clock is running, but a migration is a decision for later — not a reason to keep hand-keying AP now. Harold reads, validates and maps your invoices into GP-ready data today.
Why GP is still running your business
Dynamics GP has been in the field for decades, and the companies still on it are not there through neglect. They're there because it does the job.
It is configured to your business
Fifteen or twenty years of chart of accounts, SmartLists, custom reports and workflow that fit exactly how your finance team works. That configuration is an asset, and it does not transfer.
Your team knows it cold
No retraining budget, no productivity dip, no month-end where nobody is quite sure whether the numbers are right. Institutional knowledge has real value on the balance sheet even though it never appears there.
It runs on your terms
On-premise, predictable, no forced update cycle changing a screen your team relies on halfway through a close.
The reporting is already built
Every report your business depends on has been written, tested and trusted. Rebuilding that library is one of the largest hidden costs in any migration.
The countdown is real — the panic isn't warranted
Microsoft stopped selling new perpetual licences for Dynamics GP in April 2025 and new subscription licences in April 2026. Support for product enhancements, tax updates and technical support ends on 31 December 2029, with security updates available until 30 April 2031.
Those dates matter, and you should plan for them. But 2029 is not 2026, and a rushed migration is more dangerous than a considered one. In the meantime, GP keeps posting invoices correctly — it just needs somebody to type them in first, because GP has no native document capture and never did.
The mistake is to treat the data-entry problem and the migration decision as the same decision. They aren't. One is urgent and cheap to fix. The other is expensive and can wait until you're ready.
Fix the keystrokes now, decide the platform later
Spending on a full AP automation suite that only connects to GP is money you write off at migration. Spending eighteen months on an early migration you weren't ready for is worse. Neither is necessary.
Harold produces validated, mapped data — not a GP-shaped integration you have to unpick later. When you do eventually move to Business Central, Acumatica, NetSuite or anywhere else, you change the output mapping and the supplier training carries across. The work you do today isn't stranded on a platform you're leaving.
That's the point of putting the automation outside the ERP rather than inside it.
How Harold works with Dynamics GP
Train Harold on your suppliers
Upload a handful of invoices per supplier. Harold learns the layout and where each value sits. Under ten minutes per supplier, and it holds for every invoice that supplier sends afterwards.
Validation and coding before import
Harold recalculates totals, checks tax, matches supplier and GL accounts against your own GP reference data, and flags exceptions. What reaches GP is already coded and reconciled.
Import-ready output for GP
Harold produces a validated file in the format your payables import expects. No add-in installed into GP, no changes to a system you're eventually leaving anyway.
Why Dynamics GP users choose Harold
Nothing installed into GP
No add-in, no dictionary changes, no version dependency. On a system approaching end of support, adding nothing to it is a feature.
Portable to whatever comes next
Your supplier training and validation rules live in Harold, not in GP. When you migrate, you remap the output and keep everything else.
Coded, not just captured
Harold matches supplier and nominal codes to your own reference data. You get a posting-ready record, not raw OCR text somebody still has to code.
Free to start, no paywall
Full features from day one, no credit card. Prove it on your worst supplier before committing anything.
Common questions
When exactly does Dynamics GP support end?
Microsoft has confirmed 31 December 2029 for the end of product enhancements, regulatory and tax updates and technical support, with security updates available until 30 April 2031. New perpetual licence sales ended in April 2025 and new subscription licences in April 2026.
Should we migrate now instead of automating AP?
Those are separate decisions. Migration planning typically runs twelve to eighteen months and should be done properly. Hand-keying invoices for the next three years while you plan it is a choice you don't have to make.
Does Harold install anything into GP?
No. Harold sits outside GP entirely and produces a validated import file. Nothing is added to your GP installation and nothing has to be removed later.
What happens to our setup when we do migrate?
Your supplier templates and validation rules stay in Harold. You change the output mapping to match the new system and carry on — the training doesn't have to be redone.
Keep Dynamics GP. Lose the data entry.
Start free, no credit card required. Train Harold on one supplier and see the output before you spend anything.
Try Harold free