The Migration database provides your agency with a temporary database to test migration data before running any migration scripts on your agency’s Production database.
Data in the Migration database will be a duplicate of your Production database (at the time of copy). Once your Production database has been copied, a script will be run to migrate the required data. It will then be verified to ensure the script has executed successfully and all data is as intended. This process may be repeated multiple times to ensure all data is correctly migrated and any issues have been resolved.
When is it upgraded?
Migration database – Upgraded as required to match Production.
Production database – Upgraded as required.
What will be disabled on upgrade?
The following functionality will be disabled in your Migration database as a precaution to allow for testing and training use:
External Communications (SMS, Client Delivery and Worker Delivery)
MS Exchange
Action Triggers
ORS/SRS
Credit Card
DSS
ClientConnect and Engage
General Ledger
What happens when the database is upgraded?
After your Migration database has been upgraded to a new version of Penelope:
Client email and phone details will be de-identified
Worker email and SMS details will be de-identified (all User Groups except System Admin and External Admin and ACSO).
Worker accounts in the following User Groups will be deactivated:
Admin Exec
Clinical Worker
Intake Mgmt
Volunteer
Any items in the communications queue (client and external) will be cleared
MS Exchange queue, error queue, and credentials will be cleared
Action Trigger queue will be cleared
ORS/SRS credentials will be cleared
Credit card production credentials will be cleared
DSS production queue will be cleared and synchronization deactivated
ClientConnect notifications will be deactivated, all accounts and product keys deleted
Engage client communications and Workflows will be deactivated
Attachments removed
Agency logo removed
Billing documents logo removed
After an upgrade what features can be re-enabled?
It is recommended that these features are not enabled during the migration process unless specific testing is required.
External Communications
MS Exchange
Action Triggers
General Ledger
It should be noted that ClientConnect and Engage cannot be enabled on the Migration database.