Sage 100

Our procedure has been to make a copy of the production database then migrate and convert the production company for testing purposes. Resolve issues, then migrate and convert again. The company copy function does not copy forms and reports (although I think that used to be an option). Is there a way to copy these firms and reports so that we can compare apples to apples?

Because of all the system files, I make a conversion copy as you do, but during the initial migration, I migrate all of the companies to the new level. This moves everything for me. This allows me to convert and test everything. When go live day arrives, I just copy the MAS_xxx files and the paperless PDF logs.

Yes. We do too. My problem is the copy in the old version since it's missing the reports and forms.

copy the MAS_XXX\Reports (production) folder to the new MAS_YYY (copy) folder.

@GregStiles I don't think that will work. How do the Report system files get updated so we can 'see' the reports?

correct, we have always had the user manually type the report setting once and then it works from then on. I don't know any other way.

FWIW making a compete copy like Jeff suggested is a better way and is actually what we do as well.

Agree with complete copy. My problem is not in the migrated company but in the copy in the old version. Sage just confirmed that the forms and reports have to be defined in the respective modules, then we can copy the Reports folder on top. This means having to manually define over a hundred reports. Yuck!

What's the need for the company copy if the have a complete copy of the Mas folder?

That is exactly the reason why I migrate the complete installation the first time.

The reason we copy the production company is to permit comparison of control totals between versions. The production company in the old version can then be used while testing is completed and forms converted or redesigned. This virtually eliminates downtime for the accounting staff, excluding the effort it takes to test.

In most cases where you are migrating inventory you'll probably want to first migrate a test copy of the live data. Otherwise I've had the system make a bunch of adjusting entries to inventory. You also want a ""static"" copy of data so that the user can compare to be sure the detail transferred. If you migrate the live data you could wind up with a bunch of adjustments that you're not prepared to make yet. TL;DR: In order to migrate you may need to pre-migrate which often makes inventory adjustments.

Agree with @WayneSchulz on this. We have finished comparing totals and the only discrepancy found was a very small difference in COS on one inventory sales report. So small the controller passed on further investigation. Onward!

I think we are all talking the same. I create a TST company from the production company in the old version of Sage. I then migrate ALL companies to the new level. We then use the TST company between the two systems for control total purposes.