Yeastar Cloud PBX Migration Overview

Yeastar supports migration from Yeastar Cloud PBX to the P-Series PBX system, which allows you to seamlessly upgrade to the latest P-Series platforms while retaining your existing configurations.

Requirements

Platform Requirement
Yeastar Cloud PBX Version 81.15.0.159 or later
P-Series PBX System
Note: The P-Series PBX system MUST be a new installation or factory reset.

  • P-Series Appliance Edition: Version 37.19.0.70 or later

  • P-Series Software Edition: Version 83.19.0.70 or later

  • P-Series Cloud Edition: Version 84.19.0.70 or later

Migration scenarios

You can migrate the Yeastar Cloud PBX to any edition of the P-Series PBX, including Appliance Edition, Software Edition, or Cloud Edition.

The table below outlines the main migration scenarios for moving PBX instances from Yeastar Management Plane (YMP) to the P-Series platforms.
Target Platform Scenario Instruction
P-Series Cloud Edition Full platform migration

Migrate from all PBX instances from your self-hosted Yeastar Management Plane (YMP) to your new self-hosted Yeastar Central Management (YCM).

 Migrate Yeastar Cloud PBX to P-Series Cloud Edition
PBX instance migration

Migrate all PBX instances from your self-hosted Yeastar Management Plane (YMP) to Yeastar-hosted Yeastar Central Management (YCM).

P-Series Appliance Edition / Software Edition PBX instance migration

Migrate individual PBX instances to standalone P-Series Appliance Edition / Software Edition

 Migrate Yeastar Cloud PBX to P-Series Appliance Edition / Software Edition

Migrate Yeastar Cloud PBX to P-Series Cloud Edition

Step 1. Configuration domain settings
To ensure a seamless migration and uninterrupted domain accessibility, keep domain names unchanged when migrating your Yeastar Cloud PBXs to P-Series Cloud Edition instances. To achieve this, complete the following domain-related configuration before migration.
  1. Collect required information for both the old and new platforms.
    • The IP address of the SBC server of Yeastar Management Plane (old platform)
    • The IP addresses of the SBC server and SBC Proxy server of Yeastar Central Management (new platform)
    • The domain name of the SBC Proxy server of Yeastar Central Management, which follows the format: *.proxy1.{cloudpbx_wildcard_domain}.

      For example, if the wildcard domain of the Yeastar Cloud PBX is *.example.com, then the domain name of the SBC Proxy server should be *.proxy1.example.com.

  2. Configure single domain DNS records for Yeastar Cloud PBXs.

    Create single domain DNS records for each PBX instance to be migrated, pointing its domain name to the IP address of the old SBC server. This ensures that the PBX instances remain accessible during the migration process.

    For example, 
    pbx1.example.com    -->    203.0.113.10
pbx2.example.com    -->    203.0.113.10
pbx3.example.com    -->    203.0.113.10
  3. Configure wildcard domain DNS records for the SBC server and SBC Proxy server of Yeastar Central Management.
    • Update the DNS record to point the wildcard domain name of Yeastar Cloud PBX to the IP address of the SBC server.

      For example, 

      *.example.com    -->   203.0.113.20
    • Set the DNS record to point the wildcard domain of SBC Proxy Server to its respective IP address.

      For example,

      *.proxy1.example.com   -->  203.0.113.21
Step 2. Deploy domain
After configuring domain resolution and obtaining the latest domain certificates, deploy the domains as custom domains in Yeastar Central Management.
For more information about the configuration, see Set up New Cluster Server Domain Names.
Step 3. Obtain backup files
Export backup files for your Yeastar Cloud PBX from the YMP server. For more information, see Obtain Backup Files for Yeastar Cloud PBXs.
Step 4. Update DNS records and system settings
After obtaining the backup of the Yeastar Cloud PBXs, proceed with the following steps to update DNS records and system settings for the original PBXs.
  1. Update system settings for the PBX to be migrated.

    To avoid SIP trunk registration conflict during migration, take one of the following actions:

    • Stop the original PBX system.
    • Alternatively, disable all SIP trunks on the original PBX.
  2. Remove the single domain DNS record for the PBX to be migrated.

    To prevent domain conflicts and ensure a smooth migration, delete the single domain records associated with the original PBX.

    Note: System downtime may begin at this point, as deleting the DNS record will make the PBX inaccessible via its domain name.
Step 5. Prepare target PBX
On Yeastar Central Management, create a P-Series Cloud PBX instance with the required firmware version, ensuring that it uses the same domain as the original Yeastar Cloud PBXs.
For more information, see the following topics:
Step 6. Restore backup
Restore the backup to the target P-Series Cloud Edition instance either through Yeastar Central Management or directly on the specific P-Series Cloud Edition instance. For more information, see Restore a Cloud PBX backup on P-Series Cloud Edition.
Step 7. Verify system after restoration
After restoring the backup, perform the following checks on the new PBX.
  1. Check if all supported settings and data have been migrated.
  2. Check SIP trunk registration status.
  3. Reboot IP phones for re-registration.
  4. Test internal and external calls.

Migrate Yeastar Cloud PBX to P-Series Appliance Edition / Software Edition

Step 1. Obtain backup files

Export backup files for your Yeastar Cloud PBX from the YMP server. For more information, see Obtain Backup Files for Yeastar Cloud PBXs.

Step 2. Adjust system settings on the original PBX
After obtaining the backup of the Yeastar Cloud PBX, take one of the following actions to prevent SIP trunk registration conflicts during migration:
  • Stop the original Cloud PBX.
  • Disable all SIP trunks on the original PBX.
Step 3. Set up target PBX

Install and configure the target P-Series Appliance Edition / Software Edition with the required firmware version.

For more information about the installation, see the following guides:
Step 4. Configure remote network access with the same domain
To retain your existing Cloud PBX domain names and avoid reconfiguring settings on connected devices or systems, complete the following steps on the target PBX:
  1. Assign a public IP address.

    Ensure the target PBX is assigned a valid public IP address.

  2. Bind domain name.

    Update your DNS records to point the original Cloud PBX domain name to the new PBX's public IP address.

  3. Set up domain and port forwarding on your network to allow remote access to the target PBX.
    For more information about the configuration, see the following topics:
Step 5. Restore backup
Restore a Cloud PBX backup file on the target PBX. For more information, see Restore a Cloud PBX backup on P-Series Appliance Edition / Software Edition.
Step 6. Verify system after restoration
After restoring the backup, perform the following checks on the new PBX.
  1. Check if all supported settings and data have been migrated.
  2. Check SIP trunk registration status.
  3. Reboot IP phones for re-registration.
  4. Test internal and external calls.