Sage 100

Upgrading from MAS 90 to MAS 200 _ Same version Customer is on 4.4.10 Sage 100 Std. We are moving them to Sage 100 Adv. If I use the Parallel Migration Utility to move all the Company Codes, System files (Users and Roles), VI jobs and Crystal reports will anything in the MAS90 program migrate and overwrite anything in the new MAS 200 installation making it unusable?

I have done this successfully on V4.3 Std to 4.5 Adv, have not tried on 4.4.

I think I had an issue with this in 2013. Definitely backup the MAS_System, Home, and wksetup folders in Sage 100 Adv - I think I had to restore the SY_System table after the migration and the wksetup folder. I have a note from this upgrade that says... Drop everything in except for HOME and Uninstall folders. I'm in the middle of about three things and can't remember what that means - but I would be prepared for issues if you;re going to 2013/5.0

Can't you just copy 90 to the new location then install Library master and system set up over it??

Just migrated a customer from 4.4 Standard to 2013 Advanced without major issues. Biggest headache was having to redo some forms that threw errors during printing (AP and PR checks). Customer didn't have any UDS's, so not sure how that would go.

interesting - when I did this a few months ago the migration of the 4.5 mas90 system files did replace some things in 5.0 advanced - it no longer thought it was advanced. And then i think I did try to reinstall LM and it wouldn't work. It was a pain for me.

Had to start a case with Sage. No solution yet. Installed and registered MAS200. After migrating the first Company Code, the MAS200 Registration was no longer recognized (as Eric pointed out) and the Admin password is reset to the source data password. Have to open MAS in MAS90 mode. Migrated Company data appear in both Windows Explorer and DFDM but Company Codes do not appear in Company Maintenance even if you manually type in the Company Codes so can't convert. Sage has worked on this for over 3 hours so far with no solution. Also during migration we get an PHYSICAL UPDATE ABORT: Sy_SagePEPTask which I think Sage said has something to do with the Sage Monitoring program.

Problem has been resolved. We manually reinitialized the Sy_SagePEPTask in the source MAS_System file and migrated again. Fixed everything except overwriting the Admin password. I changed the Source Admin password to 12345678 before migrating because no one remembered what it was change to by IT.