upgrade question: data validation

When your company goes through an upgrade, do you validate the data on the upgraded system before letting users get in? Curious to see how you all handle this - who validates the data (IT? Users?)? Do you dump tables and compare data? Run reports? Screen shots? Is there a way to compare the entire source and target database to make sure all of the data is correct?

Find more posts tagged with

Comments

Legacy Contributor

Our users run reports such GL Balance reports, and AP vendor balance reports before the upgrade and they should match after the upgrade.

Legacy Contributor

We do record counts and then as sanders4 mentioned any reports that show totals or balances of various things. Balance Sheet, Vendor Balance, Inventory Valuation, Open Req Lines, Open PO Lines, RNI, MNR etc
We have about 20-30 reports we run.
We get the functional users to run in source and save in a shared location, and IT (AppSupport) then run the same reports with same parameters in target and compare.
We then give the end users the option to validate our findings or take our word for it, giving them ownership of Sign Off.

Legacy Contributor

We have a number of custom programs at Yale, so ITS ensures they work under the new Environment, before letting out to the populous.
At the same time ITS also processes a standard Test script in out TEST system, to enure sucessful processing.

Legacy Contributor

We run a variety of reports on the old and new systems, after the upgrade to confirm the upgrade properly converted all the data. If all is exact, we back up the new system and let users on. They run through some test transactions to confirm all is functioning as expected. If all is exact, we restore from the backup and GO LIVE on the new system.

We have similar tests, backups and restore while testing.

0911060553270289.pdf

Robert Canham

We do similar steps to Kelvin, however, we don't take a backup. Our users only do actions that either don't have any effect (inquires, drills, etc) or transactions that can be removed (i.e. create journal entry, release, post, backout, unrelease, delete).

Copyright © 2025 Infor. All rights reserved.