Migrating Existing Client Data to Allegro

Overview

With Release R69, Aria Allegro supports multi-tenant, true-SaaS deployment. 

To migrate an existing core Aria client with its Catalog and accounts to Aria Allegro, follow these steps:

1. Manage the DevOps ticket as detailed in section 1.4, “Adding a new client to an existing Allegro deployment.”
2. In the same or a separate DevOps ticket for data migration, provide these details:
   1. Enable the KAFKA topic for the Data feed LOM (migration) in core Aria: <topic for devops to determine> from the deployment.
   2. Enable the KAFKA topic consumer in Aria Allegro: topic for devops to determine> from the deployment.
3. Locate a link for the corresponding environment as shown in the UI snippet below. Add the client Number for data migration and say Get-Status. 
4. You can then start executing the extracts one-by-one as highlighted below.

<Advanced usage flag and Allowance/Accumulator flag update in core Aria OR create new plans for Allegro and migrate accounts in Aria to new plans>

Please note,

1. You must be connected to the Corporate VPN to use the extract tool below.
2. The URL should resemble the one in the UI snippet below, differing only in the domain name.
3. The LOM object sequence matters to avoid reprocessing errors. Execute them one by one in the order shown below.
   1. Catalog Objects
      1. Usage Types
      2. Services
      3. Plans
      4. Plan Rate Schedules
      5. Non-subscription Offerings (only if used for Commitments)
      6. Non-subscription offering rate schedules (only if used for Commitments)
   2. Account Objects (if required)
      1. Account
      2. Contact
      3. Contract
   3. Plan Instance (if required)
      1. Plan Instance