General Consultant Discussion

For those in Barbara's 2013 Installation Tips and Tricks session, there was a discussion on moving Paperless Office logs 'after' the initial migration, when you need to re-migrate the logs before going live. I forgot about this utility that updates the Paperless Office logs without remigrating the System files. This was introduced in 4.40 Product Update 3. Select File menu > Run. In the Sage MAS 90 Run Program window, enter *UTL and click OK. Select the Paperless Office Log Migration Utility. Enter the path to the MAS 90 you are migrating from. Enter the Company Code and select Proceed. Note: Type in the company code. I found that I usually get an error when using the F2 key.

Does this have to do with the records no longer showing in the Paperless Viewer after re-migrating for the go-live?

@BrettZimmerman Correct. After your initial migration for the pilot, there's a time gap for paperless office logs when you finally go live. I, personally, never run the migration utility again after the initial pass because it undoes most of the work you did getting the pilot ready for go live (I simply manually copy the company folder over and reconvert). This utility allows you to move over the newly created log records to bring them current. Of course, you may need to change the path, but at lease all the records are there.

@BillPfahnl, are you referring to the .pdf's re-linking when you mention, ""it undoes most of the work you did getting the pilot ready for go live""? Sounds like I have to now run the Utility to get the records back in the Paperless Viewers, and then re-do all the .pdf's linking. And when you say ""manually copy the company folder over and reconvert"", does that mean you don't actually go thru the literal ""re-migration"" process? 99% of the time I don't re-migrate System Files, so therefore it sounds like the .pdf re-linking shouldn't be performed until the go-live.

@BrettZimmerman Typically, I do not re-link the pdfs until we 'go live' since we'll need to update the logs anyway, and this area is not one usually tested by the client (and the old path is actually still valid). However, I do change the default path in the paperless settings so that any 'new' registers created in testing are also tested for the correct new path. Again, this is only how I run, it's not necessarily the only methodology.