Tech transformation touches critical workflows across finance, reporting, payroll, supply chain, and inventory management, not to mention all the teams that make them work. So successful migration to cloud ERP is critical to ongoing success.
The difference between a stressful and a predictable tech transformation is not just the software, it‘s the clear, proven methodology that guides how the project will run from the very first planning conversation through to go‑live and handover.
For MYOB Acumatica, our cloud ERP, we use a standardised implementation framework — referred to as One Methodology — to help set each customer’s migration up for success. Our implementation framework provides structure, roles and responsibilities and key checkpoints for a successful migration, while allowing flexibility for your business size, scope and industry.
This article gives a high‑level view of that methodology for businesses considering a move from desktop business software to MYOB Acumatica.
What is MYOB’s One Methodology?
One Methodology is MYOB Acumatica's implementation framework that guides how we work with our customers to deliver a successful implementation. One Methodology organises an implementation into phases, each with a clear objective, key activities, and a quality gate before moving on, so you have clarity every step of the way.
The core phases are:
Plan – Initiate the project, mobilise teams and establish a shared roadmap.
Design – Understand detailed business requirements and document how MYOB Acumatica will support them.
Build & Test – Configure the solution, prepare and migrate data, and validate through testing.
Readiness – Prepare the wider organisation, support structure and governance for go live.
Go Live & Closure – Execute cutover, stabilise, and hand over to business‑as‑usual teams.
Each phase includes main activities, milestones and qualification gates, so both you and the MYOB Acumatica team know what “done” looks like and who is accountable for which outcomes.
Phase 1: Plan – setting the foundation
Objective: Initiate the project, onboard teams, plan the journey, and align stakeholders on scope, outcomes and ways of working.
In the Plan phase, you and the MYOB Acumatica team will:
Initiate and set up the project
- Handover from sales to implementation.
- Mobilise the MYOB Acumatica team and customer project teams.
- Clarify roles and responsibilities across sponsors, project managers, subject matter experts (SMEs) and consultants.Confirm scope and planning approach
- Review the agreed solution scope and architecture.
- Plan the upcoming Design activities, including workshops and participants.Plan change management at a high level
- Identify stakeholders and change impacts.
- Agree principles for communication, training and success measures.Kick off the project
- Re‑state the investment case, objectives and vision.
- Present scope, timeline, methodology, governance and key work routines to the wider team.
The Plan phase closes with the basics in place: a project plan, governance structure, and shared understanding of why you’re doing this and how the work will be delivered.
Phase 2: Design – shaping how your business will use MYOB Acumatica
Objective: Capture the level of detail needed to understand how MYOB Acumatica will support your processes and outcomes, and document that in a clear design blueprint. Typical Design phase activities include:
Solution design workshops
MYOB Acumatica consultants work with your process owners and SMEs to understand outcomes, workflows, exceptions and compliance needs, then map those to good‑practice application flows.Optional prototyping
For some projects, a subset of workflows is prototyped in the application to confirm understanding before finalising the design.Customisation, integration and reporting scope
Where required, the MYOB Acumatica team and the customer define what needs to be built outside standard configuration – such as bespoke integrations, forms or reports – and document this in functional specifications.Data migration scope and methods
Together we define which data (and from which sources) will be migrated, how it will be uploaded, and what cleaning or harmonisation will be needed.
The Design phase results in design sign‑off, a formal agreement that the documented solution and any functional specifications accurately capture requirements and will serve as the baseline for build and test.
Phase 3: Build & Test – configuring, migrating and validating
Objective: Configure MYOB Acumatica as per the agreed design, prepare and upload data, and verify that the solution works as intended. Key elements of this phase:
Solution setup and configuration
Our team of MYOB Acumatica consultants configure the application to match the signed design, using standard workflows, wherever possible.Customisation, integrations, forms and reports
Any approved bespoke work is developed, tested and deployed, with emphasis on minimising impact on the core solution.Data preparation and upload
Your team extracts, cleans, harmonises and populates data into upload templates, supported by MYOB Acumatica consultants as needed. We then upload this data and you verify that it has landed correctly.Core team training
MYOB Acumatica expert consultants train your core project team (subject matter experts and process owners) on the configured solution so they can test effectively and later help enable end users.User Acceptance Testing (UAT)
Your organisation plans and executes user acceptance testing, using structured test cases, issue logs and clear criteria for what must pass before go live. This includes not only ideal, day-to-day work sequences, but also realistic “what‑if” scenarios.
Build & Test closes with UAT sign‑off, confirming that the solution behaves as designed and that any remaining issues are understood and acceptable for progression.
Phase 4: Readiness – preparing your organisation for go live
Objective: Ensure both the system and the organisation are ready for cutover, with trained users, support structures and governance in place. Typical activities include:
Parallel runs where relevant
In areas like payroll, old and new systems may be run in parallel for a period, to see if they produce matching outputs and build confidence before you switch off the old system.End‑user training
Role‑based training that covers system steps, updated responsibilities and process changes, giving managers confidence that teams can operate in the new system from day one.Support and system governance
Establishing internal first‑line support (often “super users”), defining processes for handling requests and improvements, and setting up solution and data governance roles.Readiness verification
Consolidating the status of user acceptance testing, open issues, change management, support set‑up, training and any parallel runs into a readiness assessment, often with our recommendation on risk level.
Once this Readiness phase is passed the project proceeds to the next phase: Go Live & Closure of the old system.
Phase 5: Go Live & Closure – cutover, stabilisation and handover
Objective: Move from old systems to MYOB Acumatica, provide focused support through early usage, and close the project with clear handover to business‑as‑usual functions. This final phase includes:
Cutover execution
Following the agreed plan: final data loads, shutting down work in old systems at the right time, verifying key data in the new system, and confirming that users can log in and work in the new system.Post‑go‑live assistance
MYOB consultants provide structured support while your internal support team handles first‑line queries, ensuring questions are funnelled efficiently and learnings are captured.Project closure and handover
A formal closure process confirms repositories are updated, lessons learned are documented, success is assessed against objectives, and responsibilities move cleanly to support and governance teams.
At this point, the implementation project is complete, and your organisation operates in MYOB Acumatica with clear ownership for ongoing adoption.
What this means for your migration to MYOB Acumatica
MYOB Acumatica’s One Methodology ERP implementation framework provides predictability and confidence for businesses undergoing tech transformation. Rather than a single high‑risk go‑live date, you work through a series of phases and qualification gates, each with defined deliverables and sign‑offs. For leaders and project sponsors, this translates to:
Clear visibility of what’s happening and what comes next.
Defined roles and responsibilities for MYOB and your internal team.
Confidence that key risks are being managed deliberately, not left to chance.
Ready to take the next step?
If you're running MYOB Exo Business or MYOB Greentree and thinking about what's next, book an MYOB Forward migration readiness session with our team. You'll connect with people who know your current system and MYOB Acumatica inside out, and walk away with a clearer view of your environment, how MYOB Acumatica fits your business, and a realistic path forward.
On a different solution? If you're on a legacy desktop ERP and starting to feel the limitations, book a free session with the MYOB Acumatica team and get a clear picture of what's possible and how to get there.
Information provided in this article is of a general nature and does not consider your personal situation. It does not constitute legal, financial, or other professional advice and should not be relied upon as a statement of law, policy or advice. You should consider whether this information is appropriate to your needs and, if necessary, seek independent advice. This information is only accurate at the time of publication. Although every effort has been made to verify the accuracy of the information contained on this webpage, MYOB disclaims, to the extent permitted by law, all liability for the information contained on this webpage or any loss or damage suffered by any person directly or indirectly through relying on this information.
Contributors
MYOB Subject Matter Experts