MYOB Greentree

    Is MYOB Greentree End of Life?

    If you've heard that MYOB Greentree customers are being encouraged to consider MYOB Acumatica, you may be wondering whether Greentree is being discontinued — and what that means for your business.

    The short answer

    As of August 2026, MYOB has not publicly announced that MYOB Greentree has reached end of life. Greentree remains referenced in current MYOB product, licensing and support material.

    However, MYOB is actively talking to Greentree customers about their future technology strategy and provides a pathway for businesses considering a move to MYOB Acumatica.

    So if Greentree is at the centre of your business today, now is a sensible time to understand your options — without assuming you have to immediately replace it.

    Last updated: August 202610 min read
    Operations manager at an Australian engineering contractor reviewing ERP dashboards in the office with the maintenance workshop visible through the window

    Quick Answer

    No public MYOB announcement identified as at August 2026 says MYOB Greentree has reached end of life. Greentree still appears in current MYOB product and licensing material, and Greentree agreements include product maintenance provisions. What has changed is MYOB's emphasis: it is promoting MYOB Acumatica as its modern cloud ERP and offering migration-readiness support to Greentree and MYOB Exo Business customers thinking about what's next.

    • Being encouraged to migrate is not the same as a formal end-of-life notice
    • Confirm the roadmap for your specific Greentree environment with MYOB or your partner
    • MYOB Acumatica is one option to assess — not the only one
    • Finance and operations don't have to live inside the same system; they can be separate, connected platforms

    Has MYOB announced Greentree end of life?

    No official public end-of-life announcement for MYOB Greentree has been identified as of August 2026. That's the honest position, and it's worth stating plainly before anything else.

    MYOB still publishes MYOB Greentree product information. Current Greentree licence documentation exists, and the Greentree agreement discusses ongoing product maintenance — including improvements, updates and bug fixes. Taken together, that does not support describing the entire Greentree product as formally end of life today.

    What is also true is that MYOB's recent ERP content makes it clear Greentree customers are being encouraged to think about what comes next. Both things can be true at once, and conflating them is where most of the confusion comes from.

    Being encouraged to migrate ≠ officially end of life

    A software vendor encouraging customers to consider its newer cloud platform does not automatically mean the existing product has reached formal end of life. Treat roadmap commentary from resellers, forums and industry chatter as background — not as confirmation.

    Why are Greentree users hearing about MYOB Acumatica?

    Because MYOB is investing heavily in, and promoting, MYOB Acumatica as its cloud ERP platform. MYOB's 2026 ERP guidance explicitly addresses businesses running MYOB Greentree and MYOB Exo Business that are "thinking about what's next", and encourages them to assess migration readiness and how Acumatica might fit their environment.

    Our interpretation: this reads as MYOB encouraging mature ERP customers to begin planning a longer-term technology roadmap. It is not a statement that MYOB is forcing everyone onto Acumatica, and we'd caution against reading it that way.

    Separately, plenty of Greentree businesses are already reviewing their systems for their own reasons. Common considerations include:

    Cloud accessibilitySoftware architectureIntegrationsCybersecuritySupportabilityInfrastructureWorkforce expectationsMobile accessFuture developmentReportingAutomation

    None of that implies Greentree can't do these things. They're simply the criteria most businesses end up evaluating when they review any long-standing ERP.

    Is Greentree considered legacy software?

    "Legacy" is a slippery word. For some people it means unsupported. For others it simply means established, on-premise, or heavily customised over many years. MYOB's own software lifecycle discussion is a more useful frame than the label itself.

    Software can be mature, stable, still supported and widely used — while the businesses running it simultaneously begin planning for a newer technology architecture. Those aren't contradictions.

    A typical software lifecycle

    Innovation
    Growth
    Mature Platform
    End of Life
    End of Support

    We haven't placed Greentree at a stage on this diagram, because MYOB hasn't publicly done so.

    The important question isn't which label applies to Greentree today. It's whether your current environment will still meet your business requirements over the next three to five years.

    Does this mean you need to move to MYOB Acumatica?

    Not necessarily. MYOB Acumatica may be one option for businesses reviewing Greentree, and for organisations that want to stay within the MYOB ERP ecosystem it's a reasonable candidate to assess. For others, a different ERP may make more sense.

    But before choosing any replacement system, it's worth understanding what Greentree actually does inside your organisation today. In practice, those requirements fall into two very different groups.

    Financial requirements

    • General ledger
    • Accounts payable
    • Accounts receivable
    • Financial reporting
    • Tax and BAS
    • Financial controls

    Operational requirements

    • Jobs
    • Projects
    • Labour
    • Timesheets
    • Workshops
    • Scheduling
    • Purchasing
    • Inventory
    • Assets
    • Service work
    • Field teams
    • Job costing
    • Safety workflows

    These two groups of requirements do not necessarily have to be solved by the same system. That single realisation changes what a "Greentree replacement" project looks like.

    Before replacing Greentree, look at how your business actually operates

    A system migration is expensive and disruptive. The worst outcome is spending that money simply to recreate the same inefficient workflows on newer software.

    Most businesses start by documenting their Greentree configuration. That's useful, but it only describes the work that already lives inside the ERP. The more revealing question is what happens everywhere else.

    What happens outside Greentree today?

    • Which processes live in spreadsheets?
    • What still happens on paper?
    • Which teams use separate apps?
    • How do field crews receive job information?
    • How are workshop jobs managed?
    • Where are timesheets entered?
    • How is scheduling handled?
    • Where are purchase orders created?
    • How is job profitability monitored?
    • How many times is the same data entered?
    • Which reports require manual manipulation?
    • Which processes depend on one person knowing how we've always done it?

    Don't just map your Greentree modules. Map the actual work.

    For contractors, the bigger question may be operations vs accounting

    For mining, engineering, maintenance and field-service contractors, a large amount of everyday system usage is operational rather than purely financial. Teams need to manage jobs, projects, people, workshop work, schedules, field activities, timesheets, purchasing, materials, assets, safety and costs — often before a single invoice is raised.

    Historically, all of that was pushed into the ERP because the ERP was the only system available. That's no longer the only structure worth considering.

    Traditional approach

    ERP
    FinanceOperationsFieldWorkshopProjects

    Connected approach

    SprintSuite

    Operations

    Accounting / ERP platform

    Finance

    The right structure depends on the business, but reviewing Greentree is an opportunity to consider whether every operational workflow still needs to sit inside the same ERP.

    Where SprintSuite fits

    SprintSuite isn't designed to replace the general ledger or every financial accounting function inside an ERP. It is built to manage the operational side of businesses where work moves between the office, workshop and field.

    It connects to accounting platforms rather than competing with them — see the SprintSuite MYOB and Xero integrations for how operational data reaches finance without double entry.

    Contractors working to Tier-1 requirements can also see how this comes together in mining contractor management software.

    What should Greentree businesses ask before migrating?

    1

    Why are we actually considering a move?

    Is there a genuine business problem, or are we reacting to uncertainty about the product roadmap?

    2

    Which Greentree functions are genuinely critical?

    Separate essential functionality from functionality that exists simply because it always has.

    3

    What currently happens outside Greentree?

    Identify the spreadsheets, paperwork, apps and workarounds that quietly run parts of the business.

    4

    What belongs in finance and what belongs in operations?

    Avoid automatically recreating one enormous system because that's how it's always been structured.

    5

    What does the field need?

    Consider usability away from the office, on a phone, often with poor connectivity.

    6

    What does the workshop need?

    Look specifically at technicians, labour, parts, work status and scheduling.

    7

    Which customisations need to survive?

    Not every old customisation should automatically be rebuilt in a new platform.

    8

    Which integrations matter?

    Document the actual flow of data between systems, including the manual steps between them.

    9

    How much migration effort is realistic?

    Account for data cleansing, implementation, configuration, testing, training, adoption, integrations and historical data.

    10

    What should the software environment look like in five years?

    Design forward rather than simply recreating today's environment on newer software.

    Should you wait for an official Greentree end-of-life announcement?

    You don't need an end-of-life announcement to start planning. Planning is a different activity from migrating, and it costs far less. A sensible technology review can happen well before software becomes unsupported.

    In the meantime, businesses can work through most of the groundwork:

    Document your current environment
    Understand dependencies
    Identify process problems
    Clean up data
    Assess integrations
    Compare potential platforms
    Understand implementation effort
    Establish a migration trigger

    The goal isn't to panic and migrate early. It's to avoid being forced into a rushed decision later.

    What if MYOB Greentree does reach end of life?

    This is a hypothetical, not a prediction. If MYOB eventually announces a formal Greentree end of life or end of support, these are the details that would matter:

    • Official dates
    • Support timelines
    • Security update timelines
    • Regulatory and payroll implications where relevant
    • Migration support
    • Data migration options
    • Integration impacts
    • Infrastructure requirements
    • Contractual and licensing implications

    Always rely on MYOB or your authorised MYOB partner for the official status and support dates that apply to your specific Greentree environment. Don't plan around dates published by anyone else.

    What are the alternatives to MYOB Greentree?

    There are three broad approaches, and they're genuinely different projects — not just different vendors.

    Option 1

    Move to another ERP

    A business may decide that another complete ERP is the best fit for its finance and operational requirements.

    Option 2

    Move to MYOB Acumatica

    For businesses that want to remain within the MYOB ERP ecosystem, Acumatica may be one option to assess.

    Option 3

    Separate finance and operations

    Use dedicated operational software for jobs, projects, workshop and field activity, while keeping financial accounting in an appropriate finance platform.

    For mining, engineering and field-service contractors, SprintSuite is one operational platform worth considering under the third approach. If you've already moved past "what's happening with Greentree?" and are weighing replacements, you can compare MYOB Greentree alternatives and see how the operations-plus-finance split works in practice. Businesses working through the same question about MYOB Exo Business often find the MYOB EXO alternative comparison useful, since the architecture question is identical.

    MYOB's broader ERP software information is the right starting point for the MYOB side of that comparison.

    Reviewing what comes after Greentree?

    Before choosing another ERP, take the opportunity to look at how your jobs, projects, workshop and field teams should actually work.

    SprintSuite helps mining, engineering and field-service contractors connect operational work from the office to the workshop and field.

    MYOB Greentree End of Life FAQs