Sage 100

We have a client that, through acquisition, has two MAS 90 systems, one on 4.05 and one on 4.3. The 4.05 system is to be retired. We are upgrading to 4.4 and used parallel migration to bring both sets of companies (total about 100) to the 4.4 system. Things went well on the first migrate and data conversion of both sets of companies. When we attempted to do a final migrate, the set migrated from 4.3 came over fine but the set on the 4.05 server gives us ""The company key already exist on the target installation and will not be migrated"". I checked the KB and found two articles. Res ID 535281 which says the Error occurs because the company has already been recently migrated over. Would need to edit the sy_migratedcompany.m4t file and remove the company for the list. 1.Go into Library Master | Utilities | Data File Display and Maintenance 2.Browse into the MAS90 | MAS_System | SY_MigratedCompany.m4t 3.Press the lookup button and search for the specific company code and remove The companies don't show in the SY_MigratedCompany.m4t so that didn't help. They also offer Res ID 520895 regarding 4.4 Beta which says ""Based on reported case, this error was happened when re-migrating an existing company without system files, to resolve manually copy MAS_XXX from the prior install to 4.40 install and convert data."". I did a manual copy, but did not remove the companies, just copied over them. The conversion of the data for the 4.05 companies appeared to run normally. The client reports that GL seemed fine but the data for AP, AR and BR was old (from the first conversion). All companies from the 4.05 set have all or a subset of GL, AP, AR, BR and PR. I am thinking I should have removed the destination data before doing the manual migrate. The 4.05 companies have a reports folder in 4.4 and I have backed up those. Has anyone had a similar experience or did I just miss a KB article? Thanks.

No, but let us know how the second attempt goes after deleting the MAS_XXX folder.

I might try migrating the 4.05 over to join his new stepbrother on 4.3 then do a final migration of both companies from 4.3

Thanks for the replies. Deleting the application data folders did the trick. Left the reports folder intact. Manually copied the 4.05 data folders to 4.4 and the conversion resulted in good data in all modules. Only overwriting the folders with 4.05 data must have left a few 4.3 files that convinced MAS the conversion wasn't necessary or ??? I am still not sure what happend to the ability to migrate, especially when it worked on the first go round and not the second. Any two MAS installs would likely have some duplicate company keys. I would expect by design the migration program would deal with the company code and just generate a new company key in the destination install. It's seems like there might be a difference in the two migration routines that either don't allow companies that already exist (used the first time) or allow companies that already exist (used the second time).

I would like to try the move just to 4.3 to see if it would work. This client has a single Accounts Receivable statement format used for the 4.3 companies that automatically inserts a Logo based on Company Code. If I had moved the 4.05 data into 4.3, I would have had to deal with this real time. By working with it in 4.4, I had time before the final migrate to figure out how they did it and isolate the 4.05 companies from using a statement that went looking for a non-existant logo. When the dust settles and I have time, I would like to try it. From a poster on the Community, It's always fun to learn new things.