Forum Discussion

LincolnH's avatar
LincolnH
Member
11 months ago

MYOB AccountRight Enterprise v19 Upgrade Path to stay current and supported

Hi, I am looking at the following scenario:-   Current Version:  MYOB AccountRight Enterprise v19.5 in a network configuration Questions:- Upgrade path and requirements to the next closest MY...
gavin12345's avatar
gavin12345
Ultimate User
2 months ago

Hi The_Doc​ 
Your proposed approach sounds fine. Now that AR2025 supports multi locations and foreign currency, those concerns are no longer relevant. A few things worth noting:

 

  • if client not keen to sign up immediately, MYOB will provide a trial serial number which can be used to test.
  • sometimes negative inventory cannot be turned off even if there are no negative items - file may need repair to fix and switch off the preference
  • if foreign currency is used, some invoice layouts are not allowed and if used in foreign currency transaction the file will not upgrade. Layouts need to be changed to allowable types, eg Item and service - easy for current year, less so for prior year - may need 3rd party help if you encounter this.
  • confirmation is available via a 3rd party if/when MYOB stop and decline to issue patch for those who want to keep using

Regards

Gavin

The_Doc's avatar
The_Doc
Ultimate Cover User
2 months ago

Hi gavin12345​ 

 

Thanks for your advice. Have since gained a copy of their myob.myo file - it was 1.95 mb long - an optimise reduced it to 495k - there is no perpetual inventory, no multi-currency. There are 2 files, the 2nd one no idea.

 

So I tried a local server upgrade of the file but after almost 24 hrs - and leaving my laptop going all night it was hung on, or still converting it -checking 'constraints'  - so I killed it this morning - no idea whether it was still going - my next try is to purge the file of old data and try again.

 

I know big myob files may need to be sent into MYOB - but I will try an upload to a licenced 2025.10 - as I have requested the client to expedite getting 2 licences to move forward.

 

Sometimes uploading and allowing the online system to upgrade can work better. All trial and error - but 1 Mar 25 is just around the corner and we have 2 MS Access databases to re-engineer for API access.

 

An email stating the move forward facts goes out today and the path forward for API connectivity by 1 Mar 26. (I note your advice with keeping MYOB Enterprise - yes am aware but with this client they are not small but a big business that should have upgraded long ago and ignored advice to - kid gloves removed!!)

 

 

 

Regards The Doc

  • gavin12345's avatar
    gavin12345
    Ultimate User
    2 months ago

    Hi The_Doc​ 

     

    The long upgrade process is not due to the file size (I take it you meant 1.95 GB reduced to 495 MB on optimise). I have upgraded many files in my time, some well over 490 MB.

     

    The issue is I suspect this file has possibly a large number of payroll categories and or employees and or payroll history. The upgrade process is flawed (poorly coded) and rather than use indexes, the upgrade iterates in a circular fashion through every employee and every payroll category and every pay history record in seemingly endless loops. I had several upgrades that lasted over 24 hours due to this issue. The upgrade ran smoothly only after deleting standard pay records. Upgrade shouldn't take over 2 hrs for a 500 MB file.

     

    Regards

    Gavin

Looking for something else?

Search the Community Forum for answers or find your topic and get the conversation started!

Community home

Dig into MYOB Academy for free courses, learning paths and live events to help build your business with MYOB.