A lot of Dynamics GP and NAV customers are planning their move to Business Central right now. When we talk to them about ecommerce, we hear the same sentence almost every time:
"We'll deal with the website after the ERP project."
It sounds sensible. One big project at a time. In practice it usually means the webstore sits frozen for a year or two while customers keep emailing orders, and then the store project starts from scratch after go-live with a tired team and a spent budget.
There's a better order of operations.
Why the store keeps getting pushed back
The worry is that anything built against the old ERP will have to be rebuilt against the new one. If the store talks directly to GP or NAV, that's true. Every field mapping, every price rule, every order export is tied to the old system.
So the store gets parked, and the parking lot gets long. Microsoft ends support for current versions of Dynamics GP on December 31, 2029, so most GP shops have a few years, but not unlimited ones, and every one of them is a year of orders arriving by email.
Put a layer in between
The way around this is to stop connecting the store straight to the ERP. Put an integration layer in the middle that owns the handful of things the store needs:
- customers and their ship-to addresses
- items and availability
- customer-specific pricing
- orders going in, order status coming back
- invoices and open balances, if you have a portal
The store talks to the layer. The layer talks to the ERP. When you move from GP or NAV to Business Central, you rewrite the connection from the layer to the ERP. The store, the customer logins, the order history and the URLs your customers have bookmarked all stay put.
That turns "rebuild the store after the migration" into "swap one connector during the migration."
What this buys you
You can start now. The store or portal goes live on the ERP you have today. Your customers start reordering online within months instead of after go-live.
The migration gets a test case. Your web orders are a clean, repeatable stream of transactions. They're a good way to prove the new ERP handles pricing and order entry correctly before you cut over.
Your customers don't feel the cutover. If the layer queues orders while the ERP is down, a weekend migration is invisible to the people buying from you.
What to get right
Pricing logic stays in the ERP. Customer pricing in GP or NAV and price lists in Business Central don't map one to one. Read prices from the ERP through the layer instead of copying the rules into the website, or you'll be maintaining them in two places.
Item numbers may change. If the migration cleans up your item master, plan the cross-reference early so past orders still reorder correctly.
Don't make payments wait on the ERP. Card payments and order acceptance should work even when the ERP is unavailable, with orders posted when it's back. Never let a migration weekend become a weekend with no orders.
Agree who owns the layer. Your ERP partner is focused on the migration. Make sure someone owns the web side and the connection, and that both teams meet before the cutover plan is final.
Questions we hear
Should we wait until Business Central is live to start the webstore? No. Build on the ERP you run today and put an integration layer between the store and the ERP, so the move to Business Central replaces one connection instead of the whole store.
What changes in the store when the ERP changes? Very little, if the layer is in place. Customers, logins, order history and URLs stay the same. The work is in the connector and in mapping prices and item numbers to the new system.
Who should own the integration layer? Someone outside the migration team. Your ERP partner already has a full plate. Name an owner for the web side and the connection, and get both teams in the same room before the cutover plan is final.
The short version
Treat the ERP migration as the reason to build the webstore the right way. Connect it through a layer, go live on the system you have, and let the new ERP slot in underneath when it's ready.
We wrote up how this works on BigCommerce for and for .
Calvin Luttrell is the founder of ProjectThunder, a founded in 2004. The team has launched 150 B2B storefronts across Microsoft Dynamics, SAP and other ERPs, builds on Sana Commerce, BigCommerce and DynamicWeb, and works as a Sana-certified agency for storefront design alongside clients' ERP partners.
