Migration from ProCall Enterprise to ProCall NEX

What should you bear in mind when switching from ProCall 8 (on-premises) to ProCall NEX (cloud)?

We have compiled the key points you should consider when migrating from ProCall Enterprise (on-premises) to ProCall NEX (cloud) below:

• Preparation
  This section describes points that could/should/must be considered before the actual go-live of ProCall NEX.
  
  
• GoLive
  GoLive refers to the "switchover" from the old to the new system.
  After that, ProCall NEX will be used in the customer environment instead of the old system.
  It makes perfect sense to address all points before GoLive. 

Since customer systems and environments vary greatly, this article is not intended as a step-by-step guide.
Its primary purpose is to highlight points that should be considered when migrating from ProCall Enterprise to ProCall NEX.
Depending on the customer's existing system, additional points may need to be taken into account (e.g. business process integrations) or may not be relevant.

Preparation

UCServer configuration

The configuration must be redone.

Users, groups

For users and groups, a distinction must be made between whether it is a local (file-based) user management in UCServer or whether a Microsoft Active Directory is connected.

Active Directory (AD)

Microsoft Active Directory (AD) cannot be connected to ProCall NEX. Alternatively, user management can be carried out via Entra ID. 
Further information: https://support.estos.de/en/procall-nex/inbetriebnahme-und-einrichtung-von-procall-nex/benutzerverwaltung-mit-microsoft-entra-id-einrichten

Local user management

With local user management, users cannot be transferred but must be re-entered in ProCall NEX.

Initial configuration 

The initial setup can be prepared if necessary.
If the phone number can be created on the PBX before GoLive in the lines (trunk), the initial setup can already be carried out and the users configured.

Further information on configuring ProCall NEX: https://support.estos.de/en/procall-nex/inbetriebnahme-und-einrichtung-von-procall-nex/konfigurieren-von-procall-nex

Journal

It is not possible to transfer the journal data from the old system.
The journal is written in ProCall NEX when the instance is created.

MetaDirectory

An existing MetaDirectory can be connected to a ProCall NEX UCConnect account.
Afterwards, please note that user management may need to be changed to "User management with ProCall NEX". 

Further information: https://support.estos.de/en/procall-nex/inbetriebnahme-und-einrichtung-von-procall-nex/kontaktdaten-mit-metadirectory-integrieren

The MetaDirectory should be reconfigured during or after the go-live, if necessary, as otherwise users will no longer be able to use the MetaDirectory until the go-live. 

GoLive

When switching to the new system, it should be noted that migrating from ProCall Enterprise to ProCall NEX not only replaces ProCall Enterprise, but also replaces the existing PBX with ProCall NEX.

When going live, the SIP trunk for external telephony (inbound and outbound) must be put into operation on ProCall NEX, and the ProCall clients must be registered on the ProCall NEX instance.  

SIP-Trunk

STARFACE Connect

The porting date is coordinated with STARFACE Connect. The porting date is therefore also the go-live date.

Different SIP-Trunk

When taking over the SIP trunk, the previous PBX must be logged out and ProCall NEX must be logged in to the SIP trunk. 

Before going live, please ensure if a static IP address is required. This must be requested and provided in advance.

ProCall Clients

For ProCall clients, it is recommended to uninstall the ProCall Enterprise client and then install the ProCall NEX client. 
You can find the downloads here: https://support.estos.de/en/procall-nex/procall-nex-downloads-und-anleitungen