Sage 100

HELP! I did a live upgrade last night (test was in Dec). 100 Advanced 4.50 to 2013. For live I only brought over the company data files and converted. Client started working and then told me they had changed custom office, added users, etc. in their 4.50 version and now they weren't showing up in 2013 (duh!). So because they have done work in the 2013 version this morning, and I can't export custom office 4.50 and import to custom office 2013, I made a backup of 2013 and migrated just system files from 4.50, installed product update and third party again. Now my MAS_xxx companies are all in the directory but in company maintenance, they no longer appear. SY_Company has all the data, is there any way to fix the lookup? I can create ABC company and hit activate and the modules appear but the company address, etc., possible preferences, emails, etc don't populate. Sage says we are never to remigrate system files nor are we to make a test install into the live install! So they were not of any help. I'm thinking of renaming all my live companies, remigrating system and companies again, then putting my converted companies back into place. Think that will work or any other ideas?

I feel your pain. I would backup the production company. Then rename the MAS,_xxx folder. Go to Company Maintenance and activate the modules. Copy the production data into the new company folder.

Update, SY_Company did get wiped out. I'm replacing with my backup sy_company, company codes reappeared, ran through a conversion (quick and successful), updating UDF's now. Anybody see any fallout happening from this process?

@NancyHanson I want to make sure I understand what SAGE told you! Did they tell you that when you created your 2013 test install, and I assume you made sure that all UDFs, custom Crystal Reports and Forms, and standard features were working in the 2013 test install. Did SAGE mean that you cannot re-migrate the data again from version 4.50 into your test install therefore making it ""LIVE"" 2013 system?

Mike - they indicated that a test is supposed to be done on the consultants system and the customer is to never see the test - it is only for verifying problems during migration/conversion. That aside, we can remigrate company data, but not system files if we've done the test on the customer's side. He also indicated we are to never make a test system into a live system. In my case, I remigrated company data but really should have remigrated system files since custom office, users, etc. all changed. It was truly an unbelievable conversation and I've worked with this tech person before and actually have quite a bit of respect for him, so either he wasn't understanding or there is a major issue with the process of testing, going live with upgrades. I also know I will never again click the No button to 'do you want to migrate companies that already exist in your new installation' - wipes out the sy_company file. Evidently you have to click Yes and then just unclick the actual company code you don't want to bring over. dumb! I've talked the customer into letting me totally redo the upgrade rather than just piecing it back together as PL_Form is wiped clean too with the system migration. ugh! haven't had a nasty upgrade in quite awhile!

Very strange. Who actually does testing on consultants system? How is the end user supposed to test???? Below is a link to one of Wayne's posts many moons ago. http://www.s-consult.com/support/activekb/questions.php?questionid=145 It may still be a good starting point.

Thanks Jeff, I talked the customer into letting me totally redo the conversion. They are a new customer also and I would rather them lose 2 hours of data entry then run into problems 2 days into the production environment. So remigrated system and company data (even though we're not supposed to haha!!). It was a bizarre conversation.

Unbelievable - your conversation with the Sage analyst. What universe are they living in?

@NancyHanson I applaud your approach. No one likes to deliver that message but in the long run, it's the best choice all around. Way to step up. Consulting isn't for pansies!

Thanks Shawn. And I'm really hoping the tech at Sage and I were just having a severe communication gap or he was reading a bunch of CYA statements taped to his monitor!