Scheduling and Downtime Expectations
Migrations are usually scheduled outside of the end customers' normal business hours, which means nights and weekends. The average length of downtime to be expected should be an hour or so.
If a large amount of call recording or voicemail files are found, those files may be transferred after the initial migration, in order to prevent delays to the migration window and downtime.
Not Happy with New Interface?
Original system images will only be maintained for 30 days past the migration date. At the time of the migration, the original system will be preserved, and the new system will be created separately from the original. This will ensure that in the event of a failure, a reversion to the original version can take place.
Post-Migration Checklist
The following items should be checked after a migration to ensure that they are correctly set in place and operational:
- All audio greeting files for :
- Auto-attendants (IVR)
- Recordings
- Voicemails
- Inbound Call Flows
- Outbound Call Flows
Expected Change
It is possible that the phone system credentials may change. If the credentials change, those credentials will be found in the bvoip control portal.
Migrated to a Different Data Center
When migrating phone systems, there are a few items that can be expected to change in the process. In most cases, migrations between data center locations will also coincide with the phone system version being upgraded at the same time.
Additionally, a new Public IP address will be assigned to the phone system in the destination data center. FQDN should remain the same.
- If you do any QOS related routing on your firewall/routers, then those rules will need to be updated with the new PBX IP accordingly.
- If your dial tone or sip trunk provider requires IP based authentication or routing, those vendors will need to be updated with the new IP address.
Phone Provisioning Expectation
In most cases, if phones were provisioned properly from the start, the phones would re-register on their own. In many cases, phone re-provisioning is recommended, to make sure that the SBC addresses will update to the in-region data center location rather than routing to the original data center region.