Data Import/Package Migration

Overview

This feature provides an easy and fast way to perform package migrations in Emersion via a bulk upload tool.

This tool comes with a force_complete flag that can be used to process the migration immediately regardless of any dates set. When the flag is used, these are the expected actions:

• Source package subscription is cancelled effective immediately.
• Source package subscription's end date was set to the future date given in the import file.
• Destination package subscription is created and activated immediately.
• Package Subscription note created. This note can be seen in Cumulus:
  • under the Customer > Notes tab.
  • under source Package Subscription > Package Subscription Notes tab.

When the force_complete flag is not used, the following actions will occur:

• Source package sub is placed into a PendingProvCancel state, pending cancellation.
• Destination package subscription created and Preactive.
• Package Subscription note created. This note can be seen in Cumulus:
  • under the Customer > Notes tab.
  • under source Package Subscription > Package Subscription Notes tab.

Back dated migrations are not supported by this tool. Setting the migration date as the current date (today) is treated like a future dated migration and not supported.

The system utilises the Bulk upload processing notification event to send a notification with the results of the import attempt. See below for further information.

If the import is successful, the email notification will advise you when the import process is complete.
If the import is not successful, the email notification will send details of the records that failed validation and why.

Preparing your Data

To prepare your data for import, you will need to create a CSV import file or you can download the import file below. You will need to extract the csv file and save it.

There is a hard limit of 2,000 migrations that can be performed using this import tool. If you need to migrate more than 2,000 packages at a time, please create multiple import files. A single import file can have up to 9999 rows of data plus the header row.

Media:Package_migration_import.zip

Enter the data into the import sheet. Leave no rows blank. You must ensure the data meets all validation requirements. These are contained in the data definition table below. When you submit the data file for import, the system will parse the file looking for errors. If the system finds no errors, the system will import the notes into the system. The file needs to be error-free in order to import the data. In the event errors are found, no data will be imported into Emersion. Review the bulk upload processing notification email, correct the file and try again.

Importing your Data

To access the note import tool:

1. Log into Cumulus.
2. Nav: Admin > Bulk Import > Package Migration.
3. Click the Browse button and select the csv file containing the data you want to import.
4. If you want the bulk upload processing notification email to be sent to a different email address than the address defined in the event template, tick the Override? checkbox and enter an alternative email address. This will only apply for this upload. To change the email address for all future imports, you will need to change the recipient defined in the event template.
5. Press Submit

The system will validate the data and if no errors are found, the system will import the data. When the notification email is received, the process has been completed.

The system can parse for invalid data but it cannot check for data accuracy. Therefore it is strongly recommended that you check a few random records to ensure that the import was a success. If you find an problem, you cannot roll back the import.

You have two options should this occur:

1. Manually correct the data.
2. Request Emersion fix the errors for you. This can be submitted via work order ticket. Please include a note import file with the records that need to be corrected. Do not include details of any records that do not need correcting.

Bulk Package Migration Data Definition

This section contains a list of the required fields and a definition of what the system considers as valid data.

Bulk Package Migration Data Definition table

Data field	Description
ACCOUNT_ID	The ID of the customer. MANDATORY
PACKAGE_SUBSCRIPTION_ID	The old (source) package subscription ID. MANDATORY
NEW_PACKAGE_PLAN_ID	The ID of the package plan for the new (destination) package subscription. MANDATORY
NEW_CONTRACT_TYPE_ID	Provide a contract type ID if this customer's subscription has a contract. OPTIONAL
NEW_CONTRACT_END_DATE	Give the contract against the destination subscription an optional end date OPTIONAL
FORCE_COMPLETE	This is a boolean flag and tells the system to process the migration immediately or not. Enter: 0 = NO 1 = YES MANDATORY

Viewing the Imported Data

After importing data it is important to validate it was imported correctly. Choosing a random records and performing a visual check in Cumulus should reveal any mistakes relatively quickly that would be harder to see in an import sheet.

The Bulk upload processing notification event

Most of the bulk upload tools utilise the Bulk upload processing notification event to send a notification containing the results of the import attempt. An event template must be created and the event must be enabled before the import tool can be used.