Best practises for migrating on-

prem SunSystems/Q&A (Vision)

to Infor Saas SunSystems 6.4 and
Q&A 11
8 May 2020
Best Practices Migrating On-prem to Infor
Cloud
1. Current on-prem test environment (e.g SunSystems 6.1 and Q&A 10)
a. Perform housekeeping of data such as deleting the temp tables or work tables
b. Clear the data down as far as possible. Archived data can be taken to Infor Cloud and the general recommendation is to
take 3 years worth of data
c. Validate the data
d. For the above, please refer to Infor SunSystems 6.4 Upgrade Document.pdf and reference to page 17 to page 19 on the
upgrade pre-requisites

2. Current on-prem test environment (Latest – SunSystems 6.4 and Q&A 11.3)
a. Perform the post-upgrade tasks as stated in Infor SunSystems 6.4 Upgrade Document.pdf and reference to page 42 to
page 43 on the upgrade pre-requisites
b. Validate the data including functional testing
c. Perform a full DB backup on prem and before kicking off the backup process, ensure all users are logoff, no users
present in User Operator Activity screen and Q&A screen, all jobs are ceased and all services down. It is also
recommended to clear any locking or blocking observed in DB level.
d. The patchset level of SunSystems and Q&A including Datalink and SQL version must be the same as of Infor Cloud test

Copyright © 2018. Infor. All Rights Reserved. (2)

Best Practices Migrating On-prem to Infor
Cloud
3. Moving the on-prem DB to Infor Cloud test
a. Webex session needs to be schedule with cloud ops to perform the upload of DB to S3 bucket. Incident
needed to be created with specific date and time to perform the upload by the partner.
b. Importing of the on-prem DB into Infor Cloud test environment. Incident needed to be created 2 weeks prior to
the import date and the date/time will be schedule by Infor Cloud DBA and this will be updated to the incident.
c. The import activities will take up to 12hrs to 18 hrs in Infor Cloud test

4. Infor Cloud test

a. Any sync issues of BU or data issues will need to be resolved by the implementation team
b. Implementation team identify any custom reports or custom forms that will need to be re-applied
c. Implementation team identify any interfaces, integrations or Transfer Desk automations needs to be
configured.
d. Create multi-tenant Infor Operating Services (OS) users and configure the roles
e. Create Query & Analysis users, profiles and enable end users to run Query & Analysis
f. Train and enable the users to manage and the usage
g. Refresh the on-prem DB to Infor Cloud test. Repeat 3a to 3c. Perform brief validation and testing.
Copyright © 2018. Infor. All Rights Reserved. (3)
Best Practices Migrating On-prem to Infor
Cloud
5. Moving the DB from Infor Cloud test to Infor Cloud Prod
a. Incident needs to be created 2 weeks prior to perform the backup of DB in Cloud test env by Cloud DBA
b. All users need to logoff and all services will be down during the backup process
c. This activity will take around 3 to 4 hrs

6. Infor Cloud Production

a. Incident needs to be created 2 weeks prior to perform the restoration of DB in Cloud prod env by Cloud DBA
b. The import activities will take up to 12hrs to 18 hrs
c. Any sync issues of BU or data issues will need to be resolved by the implementation team
d. Implementation team identify any custom reports or custom forms that will need to be re-applied
e. Implementation team identify any interfaces, integrations or Transfer Desk automations needs to be configured.
f. Create Query & Analysis users, profiles and enable end users to run Query & Analysis
g. Train and enable the users to manage and the usage

(Note:- The backup of DB from test env and refreshing the DB in production env should be performed one after the other within the 24 hrs
for go live preparation. Hence, it is extremely important to create these incidents 2 weeks in advance and you may suggest the date/time to
perform these activities in the incident)

Copyright © 2018. Infor. All Rights Reserved. (4)