D365ConsultantDivision of Sataware
D365ConsultantDivision of Sataware
Peace Garden State

A Business Central consultant for North Dakota, where Dynamics GP was born.

Any Business Central consultant in North Dakota soon notices how many local companies still run Dynamics GP. That is no accident: Great Plains Software started in Fargo, Microsoft bought it, and Microsoft still keeps a large campus there. Today those same GP customers face a move, and Microsoft Dynamics 365 Business Central is the natural destination. We help North Dakota manufacturers, agricultural businesses, energy service firms and distributors make that move, remotely from Phoenix with visits when useful.

Two time zones
Central across most of the state, Mountain in the southwest
GP heritage
Great Plains began in Fargo
Remote delivery
site days by agreement
Layered badlands buttes in Theodore Roosevelt National Park, North Dakota

From Great Plains to Business Central

Dynamics GP has served North Dakota businesses well, and many local finance teams know it deeply. The problem is not that GP stopped working. It is that Microsoft has announced an end to its support, the pool of GP developers is shrinking, and the add-ons many companies depend on have their own uncertain futures. Business Central runs in Microsoft's cloud, updates twice a year, and keeps extensions separate from the core so upgrades stop being projects.

A GP move is not a copy. GP's account segments usually become a main account plus dimensions in Business Central, which gives cleaner reporting but needs a mapping decision for every segment. Fixed assets, payables and receivables open items, and inventory quantities move; years of detailed GP history often stay in an archive or a reporting database instead. We make those choices with you early, because they shape the rest of the project.

How GP pieces map to Business Central

In Dynamics GP
In Business Central
What to decide
Account segments
G/L account plus global and shortcut dimensions
Which segments stay in the account number and which become dimensions
Payables and receivables
Vendor and customer ledgers with open entries
Whether to bring paid history or only open items
Inventory sites
Locations, optionally with bins
Whether warehouse handling documents are needed
Manufacturing
Production BOMs, routings and production orders
Premium edition required for production orders
Third-party GP add-ons
Standard features, AppSource apps or small extensions
Which add-ons are still genuinely used

North Dakota sectors we plan for

Equipment

Agricultural machinery makers

Fabricators and equipment builders in the Red River Valley run make-to-order work, carry large spare parts catalogs and sell through dealers.

  • โœ“Production orders
  • โœ“Service items
  • โœ“Dealer pricing
Grain

Growers, elevators and processors

Wheat, soybean, canola and sunflower businesses buy and sell commodities, and processors track lots from intake to shipment.

  • โœ“Lot tracking
  • โœ“Purchase contracts
  • โœ“Item charges
Energy

Bakken oilfield services

Service companies in the western counties bill by job and field ticket and move equipment between yards.

  • โœ“Jobs and tasks
  • โœ“Fixed assets
  • โœ“Location transfers
Trade

Wholesale distributors

Distributors in Fargo, Bismarck and Grand Forks serve a wide rural territory with their own delivery routes.

  • โœ“Multiple locations
  • โœ“Shipping agents
  • โœ“Customer price groups

Practical notes for a North Dakota project

  • โœ“Most of the state is on Central Time and a southwestern portion is on Mountain Time, so we schedule with each site's clock in mind
  • โœ“North Dakota sales tax is administered by the Office of State Tax Commissioner, with city and county rates layered on top, which maps to Business Central tax areas
  • โœ“Seasonal peaks at planting and harvest shape the go-live date for agricultural businesses more than the calendar year end
  • โœ“Rural connectivity at yards and elevators matters, so we check that the browser and mobile apps perform at each site before cutover
  • โœ“Many GP users run payroll inside GP, and Business Central has no US payroll module, so we plan a payroll provider link early
  • โœ“Companies with Canadian customers or suppliers can use Business Central's multi-currency features for invoices and payments in Canadian dollars

What North Dakota companies want to know

Why not just stay on Dynamics GP?

You can for now, but the runway is limited. Microsoft has published an end of support timeline for GP, and after that date security updates and tax updates stop. Moving on your own schedule lets you pick a quiet season and clean up data first. Waiting tends to compress the project into a rush.

What happens to our GP payroll?

Business Central does not include US payroll, so payroll moves to a dedicated provider. Many companies choose a service that exports a journal file or connects through an integration, such as an ADP integration. We design the posting so payroll lands in the right accounts and dimensions. Planning this early avoids a gap at year end.

Do you come to Fargo or Bismarck?

When the scope calls for it, yes. Our office is in Phoenix and nearly all workshops run by video, which suits the distances inside North Dakota anyway. We recommend on-site days for warehouse and shop floor walkthroughs and for training a room of users before go-live. Those days are listed in the written scope.

How long does a GP to Business Central migration take?

It depends on your modules, data quality and integrations, so we answer that in the written plan rather than here. The biggest drivers are how many GP add-ons you use and how much history you want to keep. A scoping conversation sets a realistic schedule. Our GP migration page walks through the stages.

Talk to us about your project.

Tell us what you run today and what has to change. A senior consultant replies with a written next step.

Get started

Start with a scoping conversation.

Thirty minutes with a senior consultant - not a sales call. We look at how you run today, tell you plainly whether Business Central is the right fit, and give you an honest sense of scope, cost and timeline before you commit to anything.

What happens next
1
We review your enquiry
A consultant reads it before the call - no discovery questionnaire to fill in.
2
30-minute scoping call
Your processes, your current systems, and the gaps that matter most.
3
Written summary & estimate
Indicative phases, licence counts and a cost range, in writing within three days.
Reply within one business day
NDA signed before discovery on request
No obligation, no cost for the scoping call
Microsoft-certified consultants only
Request your scoping call
Four fields. A consultant replies within one business day.
No cost
Your details stay with our consulting team - never shared, never added to a mailing list.