Prepare 3CX Data for Migration

Before migration, you need to define which 3CX data need migrating and have your clients prepare the data within 3CX for migration.

Step 1. Confirm the migration scope with your client

Item Included
User account
Account information:
  • Extension number
  • User name
  • Phone number
  • Email address
Basic settings:
  • Whether to enable voicemail
  • Voicemail pin
  • IP phone registration credentials
Preference & advanced settings:
  • Status and forwarding rules
  • BLF keys
  • User role
Note: After-migration, users can set their status, forwarding rules, and BLF keys, while system administrators can create and assign user roles.
Contacts
Contact information:
Basic settings
Global business hours & holidays
Voice prompt files
Note: To upload voice prompt files, you need to obtain the audio files from your client in advance.
Call feature settings
Digital receptionists (IVR)
Ring groups
Call queue
Voicemail
System security settings
Allowed country codes
Blacklisted numbers
IP Blacklist
SIP trunks
Basic information:
  • ITSP hostname
  • Authentication credential
  • DID number
Advanced settings:
  • Caller ID
  • Call options
  • Inbound parameters
  • Outbound parameters
Note: After migration, system administrators can configure the advanced settings for SIP trunks as needed.
Call control settings
Inbound rules
Outbound rules
Emergency number
Integrations
CRM / WhatsAPP / Microsoft Teams integration
Note: After migration, system administrators can set up the desired integrations.
Call data
Call history / Chat history / Recording history
Note: Confirm with your client whether to backup the call data.
Voicemail
Recordings

Step 2. Have your client prepare the data for migration

After the migration scope is confirmed, you need to have your clients verify and clean up the source data within 3CX to ensure the accuracy and conciseness of the data to be migrated.
  • Confirm all settings within 3CX are current.
  • Retain only the necessary data in 3CX system, and delete any deprecated, duplicate, and no-longer-needed data.

    For example, delete all the deprecated user accounts, inbound rules, and outbound rules.

  • Document any newly added data throughout the migration process.

    This will allow you to promptly capture the additions and migrate them to Yeastar Phone System, ensuring the integrity of the migrated data.