Sage 100

Upgrade problem. I'm upgrading a client from 4.1 to 2018 phase I is 4.1 to 2013. we ran all the pre-migration utilities. and converted data. the conversion finished and later it became obvious that inventory module did not convert. There were not any error messages during the conversion process, but now I'm looking at the IMxxx directory and I see all the 4.1 legacy files are still there and have data. all the 2013 framework files are there but they are empty. I tried converting data again and get a message that ""c:........\mas90\IMxxx\IMxxx.bak does not have correct permissions. I tried deleting that file and restarting the conversion and keep getting that message. currently I'm waiting on a call back from Sage (you only get one try so stay by your phone {ANGRY EMOGI} so if anyone has any ideas let me know also every time it errors out I look at the IM_OPTIONS table and it says version 5.0 and if I don't change it back to 4.1 I get a message that there is nothing to convert.

And blank key records in IM1 or whatever the Misc Item file used to be?

good thought but no blank key there. I've deleted all the framework files that were created and left empty and I've restarted the conversion. it takes about 10 minutes to finish checking for out of balance inventory files, so I'm waiting on that to finish.

have you checked the windows permissions for that particular location?

It has been my experience that you are better off upgrading to 4.5 then to 2018

I agree with with @KristenRoland . I've run into the same issue twice where IM1 largely didn't convert to CI_Item (ItemCode and and the first couple of fields only the rest blank). Convinced it was conversion bug but didn't troubleshoot conversion programs too far. One time from 3.74 and other 4.early, both to 2016. Both times resolved using 4.50 with latest PU as intermediate conversion step.

Thanks Kristen and Alnoor. I'm installing 4.5 with PU 8 now and I'll start all over and learn from that mistake!

This is the upgrade from hell! I've installed 4.5 then installed PU8 migrated data files (took several hours) now when I try to convert data files I get Error #12 SO0xxx.soa Not found or already exists. Like it is looking for the legacy options file SOZero just for grins I tried taking a copy of SO_Options.m4t and renaming that file to SO0xxx.soa and restarted conversion and then I get RA0xxx.soa not found. the company maintenance screen shows all modules are at level 4.1 but it seems to act like it is expecting legacy options tables in all the non-legacy modules. have not found anything on Sage KB which is not surprising since this is happening in 4.5 which is not supported. I hope someone has run across this, or can think of something obvious I'm forgetting with version 4.5 otherwise I'll be calling Sage again tomorrow.

I just upgraded a customer from 4.4 to 2018 yesterday but you can't migrate from 4.4 to 2018 (said it had to 4.5 or higher) so I downloaded and installed 2016 which did let me migrate and convert. No data issues although they are core only (no IM, SO, PO). The migration to 2018 then went smoothly although they are missing an AR invoice form and due to IT, I can't copy it from the old server to the new. Another project for today.... I might add, they were pleased with being live (there was no parallel testing) but didn't seem overly impressed with the new version. ""That's it?

I'm using @BillPfahnl trick of uploading a bundle of 2017 to the server, don't install but just modify the icon to startup 2017 and migrate the data files. Then hop into 2018 and migrate/convert from 2017. My last 2018 upgrade didn't have Inventory. My game plan is that if the customer is on 4.5 I'll load PU8 otherwise I'll use the 2017 bundled program as the interim. I just zipped up a relatively blank 2017 off my local computer and uploaded to the customer. Be sure you DFDM the registration as I don't think swapping keys updates the registration name on 2017 which in turn gets picked up going into 2018.

I have an update. I went back to version 4.1 last night and ran rebuild key files on most modules in Sage, took a long time but it was probably well worth it in this case. I found corruption in the Inventory files and I'm pretty sure that was the cause of my initial error when upgrading to 2013. I'll mention that I did not rebuild sales order files - I remember that in 4.1 rebuild of the sales order files sometimes turned ugly. I've re-migrated and in the process of reconverting the data to 2013 and this time I can see inventory is actually recalculating all the period data, beginning balances etc. so I think I'm in better shape at this point. I will post an update later. (good or bad )

Hard to imagine that anyone stayed on v4.1 for that long. That was the version from hell!!

Final answer here! The upgrade is complete I think. the client is now testing data. Moral of this story is to run rebuilds on old versions prior to starting the initial migration. I used to run rebuilds before all upgrades but it became time consuming and somewhat unnecessary in newer versions. But back in the 4.1 days it was necessary and now I recall why I used to run them first. this was the ""test"" upgrade so I will have to go through this all again when they are done updating integrations, reports, and forms.