Notes on ERP rollouts for mid-sized businesses
5 posts, most recently September 2026
Most recently written.
Cutover without downtime: switching while the business keeps runningThe switchover date is the riskiest hour of an ERP project. Break it into stages and there is a way back at every point.
From your legacy system to ERPNext without stopping the businessA cutover is not a date, it is an order of operations. What moves first decides how expensive a mistake gets.
Where automation really saves time, and where it just moves the workAn automated detour is still a detour. The question is not what can be automated, but what should exist at all.
What ERPNext covers out of the box, and where customisation startsThe feature list is rarely the problem. The interesting part is where the standard ends and what that means for your project.
Why one area goes live first and the rest waitsA system that can do everything but nobody uses costs more than none. The first area in production decides whether the project earns trust.