Skip to Content

Why November Is the Month to Plan Your 2027 ERP Move

Planning an ERP move in 2027? Use November to decide what needs to change and prepare for a realistic go-live

Around November, a familiar conversation comes up in boardrooms and back offices across South Africa. Someone says, “Next year, we really need to sort out our systems.” Everyone agrees. Then December arrives, January is spent catching up, and by March the business is still running on the same spreadsheets it promised to leave behind.

The intention was real. What was missing was a plan to turn it into action.

For a growing business where month-end means chasing three people for numbers, and stock lives in one system while invoices live in another, that delay keeps the same problems in play. So instead of another reminder to “digitise”, we want to answer one practical question: what can you do now to make an ERP move in 2027 more realistic?


The timing problem nobody talks about


When businesses think about ERP, they tend to think about the go-live date: the day the new system switches on. What they don’t always see is everything that needs to happen before that day.

Requirements need to be understood. Current processes need to be mapped, including the workarounds nobody has written down. Data needs to be cleaned up, because moving messy data into a new system just gives you messy data in a nicer interface. Decisions need to be made about which modules come first, who needs access to what, and how the team will be trained.

Some of that work is straightforward. Some, like reconciling opening balances or testing how an order moves from sale to dispatch and invoicing, takes time and input from people who are already busy.


Why November works


November sits in a useful spot on the calendar. You’ve had most of the year to see where the pain points are, and if next year’s budget is still being discussed, there’s a natural moment to make the case for change. There may also be time to get the right people together before festive leave or peak trading takes over.

Start the conversation now and you can come back in January with priorities, an owner and a next step. If December is your busiest month, that may be all you need to agree before the break.


What good planning actually looks like


Planning an ERP move doesn’t mean committing to a full project before Christmas. It means getting clear on three things.


Start with the problems, not the software

Which tasks take far longer than they should? Where do errors keep appearing? Which reports are hardest to produce? These answers shape everything that follows.


Look honestly at your data

How many places does your customer, stock and financial information live? What needs to move, what can stay accessible for reference, and who will check that the migrated records are right? Finding those answers early gives you a better idea of the work involved.


Decide who owns it

Who will lead the project inside the business? An ERP project moves faster when someone internal has the time and authority to make decisions and keep it moving.


It can move faster than you think


It’s easy to put off ERP if you picture a project that takes years. A focused first phase can move much faster when the scope is clear, the data is ready and the team has time to make decisions and test.

Ask what really needs to go live on day one. A rollout covering core workflows will have a different timeline from one that also brings in multiple companies, complex integrations or years of transaction history

Professional Group, an aviation, logistics and operations business working across South Africa and Lesotho, moved from Oracle NetSuite to Odoo with Amplifi ERP and was live in 30 days. That kind of timeline doesn’t happen by accident. It happens because the groundwork was done properly before the switch.


Waiting for the right time usually means paying the cost of disconnected systems for another year.

Book an ERP Discovery Session Today

The real cost of waiting

Every month on disconnected systems has a cost, even if it never shows up as a line item. It’s the hours spent reconciling spreadsheets, the stock that was sold twice, the report that arrived too late to be useful, and the growth opportunity that felt like more admin than it was worth.


Frequently asked questions

How long does an ERP implementation take?

It depends on the scope, the systems you’re replacing, the state of your data and how quickly your team can make decisions and test. A focused first phase may take weeks; a more complex rollout needs more time. Agree what must work on day one before setting a date.

Do we need to commit before the end of the year?

No. November is for planning and conversations. Commitment comes once you understand the scope, the investment and the timeline.

What should we prepare before speaking to a partner?

A list of your current systems, the tasks that take the most time, and the reports you struggle to produce. That’s enough for a useful first conversation.

Where to start

You don’t need every answer in November. You just need to start asking the right questions while there’s still time to act on them. In an ERP Discovery Session, we’ll look at where your team is losing time and what would make sense to tackle first.


Book an ERP Discovery Session at amplifierp.com for a no-pressure conversation about starting 2027 on one system.


Book an ERP Discovery Session Today

Amplifi ERP is an official Odoo implementation partner in South Africa.