Hello IFS Community!
I’m assessing a strategy for a legacy ERP migration into a PRODUCTION IFS APPS 10 (UPD16). This is a multi-tenant instance (many companies are running on this IFS instance). There is already one company operational and I am migrating company #2.
My question is this: we are considering two strategies
- Migrate this new company (let’s call it, company “A”) into PRODUCTION where the current company (company “B”) is operational. Do the migration and QA work directly in PROD. Once the GO-NO GO decision is made (if GO) then just start using PROD with no further delays. In this approach there is no freeze period for company “B”
- Migrate this new company in a staging environment that we will clone off PRODUCTION (so all of company’s “B” data is there), freeze PROD during migration (tell users of company “B” site is off-limits for now). Do the migration and QA work there (in staging). Once the GO-NO GO decision is made (if GO) then clone back the staging into PROD and unfreeze PROD for Company “B”.
Obviously approach “1” is more convenient for company “B” as they will be able to use the PROD environment during migration (performance can be an issue as both OLTP work from operations and BATCH work from migration compete for resources, but I’m leaving those considerations out of here for simplicity’s sake). The reason why approach “2” was suggested is because rollback would be way easier there, no need to perform a backup just before migration starts nor there is a need to restore that backup should QA work would deem for any reason a NO-GO.
Has anybody done Legacy to IFS migrations to environments where other companies are up and running? if so, what strategy worked for you?
Thanks!