/
.webp)
There is a particular kind of cold that settles over Fargo in January — not the dramatic, postcard cold of the Rockies, but a flat, relentless, wind-driven cold that comes down out of Canada and has nowhere to go because there is nothing between you and the Arctic Circle but wheat fields and stubbornness. It is, by almost any measure, one of the last places on earth you would choose to build a technology empire.
Doug Burgum chose it anyway.
In the spring of 1983, Burgum was twenty-six years old, freshly minted with an MBA from Stanford, and working as a management consultant at McKinsey in Chicago. He had a future that looked, from the outside, perfectly predictable: partner track, corner office, the quiet accumulation of someone else's money. Instead, he mortgaged $250,000 worth of inherited farmland — his family's land, the kind of asset you do not gamble with in North Dakota — and flew to Fargo to buy a stake in a small accounting software company called Great Plains Software.
The company had eleven employees. It was operating out of a converted building in a city that most of America associated with a Coen Brothers film that hadn't been made yet. The idea was to build accounting software for small and medium-sized businesses — not glamorous, not visionary in the way that Silicon Valley defined vision, just deeply, stubbornly useful.
Twenty years later, Microsoft would pay $1.1 billion for it.
And the man who built it would eventually become the Governor of North Dakota, a Republican presidential candidate, and the United States Secretary of the Interior.
But none of that was visible in 1983. In 1983, there was just the cold, and the code, and the stubborn bet that useful software, built by unglamorous people in an unglamorous place, was worth something.
The question is not just geographic. It is cultural.
Doug Burgum grew up in Arthur, North Dakota — a town of fewer than 400 people, the kind of place where everyone is one bad harvest from understanding exactly what risk means. His family farmed. He attended North Dakota State University, which in the late 1970s was not producing future technology CEOs by design. He was smart enough to get to Stanford, ambitious enough to get through it, and practical enough to take the McKinsey job. The standard trajectory of a smart Midwestern kid who made it out.
But Burgum never fully made it out. Or rather — he chose not to. When two NDSU computer science graduates named Joseph Larson and James Turner had incorporated Great Plains Software as a division of Great Plains Computers two years earlier, they were solving a real problem: small businesses needed accounting software that actually worked on the new personal computers that were arriving on desks across America. Mainframes were for corporations. Minis were for universities. The personal computer was for everyone else, and everyone else needed to track their money.
Great Plains Software did that. It was not beautiful. It was not inspired. It worked.
When Burgum arrived in 1983 and bought his 2.5% stake, then spent the next year quietly acquiring the rest of the company, he understood something fundamental about the software business that many Silicon Valley founders never grasped: the accountants, the small manufacturers, the mid-sized distributors — these were not sexy customers. They were also not going anywhere. They needed their books. They needed their payroll. They would pay for software that did those things reliably, year after year, and they would become fiercely loyal to it if you served them well.
Burgum built the company around that loyalty. He instituted a customer service culture that was unusual for software in the 1980s — all customer service reps had four-year college degrees, a third of all employees worked in service, and the company measured itself obsessively on how well it took care of partners and clients. He was not building a product; he was building a relationship business that happened to use software as the medium.
He also understood why Fargo worked for this. North Dakota State University was a reliable pipeline of engineering talent. The cost of living was low. The people were, as Burgum often put it, humble and hardworking in a way that translated directly into service culture. "Every farmer and rancher is an entrepreneur and tinkerer and inventor," he would say. There was pioneering spirit in the region's DNA — not the performative disruption of the Bay Area, but something quieter and more durable.
Great Plains Software was Fargo's answer to Silicon Valley: built on utility, not mythology.
By 1989, Great Plains had 250 employees. By 1990, it was doing $22 million in annual revenue. These are not tech-boom numbers. They are the numbers of a company that grew by selling a product to people who needed it, in markets that nobody at Sand Hill Road was excited about.
The company survived the brutal competitive dynamics of the 1980s accounting software wars — Peachtree, ACCPAC, MAS 90, and dozens of others were fighting for the same customers. Great Plains differentiated on two things: the depth of its partner channel (it sold almost exclusively through certified resellers, building a network of small businesses who staked their own livelihoods on the product) and the quality of its service.
The 1990s changed things. The internet arrived and Burgum understood earlier than most that it was a distribution engine, not just a communication tool. He used it to extend the company's reach beyond the Midwest, selling into markets that had never heard of Fargo and didn't need to. The software was the product. Fargo was irrelevant to anyone who wasn't standing in it.
By 1997, Great Plains Software was ready to go public. The IPO landed on a market that was beginning its euphoric ascent toward the dot-com peak. Shares priced at $16 and promptly doubled. The company raised over $50 million. Suddenly, a software company in Fargo, North Dakota was a publicly traded entity with a market cap that made the local newspaper feel like it was reporting from a different planet.
Then came Solomon.
In June 2000, at the peak of the dot-com bubble, Great Plains acquired Solomon Software — a smaller ERP company that had carved out a niche in project accounting for professional services firms. Solomon brought a different user base, different architecture, and a different culture. Great Plains now had two products, two sets of customers, and the beginning of what would become a recurring challenge: integration without alienation.
They never had to solve it. Six months later, Microsoft called.
The announcement came on December 21, 2000 — not the most auspicious date to announce the largest acquisition of Microsoft's workforce to date, with the dot-com bubble already beginning to deflate and markets twitching with anxiety. But the logic was sound: Microsoft had built its empire on the desktop and was now watching enterprises spend money on software it didn't make. SAP, Oracle, PeopleSoft — these were the names in ERP. Microsoft was absent.
Great Plains was the beachhead.
The personal connection mattered. Doug Burgum had spent his last quarter at Stanford on a project team with Steve Ballmer. Two decades later, Ballmer was Microsoft's CEO and Burgum's old classmate was writing a $1.1 billion check — paid in Microsoft stock — to bring Great Plains and its 2,200 employees into the fold. It was the largest acquisition of personnel Microsoft had ever executed. The Visio acquisition the year before had cost $1.3 billion and delivered 15 people. Great Plains cost $1.1 billion and delivered the institutional knowledge of an entire industry.
The deal closed April 5, 2001. Burgum became Senior Vice President of Microsoft Business Solutions, the new division built around Great Plains. Fargo got a Microsoft campus. The employees got Microsoft stock options. The customers got… complicated.
Because Microsoft was not done shopping.
Fourteen months later, in July 2002, Microsoft announced the acquisition of Navision A/S — a Danish software company — for $1.45 billion, the largest acquisition Microsoft had ever made until that point. Navision had been founded in 1984 in Copenhagen as PC&C (Personal Computing and Consulting) by three entrepreneurs, released its first accounting product in 1985, and spent the next fifteen years quietly building the dominant ERP presence across Europe, particularly in Scandinavia and Germany.
But Navision had also, in 2000, merged with a rival Danish company called Damgaard A/S — itself founded in 1983 and famous for an ERP product called Axapta, a more sophisticated, enterprise-oriented system that competed in the upper mid-market. The merger created a combined company that Microsoft could acquire in a single transaction. And so in one move, Microsoft picked up three distinct ERP systems: Navision (Attain), Damgaard's Axapta, and Navision's own C5 product for smaller businesses.
Combined with Great Plains and Solomon, Microsoft now had four full ERP systems. Different architectures. Different programming languages. Different user communities. Different cultures.
Four separate software lineages, written by four different sets of engineers, for four different types of customers, in two different countries. And Microsoft, optimistically, named all of them "Microsoft Dynamics."
Microsoft's plan was ambitious. Internally, it was called Project Green.
The vision: take the four acquired ERP systems and migrate them all toward a single, unified codebase built on Microsoft technology. One ERP to rule them all. One platform, one architecture, one future. It was the kind of grand synthesis that makes perfect sense on a whiteboard in Redmond and breaks apart on contact with the ground-level reality of 140,000 businesses that have spent years building their operations around your software and are not excited about a forced migration.
By 2004, Burgum himself was acknowledging the retreat. Developer headcount on Project Green had been cut from 200 to 70. By 2005, the project was quietly redefined: instead of a unified codebase, Microsoft would incrementally update each product separately. Project Green died. The four products lived on.
Microsoft simply rebranded them:
- Great Plains became Dynamics GP
- Navision became Dynamics NAV
- Axapta became Dynamics AX
- Solomon became Dynamics SL
Same software. New label. The problems didn't change with the name.
The GP user base — small to mid-sized manufacturers, distributors, nonprofits — had no meaningful path to AX. The NAV user base — European mid-market companies, often with strong local partner networks — had no reason to consider GP. AX sat above both, nominally targeting enterprise customers, but awkwardly sized compared to SAP or Oracle. SL quietly served project-based businesses and hoped nobody noticed.
Microsoft spent the next decade managing what it could not fully unify. They invested, separately, in each product. They updated each product. They marketed all of them under the same Dynamics banner. But the banner was a fiction — underneath it were four distinct product families with four distinct implementation ecosystems, four sets of certified partners, and four communities of customers who had no particular interest in crossing the borders Microsoft had drawn.
The 2016 rebrand — Dynamics 365 — was Microsoft's second attempt at coherence. This time, the strategy was cloud-first: move everything to Azure, build a unified data layer, wrap it in a subscription model, and create a platform story that could compete with Salesforce in CRM and SAP in ERP simultaneously. Dynamics 365 launched in November 2016 with separate applications — Sales, Customer Service, Field Service, Finance, Supply Chain Management, Business Central — that could theoretically snap together like Lego bricks.
The bricks don't always snap cleanly. But the strategy is more honest than Project Green was. Rather than pretending the four products could become one, Microsoft accepted the pluralism and tried to make it feel like a feature. Business Central (the cloud successor to NAV) became the flagship for the mid-market. Finance and Operations (the cloud successor to AX) handles enterprise customers. GP and SL — the old Great Plains and Solomon products, the ones that started everything — are being wound down. Microsoft announced in 2022 that Dynamics GP would be retired. The end-of-life date is December 31, 2029.
In 2029, Great Plains Software will die, officially. The software that Doug Burgum mortgaged his family's farmland to build, the software that 140,000 businesses trusted with their books, will stop receiving updates. The ghost of Fargo will be migrated, awkwardly and expensively, to Business Central — which is what Navision became, which means the Danish company that Microsoft bought after Great Plains will ultimately outlive it.
The irony is complete.
Today, Microsoft Dynamics 365 is a quiet colossus. The platform generates over $7 billion in annual revenue and is growing at roughly 19% year-over-year. By ERP revenue alone — an estimated $5.4 billion in 2024 — Dynamics ranks third in the world, behind Oracle and SAP. In CRM, it competes directly with Salesforce, holding roughly 7-8% of the global market against Salesforce's 21%.
It is not the dominant platform in any single category. But few platforms span as many categories — financial management, supply chain, sales, customer service, marketing, field service, human resources, commerce — while remaining plugged into the same ecosystem: Azure, Teams, Power BI, Power Automate, Copilot. The integration story is what Microsoft has always been selling. Whether customers buy it is a different question.
And the man who started it all is no longer in the software business.
Doug Burgum left Microsoft in 2007, spent years angel investing in tech companies, and in 2016 did something that surprised nearly everyone who knew him: he ran for governor. He had no political experience. He lost the state Republican party's endorsement to the longtime attorney general. He beat that attorney general anyway, in the primary, then won the general election with over 75% of the vote.
He served two terms as governor of North Dakota. In 2023, he briefly ran for president of the United States. He didn't win, but he used his brief moment on the debate stage to — famously, and somewhat endearingly — offer a $20 gift card to anyone who could prove he was actually speaking, in an attempt to get people to download his campaign app.
In January 2025, he was confirmed by the United States Senate, 79-18, as the 55th Secretary of the Interior under President Donald Trump. The farmer's grandson who mortgaged his land to buy accounting software now oversees 500 million acres of federal land and the energy policy of the most powerful country on earth.
Great Plains Software begat Microsoft Dynamics. Microsoft Dynamics begat a billionaire. The billionaire became a governor. The governor became a cabinet secretary.
Fargo to Washington, through Redmond. The flattest possible route to the top.
Most people who use Dynamics GP to run their accounting have no idea that the person who built the original Great Plains Software is Doug Burgum, who spent 2023 running for President of the United States and is now the 55th Secretary of the Interior under Donald Trump. He oversees federal land, energy extraction, and national parks. He got there from Fargo. Via Redmond. The founder of a mid-market ERP company is now one of the most powerful appointees in the federal government.
When people talk about the Navision acquisition, they usually miss the detail that makes it interesting: Navision had just merged with Damgaard A/S — another Danish ERP company — in 2000, before Microsoft bought the combined entity in 2002 for $1.45 billion. Damgaard made Axapta. So Microsoft paid for Navision and got Axapta as part of the deal. Two products, two architectures, two user bases, one check. This is the moment the four-headed hydra problem was born: Microsoft was buying whole genealogies of software, not just products.
"Project Green" was the internal codename for Microsoft's plan to merge Great Plains, Navision, Axapta, and Solomon into a single codebase. It started in 2003, was presented as the future of enterprise software, and by 2004 was already being dismantled. Developer headcount was cut from 200 to 70. The plan was quietly reframed as "incremental enhancement" of existing products. In 2006, Microsoft stopped using the Project Green name entirely. The four products were simply rebranded as Dynamics AX, GP, NAV, and SL — the same four architectures, the same four user communities, the same four support organizations. The unification never happened. It still hasn't.
Great Plains — the original American heart of Microsoft Dynamics, the software that 140,000 businesses trusted, the product that cost $1.1 billion — is being retired. Microsoft's end-of-life date for Dynamics GP is December 31, 2029. The migration path they're recommending is Business Central, which is the cloud evolution of Navision, the Danish product they bought later, for more money. In the long tournament of Microsoft ERP products, Fargo loses to Copenhagen. The American blue-collar accounting software gets sunset; the Scandinavian platform becomes the future. This is not how the story was supposed to go.
Microsoft Dynamics 365 is playing in two of the largest software markets in the world at the same time. In ERP, it's the third-largest vendor by revenue behind Oracle and SAP, with an estimated $5.4 billion in 2024. In CRM, it's the fastest-growing challenger to Salesforce — which still owns 21% of the global market versus Dynamics' 7-8%. No other vendor tries to win both fights simultaneously. The reason Microsoft can attempt this is Azure: both Dynamics ERP and Dynamics CRM run on the same cloud infrastructure, connected to the same identity layer (Entra), the same BI layer (Power BI), and increasingly the same AI layer (Copilot). The integration story is the actual product. Not GP, not NAV, not AX — Microsoft. That is both the company's greatest strength in Dynamics and the reason the individual products have always felt secondary to the platform they live on.
Sources used in research: Microsoft Press Releases (news.microsoft.com), Wikipedia (Great Plains Software, Microsoft Dynamics, Doug Burgum), InForum (Fargo), Fortune, CFO.com, Computerworld, Integrity Data, SoftwareConnect, Rand Group, ClientsFirst, Nigel Frank International, Sterling Team, Navision Planet, Hans Peter Bech, Binary Stream, Enavate, Learn.Microsoft.com
