2Migrating Legacy Data

Migrating Data Using Oracle Integration Cloud

Use Oracle Integration Cloud (OIC) to migrate your legacy data to Public Sector Compliance and Regulation (PSCR).

Using OIC integrations delivered by PSCR, you can migrate data for permits, inspections, attachments, fees and payments, property information, and custom fields.

Data Migration Process Flow

1. Review the PSCR objects for which legacy data migration is supported.

   For a list of supported PSCR objects, see Migrating Data to PSCR Using OIC.

2. Determine which legacy data needs to be migrated.

   Completed transactions will have no workflow associated with them. In-flight transactions will require configuring workflow and assigning migration statuses.

3. Define your PSCR workflow.

   See Setting Up Process Definitions for Workflow

4. Identify legacy transaction status values to migrate and the corresponding workflow process definition user task.

   See Assigning Workflow Status to Migrated Transactions

   Note: Make sure that the latest workflow process definition is selected for a transaction type before running a migration integration associated with it. Otherwise, you will be unable to migrate the workflow status associated with the transactions.

5. Review, configure and run the delivered OIC integrations.

   See Migrating Data to PSCR Using OIC.

6. Review and verify migrated data.

7. Run the Prepare Migrated Data for PSCR process.

   See Assigning Workflow Status to Migrated Transactions

8. Review the status of migrated transactions.

Assigning Workflow Status to Migrated Transactions

After you complete your data migration, run the Prepare Migrated Data for PSCR process to assign the correct workflow status to migrated transactions.

Mapping Legacy Statuses to PSCR Statuses

Before running the process, you need to map your legacy transaction statuses to the correct PSCR statuses through your OIC user tasks. For example, you might map your legacy permit statuses as follows:

Legacy Permit Status	OIC Process Definition User Task	PSCR Permit Status
Submitted	Accept Application	INS (Inspection)
Plan Review	Complete Plan Review	PLR (Plan review)
In Process	Issue Permit	SUB (Submitted)
Issued Permit (no inspection)	Complete Permit	CMP (Completed) or COO (Certificate of Occupancy)
Issued Permit (inspection required)	Approve Final Inspection	PTI (Permit issued)

You define this mapping by adding the PSC_MIGRATION_TASK as a custom property to your process definition tasks.

Note: For the first process definition task you must assign a value of SUB to the PSC_MIGRATION_TASK.

For more information on process definitions and custom properties, see Setting Up Process Definitions for Workflow and Using Custom Properties.

Running the Prepare Migrated Data for PSCR Process

1. Access the process by selecting Common > Prepare Migrated Data for PSCR

   You can also access this process from the Process Monitor. See Using the Process Monitor.

2. Select your process parameters on the Parameters tab.

   Page Element	Description
   All Permit Types	Select to run the process for all permit types.
   Specify Permit Types	Select to run the process only for the permit types you select in the Select Permit Types field.

   Note: Before running the process for all permits, it's recommended that you test the process with just a few permits to make sure that the process definition mapping is set up correctly.

3. On the Schedule tab, select the As soon as possible option to immediately add the process to the queue.

   Select the Using a schedule option to schedule when you want the process to run.

4. (Optional) Turn on the Notify Me When This Process Ends switch to send yourself a notification when the process finishes.

   Click Add on the Notification tab, and enter the recipient and conditions of the notification.

5. Click Submit.

   The process instantiates workflow for migrated transactions, and assigns the correct PSCR workflow user task to them.

   For transactions with statuses not mapped in the process definition, the process instantiates workflow and updates the migration status to undefined (U). These will need to be fixed manually by altering the workflow. See Using Workflow.