Skip to main content
Skip table of contents

Migrating Document Manager integrated with AE Practice Manager to a new server

This support note applies to:

  • AE Document Manager (AU)
Article ID: 31674

MYOB INTERNAL STAFF ONLY

**DO NOT MODIFY THIS ARTICLE. WHERE CHANGES ARE REQUIRED, REFER TO THE TECHNICAL SERVICES TEAM**

This article is an overview of how to migrate MYOB Document Manager (DM) to a new server.

The procedure involves a clean installation of the program files on the new server and restoring the database and documents on the new server.

MYOB does provide a migration service. If you have any doubts or concerns about completing this migration yourself, please contact MYOB and arrange for one of our consultants to perform the migration for you. This service may require a booking, so please plan well in advance.

It is important that someone who is confident with the Microsoft Windows operating system manages the migration.

If you experience issues with MYOB software after following the instructions below, additional assistance on your migration may fall outside of the terms of your Sales and Service Agreement.

Please read through these instructions prior to undertaking the migration process.

1. Migrate MYOB Accountants Enterprise Practice Manager (AE PM)

 It is required that you migrate MYOB Practice Manager to the new server before Migrating Document Manager. For details of how to migrate AE PM to a new server refer to Migrating AE Practice Manager to a new server.

2. Copy the intranet data and document file storage over to the new server

To find the location of your Document Manager file store

Open MYOB Practice Manager (AE PM) and follow the menu path Maintenance > Documents > Document Manager Setup > File Store tab and note the location.

To find the location of your Intranet file store

Open MYOB Practice Manager (AE PM) and follow the menu path Maintenance > Documents > Intranet Administration > Tools > Configuration and note the location.

Do not copy over the DatabaseLookup.xml file from either data folder. If you do accidently they must be deleted before running the install.
3. Delete registered database identifier key
  1. Open SSMS.
  2. In the AEDB database, go to the table pmo_SyncConfiguration.
  3. Right-click the table and select edit top 200.
  4. Delete the row with the registered_database_identifier key.
4. Install DM on the new Server pointing at the new data locations

Please refer to the Document Manager installation guide on the my.MYOB Product Downloads page, Australia for details of how to install Document Manager.

5. Remove old workstation installs from workstation or terminal server

Open up Control Panel > Programs and features and remove MYOB Document Manager Workstation and MYOB Intranet Workstation if they exist.

6. Run workstation installs on workstation or terminal server

 To run a Document Manager workstation install:

  1. Click the Start button and select Run.
  2. In the Open field type \\SERVERNAME\MYOBDM\SETUP\docmgrwkstn.exe, where SERVERNAME is the name of the server where Document Manager is installed.
7. Disable SQL and MYOB Share on the old server

Disable the following services from the old server so the users don't access the data from the old server.

  • SQL Server(MYOBACCT) or SQL Server(name of your AE SQL instance)
  • MYOB OntheGo Service
  • MYOB Sync Client Service
  • MYOB Tax SBR Sender Service  (if exists)
  • MYOB DM Portal Sync Service

To disable the services:

  1. On the old server, go to Control Panel > Services.
  2. Right click the service you want to disable, for example SQL Server(MYOBACCT) and select Properties.
  3. At Startup type, select Disabled from the drop-down.
  4. At Service status, click Stop.
  5. Click OK.

You'll also need to remove the share from the shared MYOB folder (for example S6SYSTEM, AONET). Talk to your IT on how to remove sharing from a folder.

If you're unable to disable the SQL Server, detach the old MYOB AE/MYOB AO(for example, VPMSER or AODB1) and Tax databases (for example, AOTAX1, AETAX1)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.