Group To Enterprise Migration
Introduction
A BroadWorks's Group can be highly customized with Users, Devices, and various service instances. The configuration process can be extensive and time consuming. If the Group was originally created within a Service Provider, but now needs to exist within an Enterprise, the manual process of achieving this can be arduous.
This feature, Group to Enterprise Migration, provides a function that allows a BroadWork's Group that is currently within a Service Provider, to be moved out of that Service Provider to an Enterprise that was created based on the settings of the Group to be migrated. There is also an option to split the Group into multiple Groups
Process
Group To Enterprise Migration can be accessed via the Group To Enterprise Migration button within the Actions tab on Group page. Note that you can return to any previously completed step by clicking the check mark next to the step name.
- Once on the Group to Enterprise Migration page, enter the name of the Enterprise you wish to create. Note that this must be a unique Id.
- In the next step you can split up the Groups if you wish. To split up the Groups, enter a new Group Id in the box and press add. You can add as many Groups as needed. Once the Groups have been added, you may drag and drop the Users to the desired Group.
- Click Next Step to begin the encumbrance check. If no encumbrances are found, the next step will appear. Otherwise you may not proceed until the encumbrances are resolved.
- The requirement checks will begin right after the encumbrance checks pass. If no requirements are found, the next step will appear. Otherwise you may not proceed until the requirements are resolved.
- If all checks pass, the migrate step becomes available. Click Migrate To Enterprise to begin the migration process.
- After the button has been pressed, you will be re-directed to the task page where you can monitor the status of the migration.
Background Procedure
Group to Enterprise Migration performs a sequence of information retrieval prior to migration to ensure that the Group meets the set of requirements and encumbrances that will allow the Group to successfully migrate out of the current Service Provider into a new Enterprise and possibly split into multiple Groups.
- Retrieve Group Information
- Check Migration Validity
- Remove Users from Group
- Remove Group
- Remove Phone Numbers from Service Provider
- Create New Enterprise
- Authorize Services and Service Packs
- Add Enterprise Settings
- Transform the single Group into multiple Groups (optional)
- Add Service Settings
- Add the Group(s) to the new Enterprise
Recovery
Following the information retrieval process the full details of the Group are backed up for recovery purposes. The settings information retrieved is backed up as JSON. Announcement files and device configuration files are backed up in their original format. These files collectively can be used for recovery purposes.
Limitations
Encumbrances
- Encumbrances are restrictions that are contained within the Group or Users settings. These restrictions do not require a Destination Enterprise to be determined and can be checked in advance for potential migration targets.
User Level Encumbrances
- Call Center Encumbrance - If one of the User's who is being migrated out of the Group is an Agent or Supervisor on a Call Center,then the Migration is encumbered.
- Hunt Group Encumbrance - If one of the User's who is being migrated out of the Group is an Agent on a Hunt Group,then the Migration is encumbered.
- Meet Me Conferencing Encumbrance - If one of the User's who is being migrated out of the Group is a Host on a Conferencing Bridge, then the Migration is encumbered.
- Call Park Encumbrance - If one of the Users who is being migrated is assigned to a Call Park, then all other Users who are assigned to that Call Park must also be migrated. The Call Park may not have Users who are not being migrated assigned, otherwise this is a migration encumbrance.
- Group Paging Encumbrance - If a User who is being migrated out of the Group is included in the Originators or Targets List for a Group Paging, then the migration is encumbered.
- Collaborate Bridge Encumbrance - If one of the User's who is being migrated out of the Group is a Owner on a Collaborate Bridge, then the Migration is encumbered.
- Find Me Follow Me Encumbrance - If one of the User's who is being migrated out of the Group is in a Alerting Group of a Find Me Follow Me, then the Migration is encumbered.
- Call Pickup Encumbrance - If one of the Users who is being migrated is assigned to a Call Pickup Group, then all other Users assigned to that Call Pickup Group must also be migrated. The Call Pickup Group may not have Users who are not being migrated assigned, otherwise this is a migration encumbrance.
- Trunk Group Encumbrance - If a User who is to be migrated belongs to a Trunk Group or Enterprise Trunk or is a Pilot User on a Trunk Group, then the migration is encumbered.
- Device Encumbrance - If a User who is being migrated is attached to a device, all other Users who are attached to the same device, must also be migrated. If the device has Users who are not being migrated, then the migration encumbered.
Group Level Encumbrances
- Route Point Encumbrance - If the Group contains a Route Point, the migration is encumbered.
- Device Encumbrance - If the Group uses System or Service Provider level devices, the migration is encumbered.
- Attendant Console Encumbrance - If a Group's Auto Attendant monitors Users outside of the Group, the migration is encumbered.
- Shared Call Appearance Encumbrance - If a Users in a Group belong to a SCA shared to devices outside of the Group, the migration is encumbered.
- Hunt Group Encumbrance - If a Group's Hunt Group has Users from another Group, the migration is encumbered.
- Meet Me Conferencing Encumbrance - If a host on one of the Group's Meet Me Conferencing Bridge belongs to another Group, the migration is encumbered.
Service Provider / Enterprise Level Encumbrances
- External Authentication Encumbrance - If external authentication is being used, the migration is encumbered.
Requirements
Requirements are restrictions on migration that are determined by inspecting the desired Destination Enterprise to determine if the Group can be moved into the Destination Enterprise.
- Enterprise ID Requirement - The provided Enterprise ID must not belong to another Enterprise within the System, otherwise the migration has requirements that are not met.
- Group ID Requirement - The provided Group IDs must not belong to other Groups within the System, otherwise the migration has requirements that are not met.