Introduction

This document provides instructions for performing complete and partial migration of a Civic Platform deployment from one environment to another. This document does not address conversion of data from an external source into Civic Platform. Contact Accela professional services for conversion of data from an external source.

You migrate a Civic Platform deployment by moving information from a source database to a target database. To complete the migration, you set parameters specific to the new environment and reset certain Civic Platform operational parameters.

Civic Platform provides for migrating two types of database information; 1) configuration data and, 2) transaction data. Configuration data consists of two components; 1) information about the agency, module, record type and so forth (the Accela schema), and 2) information about the main console layout and main console setup (the Jetspeed schema). Transaction data consists of (auditable) information that Civic Platform generates on record type instances during their lifecycle from creation to destruction.

Note:
Agency configuration data equates to the 
serv_prov_code
level of your implementation. When you migrate agency configuration data you may affect interactions with other agencies that operate under the same super agency.

You can migrate configuration data and transaction data or only configuration data. You can also migrate a selective subset of configuration data.

The approach you use to export data from the source database depends on your database (SQL Server or Oracle) and whether you want to migrate configuration data and transaction data, only configuration data, or only a subset of configuration data.

If you want to migrate all configuration data and all transaction data, perform a full backup of the source database and restore to the target database (export/import or data pump if you are using Oracle) (Accela Database Migration). If you only want to migrate configuration data, you run a script to export the configuration data. You then import the configuration data into the target database (Configuration Migration). If you only want to migrate a subset of configuration data, use the Data Manager tool (Data Manager.)

Typical use cases for a database migration include the following:

  • Development to test and test to production. In both these use cases, you typically migrate configuration data only. Use Data Manager to make incremental configuration changes to the test environment or production environment without disrupting transaction data in your environment.

    Note:

    The Data Manager tool only migrates record type configuration data. You cannot use Data Manager to migrate configuration data related to the agency, module, or the main console layout and main console setup (the Jetspeed schema).

  • Production to production environment. In this use case, you migrate configuration data and transaction data.