In preparation of Migration to FreePBX 17 - Commercial Modules/Hardware Lock/No Remaining Zend resets

Commercial Modules
,
1

I am getting ready to migrate all of my School Districts to FreePBX 17 over the summer. I am just wanting to get the best insight on how to make this as seamless as possible when migrating from our old VMs to the new Debian VMs and FreePBX 17. I figure others may be in the same boat so I thought I would ask on the forums.

I am wondering in particular, what best practice is in doing this. I know the Zend resets can be replenished. Do I need to do a support ticket? Or is this handled on the portal here:

Screenshot 2025-05-14 at 11.07.12 AM
Screenshot 2025-05-14 at 11.07.12 AM2204×360 16.9 KB

If I do select this option on the respective deployment now, will there be any impact on my PBX in production?

Then on the new machine what is the best course of action for migrating the deployment ID or does it need to be a new deployment ID?

Any and all tips for best practice are appreciated. I am well acquainted with FreePBX just wanting to be sure best practice is being used.

Thanks - To any that weigh-in.

2

Hi @TaylorDurden

Zend ID reset is not required to have support token or credit. Its free. You have to open a ticket day 1-2 before.

Best practice, Backup old PBX and restore to to new one VM side.
Power off old PBX, Activate new PBX with existing ID (Zend ID) be sure all paid modules your are seeing it at the new pbx side. Restore backup. You must give same IP address of the New PBX to not have any Phone registration issue.

I think thats it.

If something is happened and didn’t work alwasy you have old PBX for a backup. you can run it if you needed.

GL