Sage 100

Doing a 2013 to 2016 final migration (Standard). don't want to migrate system files. Way back when they had EES, but don't have CRM installed. There is a renamed CU folder in their 2013 folder. Can I get around migrating system files?

You've done the initial migration and copied the system files?? I would say go for it by just copying the data folder and reconverting. You probably will need to copy the system paperless logs. I am not sure if you have to run the @JimWoodhead import utility because of a table change or not.

Thanks @JeffSchwenk - was trying to avoid that, but going with your suggestion.

Barbara--What Jeff says is what I do most of the time. Copy over PDF logs. Also, since your reports files are already converted in your testing environment, you could also change them out, too.

@RobertaChase, yes, i back up the Reports folders prior to re-migration or conversion and restore.

I located the utilities on my hard drive,, but can't locate instructions on how to use them. Can someone please share them? @JimWoodhead @MarcosDeLuna

@barbara. Here is a link the solution. https://www.evernote.com/shard/s270/sh/b0272bf6-77cb-49c1-8415-4838c104123d/3de63f3162cecc2a656d76612ff87409

Shoot - not moving servers, but moving location on server. guess I need to use Link maint

Actually, one the @JimWoodhead utilities resizes the log table. There is another one that is super fast in changing the pathing.

Just to be clear - this will be good for 2013 to 2016? Because the instructions are for 4.3 to 5.1.

My scenario is 2013 to 2016, same server, different locations. Which utility is the one to use, if either? @JimWoodhead @MarcosDeLuna @JeffSchwenk

is your paperless location changing? if not then follow the merge instructions.

@JimWoodhead which utility? I haven't used either.

MERGE UTILITY - OLD PRODUCTION SYSTEM INTO NEW TEST (NOW LIVE) AFTER GOING LIVE: Note that this solution presumes that between the old version and the new upgrade the location of the paperless documents is not changing. If the location is changing then you'll need to use the utilities in Sage to relink the location. This utility also only merges the journals and registers. The customer/vendor PDF files stay with the MAS_XXX folders, the reports and period end are the two which would need to be manually changed (not affected by this script). 1) Copy attached program(PL_LOGMERGE) to SOA folder in v2016 system 2) Copy Pl_JournalLogPdf.M4T to Pl_JournalLogPdfOld.M4T in the MAS_SYSTEM folder of v2013 system 3) Copy the new file (Pl_JournalLogPdfOld.M4t) to the Same location on v2016 system 4) Run ""SYZCON"" at File/Run to drop to prompt 5) At Prompt type following RUN ""PL_LOGMERGE"" 6) Program will run 7) Click ""DONE"" when finished

I don't get it. Paths didn't change. How would it know what path to change to? And instructions for the other utility don't look like there's a place to specify new path. @JimWoodhead

Hi, Barbara. I rarely ""re-migrate"" when doing an upgrade, so I usually move the PL Logs manually. ASSUMING that the Paperless folders have not moved, I rename the 3 PL_logs (for JournalsRegisters, Reports, PEreport) in MAS_SYSTEM folder) in the new system (V2016). Then, I'll take a copy of the 3 PLlogs from the OLD system (V2013). Paste them into the new system. Your logs are now updated. I do involve one of our programmers if the folders have moved. Logs for customer and vendor forms are in the data files themselves and will move automatically with your cut and paste of MAS_XXX.

Thanks @RobertaChase , the issue here is that the path IS changing, from one location on the server to another location on the SAME server. I've resigned myself to one of the most painful PL moves I can recall.

I HATE LINK MAINTENANCE!! Ok, I feel a little better now.

I couldn't quite figure if they were or weren't changing. I'm lucky enough to have programmers help me with that with code. Link Maintenance is PAINFUL. You probably know that you can do up to 8000 docs at a time. I usually cap it at 5000 docs at one time, since it takes so long to do 8000 I wonder if I screwed something up.

@BarbaraGoldstein Give me a call.

v2016 I believe using the migration tool on just company (not system) data does indeed bring the applicable paperless data along (including register / journal records). You'll still have to update the paths, but the PDFLogConvertDirectoryV2 utility is wonderful for that.

@JimWoodhead thank you so much for talking this through with me yesterday. Unfortunately, due to additional complication (don't ask), I didn't use the utility. But I really appreciate your time, and I'm going to use it next time I have one of these situations.

Another shout out of thanks to @JimWoodhead and @MarcosDeLuna creating this utility. After spending 30 minutes waiting for the link utility to open up, I installed the PDFLogConvertDirectoryV2 utility and completed the path updating in five minutes...

Thank You !Thank You !Thank You ! @JimWoodhead and @MarcosDeLuna for the Merge and Path Change Utility's !!! I can not believe how fast the utility works!!!!