Everything you need before you replace your ERP
Nine free tools. Work out what standing still costs you, catalogue what you have built, define what you need, build the case, and plan the switch.
Start here
Not sure where to start?
Four questions, about thirty seconds. We will point you at the three tools most useful for where you are. No email needed.
Question 1 of 4
What are you running now?
Question 2 of 4
Roughly how many people would use a new system?
Question 3 of 4
Where are you up to?
Question 4 of 4
When would you want to be live?
Nine tools, in the order you need them
Every page is free to read in full. The working files need an email address. The complete pack asks a few more questions so we send you the right things.
Total what your current system actually costs each year, including the staff time nobody invoices for, and set it against the cost of moving.
Catalogue everything built on top of your ERP, and find out how much of it anyone still uses. Most organisations are surprised.
Real cost ranges from delivered projects, and the six factors that move a project up or down the range.
Requirements by function and industry, already written and ready to edit. Records what your current system already does, so the list becomes a gap analysis.
The questions vendors hope you will not ask, with what a strong answer sounds like and what to watch out for.
For a formal process. Includes a prescribed commercial response format, so the pricing you get back can actually be compared.
The structure, the financial framing, and the questions boards actually ask. Unbranded, so it goes to your board as your document.
The presentation version, with speaker notes on every slide and a presenter-only slide of the questions to expect.
Checks across data, testing, parallel running, cutover and rollback, plus a runbook and a go or no go record.
Most ERP suppliers will not discuss cost until you are several meetings into a sales process. The tools they publish tend to be shaped around what their product happens to do well.
We took a different view. These tools are deliberately neutral. The requirements list is not modelled on any product, including the one we implement. The demo question bank includes the questions we would rather not be asked ourselves. The business case template works just as well if the case you build concludes you should stay where you are.
Buyers who understand what they are getting into make better decisions, and better customers. That is the whole argument.
Would you like us to talk you through how to use this toolkit? Book a quick 30-minute chat for us to run you through how to use it.
Coming from a particular system?
These pages cover what a migration looks like from where you are now.
Common Questions
Every page is free to read in full. The working files need an email address so we can send them to you, and the complete pack asks a few more questions so we send the right things. There is no obligation to talk to anyone, and the tools are written to be useful in a process we are not part of.
Yes. They are written against what mid-market organisations need rather than what any one product does. The requirements template is not modelled on any vendor's feature list, and the demo question bank includes questions we would rather not be asked ourselves.
Start by working out what your current system costs you each year, including staff time, and catalogue what has been customised or integrated on top of it. Then define your requirements and record which ones your current system already meets, so you can see the gaps. Build the internal case on that evidence, run a structured selection process, and plan the cutover in detail. The tools here follow that sequence.
Only you can answer whether the timing is right. If you are weighing it up, the cost of standing still worksheet and the customisation register will tell you more about your own position than any vendor conversation will. Avanza is part of Verde Group, which supports Greentree customers in New Zealand, so if you do decide to move you would not be handing your system to a stranger.
It depends on scope, the number of entities, how much has been customised, and how much of your own team's time is available. Rather than a single figure, work through the customisation register first. The volume of customisation and integration is the largest single variable in both timeline and cost, and most organisations find it is smaller than they assumed.