Merging Migrated Volunteer Data with Configuration

During onboarding a number of activities are happening in parallel. The Database Migration workstream builds towards preparing a complete set of migrated volunteer data, using the migration instance for review purposes. Meanwhile a wide range of training and setup activities are happening in UATSandbox.

VAL and PROD are both is created by merging configuration from a ClinSpark source instance with the migrated volunteer data.

VAL is created using by making a clone of PROD (for upgrades) or by making a clone of pre-PROD (for initial onboarding) instance as the configuration source.

...

PROD is created using Pre-PROD as the configuration source.

...

What Comes from Volunteer Database Migration

• Volunteers data. Note that the volunteer IDs are not carried forward from the source system, unless specifically migrated to a custom field

• Medical History config: medications, medical conditions, substance use parameters (dose, freq, route)

• Historical studies. Created in ClinSpark as archived studies and used to record past study participation

What Comes from the Configuration Source Instance

Everything except what comes from the migration and (noted above) is carried forward from the source instance. The configuration source instance’s database is the starting point for the merge process. All studies including their configuration and data are deleted (not archived), as well as any volunteers and medical history configuration.

Note that this means that application users, roles, general settings and all other configurations are carried forward from the configuration source instance.

Post-Migration Instance Setup

After the migration any required configuration changes to adapt the new instance to its purpose can be made. This typically includes user and role changes, setup of SSO, etc.