Skip to content
Financial Management
Accounting, General Ledger, Accounts Payable, Receivable, and Cash Management, Reporting of financial operations.
Customer Management
An integrated CRM to manage marketing, quoting, sales, post-sales support, and customer information.
Field Service Management
Mobile Field Service for real-time data between the field and office, track equipment, maintenance and manage service orders.
Construction
Powerful financials, Job Cost Accounting, Project Management, Payroll, Inventory, Service Management, CRM, and more.
Manufacturing
Streamline operations from production planning and shop floor management to financials, CRM, inventory, and sales orders.
Project Accounting
Manage budgeting, inventory, change orders, timesheets, billing, profitability, and reporting for individual business initiatives. 
Wholesale Distribution
Advanced inventory management, WMS, serial and batch tracking, kit assemblies, bin location, pick/pack/ship.
eCommerce & Retail
Synchronise real-time data between MYOB Advanced ERP and BigCommerce or Shopify with a native connector.
Payroll & Workforce Management
A modern Cloud Payroll and HR Management Solution working alongside MYOB Advanced ERP.

All you need to Advance your business

MYOB Acumatica Cloud ERP has the flexibility to grow with your business.

Are you ready to take your business to the next level? 

Connect all your business functions with MYOB Acumatica in the Cloud

Wholesale Distribution
Advanced inventory management, serial and batch tracking, kit assembly, bin location, pick priorities, manage multiple customer and supplier price lists, order discounting.
Retail and eCommerce
Native eCommerce Connector provides tools for syncing data between MYOB Advanced ERP and leading eCommerce solutions, BigCommerce and Shopify.
Manufacturing
By connecting production planning, shop floor, financials, CRM, inventory management, and sales orders, it enables real-time coordination across your entire organisation.
Field Services Management
Streamline tasks, scheduling and routing, manage inventory of tools and parts, seamlessly integrate accounting, and administrative information into a single unified system.
Construction
Project Accounting, Project Billing, Contracts, Job Costing, Change Orders, Daily Field Reports, Retentions, Compliance, Mobile Applications, Payroll and Reporting in one solution.
Solutions for all industries
MYOB Advanced is designed to adapt to the ever-changing landscape of different industries. With customisation options, it effortlessly caters to a diverse range of industries. 

MYOB Acumatica Cloud ERP for New Zealand Businesses

Are you ready to take your business to the next level? 

Connect all your business functions with MYOB Acumatica in the Cloud

What happens to your customisations when you migrate ERP?

Stage 1 · Working out whether to move

They do not migrate. They get sorted, and only one of the four outcomes is expensive.

"Our customisations are unique" is the most common objection to changing ERP, and the least tested. Until someone lists every item and asks who uses it, nobody can say which group anything belongs in, so the whole set gets treated as untouchable and the migration is priced against an unknown.

HOW THEY'RE SORTED

The four potential outcomes for your customisations

01 · RETIRE
Nothing depends on it

The report nobody reads, the field added for a customer you no longer have, the workflow built around someone who left in 2019.


Cost Low

Consistently the largest group

02 · REPLACE
Standard does it now

Built to fill a gap that has since closed. Approval workflows, document layouts, multi-entity, mobile access.


Cost Medium

Second largest, usually

03 · REDESIGN
Right need, wrong build

The requirement is real but the way it was implemented cannot survive the move. Anything wired directly into the database lives here.


Cost MedHigh

Second largest, usually

04 · REBUILD
Genuinely yours

Encodes something specific to how your business operates, still used, and not available as standard.


Cost High

Almost always the smallest

Every item you retire is scope you do not pay to rebuild, test, train on and support for the next decade.

Customisations accumulate over a decade. Each one made sense on the day. Together they form a layer nobody has ever looked at as a whole, and organisations that examine it properly consistently find a meaningful part is simply dead.

Excel · 5 tabs · free

Customisation and Integration Register

Three registers with dropdowns and automatic disposition, plus a findings tab that counts retirement candidates and key person risks.

- Format - Excel (.xlsx)
- Registers - Customisations, integrations, reports
- Time to complete - About 2 days

Customisation Register
NOT ALL EQUAL

What breaks hardest

Knowing the difference is what turns a list into a plan.

Worst case

Direct database connections

Anything reading or writing straight into the database, including reporting tools pointed at the back end, does not survive in any form. These always need redesigning, and they are frequently the last thing anyone looks for because IT built them rather than the ERP partner.


THE REAL RISK

Undocumented scripts and business rules

Not because they are hard to rebuild, but because nobody can say with confidence what they do. You cannot safely retire what you do not understand, so it gets carried forward by default, at full cost.


CHEAPER TO ABANDON

Screen and form level customisation

Modern systems handle layout, fields and personalisation very differently. Attempting a faithful reproduction of an old screen is normally the wrong instinct and an expensive one.


OPPORTUNITY

Manual export and import routines

Not integrations at all. Someone is doing that by hand, on a schedule, forever. They rarely appear on any inventory because no software was ever purchased, and most are automation opportunities rather than migration scope.


LARGEST, SOFTEST

Custom reports

Where the highest proportion of genuinely unused items hides. Reports get built, distributed, then quietly ignored while continuing to be produced.

Customisation and Integration Register

Three registers with dropdowns and automatic disposition, plus a findings tab that counts retirement candidates and key person risks.
HOW TO USE THE REGISTER

The four questions to ask for each business area

Who actually uses this, and how often?

Ask the users, not the person who commissioned it. Anything answered with "never" or "I'm not sure" is a retirement candidate.

Does anyone here understand how it works?

If the answer is nobody, that is a risk you are carrying right now. Migration does not create it, it just makes it visible.

Would standard functionality do this today?

Many customisations fill a gap that mainstream systems closed years ago. Ask for every item rather than assuming.

What breaks if it disappears tomorrow?

The fastest way to separate genuine dependency from habit. If nobody can answer, you have learnt something.

Say this out loud at the start of every session: nobody is in trouble for admitting something is not used. A register that flatters the current state is worse than no register at all, because it hardens a wrong number into a plan and a budget.

Ninety minutes per business area, with the people who use the system. Two days of effort in total is typical, spread over a fortnight so people can check things between sessions.

ONCE THE REGISTER IS FILLED IN

Three things to do next

Document the key person dependencies first. That work is worth doing whether or not you ever migrate, and it is the finding most likely to change someone's mind about how urgent this is.

Take the challenge list to the people who would notice. Not the person who built the item. The person who would ring you if it vanished. Get a yes or a no.

Give it to any partner or vendor you talk to. A supplier quoting against a real inventory produces a very different number from one quoting against an unknown, and comparing quotes becomes possible for the first time. Keep it afterwards as your scope baseline.

QUESTIONS

Common Questions

Avanza Solutions is a MYOB Acumatica implementation partner based in New Zealand. This register is published as a neutral planning aid. It is designed to be useful to you and to any partner or vendor you choose to work with, including one that is not us, and useful whether or not you decide to migrate at all.

What happens to our customisations when we migrate ERP?

They sort into four groups: retired because nothing depends on them any more, replaced by standard functionality that did not exist when they were built, redesigned because the implementation method cannot survive the move, and rebuilt because they encode something genuinely specific to your business. The last group is usually smaller than expected.

Which ERP customisations are hardest to migrate?

Direct database connections are the worst case and never survive, because the underlying table structure changes. Undocumented scripts and business rules are next hardest, not because rebuilding is difficult but because nobody can safely say what they do. Screen and form level customisation is usually cheaper to abandon than to reproduce faithfully.

Should we do a customisation audit before talking to ERP vendors?

Yes. It is the single most useful piece of preparation available to you. Suppliers quoting against an unknown have to price the risk, and you pay for that uncertainty. Quoting against a real inventory produces sharper numbers and makes comparing proposals possible.

How long does a customisation audit take?

For a mid-sized organisation, one ninety minute session per business area plus a few hours of collation. Two days of effort in total is typical, spread over a fortnight so people can check things between sessions.