Alpaca 5.0

Group Migration

Introduction

A BroadWork's Group can be highly customized with Users, Devices, and various service instances such as Call Centers. This configuration process can be extensive and time consuming. If later the Group needs to be moved to a different Service Provider or Enterprise the process of deleting the Group and rebuilding in another is a disruptive operation. Collecting all the details from the source Group to perform the migrate is time consuming. And tracking down information such as User passwords to migrate is exceptionally difficult.

This feature, Group Migration, provides a function that allows BroadWorks' Groups to be moved from one Service Provider or another Service Provider without a loss of Users, Devices, settings, passwords, greetings, or corresponding attached files.

Procedure

Group Migration performs a sequence of information retrieval prior to migration to ensure that the Group meets the set of requirements that will allow the Group to successfully migrate to the Destination Service Provider. There are two types of restrictions that would prevent a valid migration - Requirements and Encumbrances. If either one of the restrictions contains errors then the migration will not be allowed to procede.

  • Check Migration Validity
  • Remove Users from Group
  • Remove Group
  • Remove Phone Numbers from Service Provider
  • Add Phone Numbers to destination Service Provider
  • Create New Group
  • Authorize Services and Service Packs
  • Add Group Settings that need to be added before Users
  • Add Devices
  • Add Users
  • Add Service Instances
  • Add Device Users
  • Add Group Settings that need to be added after Users
  • Add User Service Settings
  • Add Group Service Settings
  • Add Credentials

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

These items are not included in Group Migration.

  • Trunk Group User Creation Tasks

Requirements

Requirements are restrictions that are determined by inspecting the desired Destination Service Provider to determine if the Group can be moved into the Destination Service Provider successfully.

  • User Requirements
    • If one of the User's within the Group have limiting requirements from this migration type then the Group also has requirements.
  • Office Zones
    • The Office Zones available to the Source Group must also be available Destination Service Provider.
  • Domains
    • The Domains that are available to the Source Group must also be available in the Destination Service Provider.
  • Service and Service Pack
    • Services and Service Packs that the Source Group has available must also be made available by the Destination Service Provider.
  • Route Point External System
    • The Route Point External Systems that are available to the Source Group must also be available in the Destination Service Provider.
  • Meet Me Conferencing Ports
    • If the Source Group has Meet Me Conferencing Ports allocated to it then the Destination Sevice Provider must have at least that many ports availble for allocation.
  • Network Class of Service
    • The Network Class of Services that are available to the Source Group must also be available in the Destination Service Provider.
  • Communication Barring Profile
    • The Communication Barring Profiles that are available to the Source Group must also be available in the Destination Service Provider.
  • Schedules
    • The schedules contained within the Group’s Source Service Provider and System must also be contained within the Groups’s Destination Service Provider and System.
  • System User Limit
    • The Destination System must have sufficient user availability to perform the move.
  • Extension Length
    • The Destination Service Provider must have a valid extension length for the Group.

Encumbrances

Encumbrances are restrictions that are contained within the Group's settings. These restrictions do not require a Destination Service Provider to be determined and can be checked in advance for potential migration targets.

  • User Encumbrances
    • If one of the User's within the Group have limiting encumbrances from this migration type then the Group also has encumbrances.
  • Route Point
    • If the Source Group is using a Route Point, the Group cannot be migrated.
  • System or Service Provider Access Device
    • If the Source Group is using System or Service Provider Access Devices then it cannot be migrated.
  • Hunt Group
    • If a Hunt Group within the Source Group has Users from another Group, then the Group cannot be migrated.
  • Auto Attendant
    • If a Source Group Auto Attendant is monitoring Users outside of the Source Group, then the Group cannot be migrated.
  • Shared Call Appearance
    • If a User in the Source Group has a Shared Call Appearance with a device that is shared with Users outside of the Source Group then the Group cannot be migrated.
  • Busy Lamp Field
    • If a User in the Source Group has a Busy Lamp Field that monitors Users outside of the Source Group then the Group cannot be migrated.
  • Meet Me Conferencing Bridge Hosts
    • If the Source Group has a Meet Me Conferencing Bridge that has hosts that are outside of the Source Group then the Group cannot be migrated.