FreePBX | Register | Issues | Wiki | Portal | Support

Distro Conversion Tool and Commercial Module *configuration*


(Bruce Vrieling) #1

Hi all,

I have an existing 64-bit FreePBX 10.13.66 system which is working great.

I would like to move to the SNG7-PBX-64bit-1904 distro and move to new hardware at the same time. Because of this, I think I need to use the Distro Conversion Tool described here: https://wiki.freepbx.org/display/PPS/Elastix+and+PBXinaFlash+to+FreePBX+Distro+Conversion+Tool

For testing purposes, I installed SNG7-PBX-64bit-1904 on a test server, activated it, and went through the conversion process. It seemed to work great!

Question: I have a number of Commercial Modules and they are unlicensed on the new server (unsurprising). In order for the licensing to move over, I understand I have to remove the license files from the old server (well documented) and then move the licenses for the Commercial Modules to the new server. My questions below are basically concerning the migration of the configuration of these Commercial Modules.

I have the following questions:

  1. If the licensing matter is addressed properly, does the Donor Conversion Tool also migrate over the settings/config for the Commercial Modules? EPM is the big one for me.
  2. If yes, should I be moving the licenses for these Commercial Modules over BEFORE using the Distro Conversion Tool?
  3. If yes, would the process for the eventual move of the existing server to a new production server (after testing is complete) look something like this:

Activate new server
Unlicense commercial modules from old server (ie. remove hardware lock)
Add commercial module licenses to the new server
Use the Distro Conversion Tool to move the config from the old server to the new

If the Distro Conversion Tool does not handle the migration of the configs for the Commercial Modules, I am guessing I should instead migrate on existing hardware using https://wiki.freepbx.org/display/PPS/Upgrading+from+FreePBX+10.13.66+to+SNG7 and then move to new hardware as a separate process. Right? Or recreate the missing configs (eg. EPM) by hand?

Thanks for any pointers you can send my way!

…Bruce


(Lorne Gaetz) #2

Wiki page for moving licenses:
https://wiki.freepbx.org/display/FPAS/How+to+Move+a+PBX+Deployment+to+a+New+PBX

The distro conversion tool has a number of shortcomings which are discussed in this thread: How to: Upgrade FreePBX13 to FreePBX14 on Hyper V - Guide

You will see from the linked thread that EPM config is not migrated. In your situation, I would restore a full backup of your existing system to a new 13 install, and then upgrade to 14 on the new system. Once you are happy with the result, move the licensing over. The commercial module config should be all there waiting for you once the licensing is moved over.