Dynamics 365
Dynamics 365 Supply Chain Management
Planning, inventory, warehouse and production execution, with availability that reflects what is physically there.
Manufacturing · Strategy & Transformation
A meat producer that decided to become a technology company
A large food production business, United States. Ageing on-premises systems required constant monitoring and carried cybersecurity risk, but the manufacturing and shipping schedule left no room for disruption during a replacement.
The situation
What the organization was dealing with
Ageing on-premises systems required constant monitoring and carried cybersecurity risk, but the manufacturing and shipping schedule left no room for disruption during a replacement.
Food production runs on a schedule that does not pause for an ERP migration. That constraint shapes everything about how such a project can be sequenced.
What was done
The work, and the part that was actually hard
Leadership committed to a full move to Dynamics 365 Supply Chain Management and Finance with a partner, with a critical goal of completing upgrade, testing, integration and cutover without disrupting the rhythm of business.
The stated goal — complete the upgrade, testing, integration and cutover with no disruption to the rhythm of business — is the right success criterion and an uncommon one to state explicitly. Three hundred users across offices, warehouses and manufacturing going live together is an aggressive scope for that constraint.
Results
What was published
These are the figures exactly as reported in the source. Nothing has been rounded, extrapolated or restated.
Users live at go-live300+
Disruption to production0
Centralised data platform1
What changed
- More than 300 users across offices, warehouses and manufacturing live on the new platform
- Cutover completed without disrupting manufacturing and shipping
- Cybersecurity risk of ageing on-premises systems removed
- Warehouse, manufacturing and financial operations modernised together
Platforms involved
What each product was doing here
Dynamics 365
Dynamics 365 Finance
Financial management, cost accounting and close automation across entities and currencies.
What transfers
If you were to attempt this
Writing the no-disruption requirement into the success criteria, rather than assuming it, changes how the plan is built.
Where it usually gets harder than expected: The security motivation is worth noting: ageing on-premises systems were a stated risk. Migration business cases built only on features tend to lose to 'it still works'.
How we would take it on
Our approach to Strategy & Transformation work
1
Establish the real baseline
We measure what the current estate actually costs to run and what it prevents, before anyone proposes a target state.
2
Agree the outcomes in writing
The measures, the definitions and the method — settled with the executive team before design begins rather than argued about at the end.
3
Sequence by payback
Phase one is scoped to prove itself before phase two is commissioned. Long programmes that produce nothing for a year lose their sponsor before they finish.
4
Keep the option to stop
Each phase ends at a decision point with the evidence to make it. Continuing to protect a decision already made is an expensive habit.
Recognise the problem?
If any of the above describes your organization, tell us where it hurts most. We will tell you what the same platforms could realistically do in your environment, what we would measure, and whether we think it is worth doing at all.
Talk to our teamMore Strategy & Transformation storiesWe reply to every message within one business day.
Related reports