This article details the steps in the FYI Migrate app when you have selected MYOB Document Manager or Virtual Cabinet as your current software (refer to Using the FYI Migrate App to Sync your Data).
Video Walkthrough
Note: Since the recording of this video, the option to Include Folder Name on Export is no longer shown and is automatically set "On".
This article contains the following sections:
- Enter the Server Name and Database Name
- Start the Syncing
- Once the Sync is Underway
- How to find MYOB and Virtual Cabinet Server and Database Details
- Introduction to Live Import
- Refiling
- Migrating a Filtered List of Documents
Enter the Server Name and Database Name
- Enter the Server Name and Database Name for your MYOB or Virtual Cabinet documents.
If a password is required for the FYI app to access the SQL database, then enter those details also.
If no password is required, leave it blank.
By default, the server name is set to “localhost” (for both systems) and the database to "VPMSER" (for MYOB) or "VirtualCabinet" (for Virtual Cabinet).
If you do not know this information, refer below to How to find MYOB or Virtual Cabinet server and database details at the end of this article. This may require the assistance of your IT provider.
- Click Next.
If you enter an incorrect Server Name and then click Next, the app will display an error.
Select your Folder(s) to Migrate
When the Server Name and Database Name have been entered correctly, you are prompted to add the folders that hold the files to migrate.
Click the Add and select the top-level folder containing the documents to migrate.
For Virtual Cabinet this is usually called "VCFileStore" or similar (and should contain folders similar to the above screenshot).
For Virtual Cabinet, as of version 1.0.0.172, the FYI Migrate app will import documents by the file path as well as the file content store path. This ensures that files held in the file path that are not the same as the file content store path are imported.
For MYOB this is usually called "DMFS_VPMSER", "VPMSER", "DMFS_AODB1" or similar.
When the folder is selected it displays in the migrate application.
Important Note: For MYOB or Virtual Cabinet:
- It is the head folder we want to sync (should look like our screenshots)
- Not the internal folders (that is, 2018, 2019, index1, index2 etc)
In the Select your folder(s) to Migrate, Back takes you back one screen, Add lets you add a folder or another folder, Remove removes the select folder and Clear removes all the selected folders.
To continue with your selection, click Done.
Note: For Virtual Cabinet, you may be prompted to select if you want to use the Client ID or Client Code to indicate whichever will match the client correctly to the practice management software. If a match is not made on the respective Client ID or Client Code, FYI will then try to match on the Client name. If there is no match on the Client name, the client is created as an unmatched client which can be resolved after the migration, using resolve unmatched (refer to Resolving Unmatched Clients). If this prompt does not appear, the migration will commence and matching will will run across all criteria.
Start the Syncing
The Syncing screen displays.
To begin syncing your MYOB or Virtual Cabinet documents with FYI, click Start.
If you want to double-check your selection before starting, you can click Restart Wizard and it will return you to the first step in the process (but it will remember what you have entered, so you don't have to completely start from scratch).
Once the Sync is Underway
Before beginning the sync, the application will check the selected directories for the number of documents.
The headline status shows what the application is doing while you wait for the sync to begin.
Note: Once the first sync is complete, the app will return to the top and look for any new/edited documents and sync them also. This process repeats hourly until either the app is closed or the sync is stopped.
How to find MYOB and Virtual Cabinet Server and Database Details
Finding the MYOB Server Name and Database Name
For MYOB sites you can usually find the server name and database name in the DMFS folder location in a document called databaselookup.xml. In the example below, this shows the Server Name of MYOBSRV\MYOBACCT and the Database Name is AODB1.
How to find the MYOB or Virtual Cabinet Server Name and Database Name
Where the defaults or above suggestions do not work, you can always find what you need using Microsoft SQL Server Management Studio.
Note: you may need the assistance of your IT provider to perform the following steps.
- Run SQL Server Management Studio and log in.
If you are running the FYI Migrate app on the SQL Server machine, then the server "localhost" will usually work.
The default Database name for MYOB is "VPMSER" and for Virtual Cabinet, it is "VirtualCabinet". - Locate the server name and database name
In this screenshot example, the server is "ACCDATABASE20" and the database is "VirtualCabinet".
Introduction to Live Import
When the syncing begins, your documents will LIVE IMPORT into FYI. Refer also to Implementors: Live Import.
- Cabinets and Categories in FYI will be generated automatically directly from the MYOB or Virtual Cabinet data.
- FYI will place the documents into Cabinets and Categories based on the original data in MYOB or Virtual Cabinet.
- FYI will look to match Client Names and Client Codes with your practice management software where possible.
- FYI will also look to assign the Year where possible.
Note: It is acceptable if Client Names, Years etc. do not appear to come into FYI perfectly during the live import. It could be, for example, that the Client Name was spelt slightly differently, or the Client Code is not in your practice management software. These issues can be resolved following the completion of the migration process. FYI will provide instructions.
How documents behave inside of FYI during the LIVE IMPORT
- If a document appears in FYI, it can be selected, edited, refiled etc.
- For Live Import from MYOB, if FYI identifies a new version of the document, from your historical document store, FYI will version that on top of any edits made inside of FYI.
- For Live Import from Virtual Cabinet, because of the way documents are recorded, there would be a separate document uploaded, not a new version.
Note: We suggest your users are careful editing documents that are still live importing.
Refiling
Once your data sync is complete, liaise with your Client Success Consultant who will arrange refiling in consultation with you.
Migrating a Filtered List of Documents
You can prepare a file that holds a list of reference numbers or documents IDs of the files you want to migrate and save the file locally.
The file can contain:
- A reference number (document id and the specific version, for example, 1438_9)
Or - A document id in which case the latest version of the specified document id will be migrated. When the document is an email, this will migrate all versions. Therefore newer versions of existing migrated documents will be migrated.
When creating the file:
- Only one file can be used per migration. Add all the reference numbers or documents IDs to the file before selecting the file.
- The file should be created as a plain text file (for example a .txt).
- Add one reference number or document ID per line in the file.
- Notes are also filtered with the list, but only for reference numbers, as Note IDs can conflict with documents.
Selecting the File
- In the Select your folder(s) to Migrate, click the Filter icon
- Click the option Select file containing documents to migrate.
- You are then prompted to select the file that you have saved locally from your Windows Explorer.
- A list displays of the reference numbers or documents IDs from the selected file. If required, use this to confirm the reference numbers or documents IDs in the file that is being uploaded.
- Click OK.
- Finalise the process as for the 'standard' migration. Click Done and the sync starts.
If the Migration App is run a subsequent time with a different file, if any reference numbers or document IDs are the same, the files will not be migrated again unless the file has changed.