Move Service from package X to Package Y

[Blesta Addons]

We want to talk about a experience of migrating services from package X to package Y .

Normally blesta allow admin to change package service via upgrade/downgrade in edit service, but this action is restricted to :

 - The package Source/destination should has the same Module .
 - the package group should has enabled "Allow Upgrades/Downgrades between Packages within this Group" .

without this two condition you can't move/migrate service to any other package, and in blesta v4 is more complicated with the new restricted mode that disallow change package's module if the package used by a service either active or canceled, this behavior has load a lot of request from our client to allow them change package module from module x to module y, and specially for client that are moving from other billing system, as the import manager assign service that hasn't a matched module in blesta to universal module, then they are stuck in universal module without any solution, we inspired the idea from the core plugin "reassign pricing", we have tweaked the plugin to allow not only change pricing_id and module_row_id , we have added support to update the package group id and the service fields to match the new module service fields, it took from us a lot of time and work to make it workable and supporting all modules via a simple config file. this plugin was tested and we was  able to migrate service from package to package .

the only issue we have is that we should do this for every service, no mass change possible due to some limitations and service fields issue for new module.

we will release the plugin freely soon .

[Paul]

Do you remap service field data for all services that get a module change? It's one of the reasons we don't allow it currently, because it could potentially create issues with those services. I agree something needs to be done though, so looking forward to seeing what you're working on!  

[Blesta Addons]

Just now, Paul said:

Do you remap service field data for all services that get a module change? It's one of the reasons we don't allow it currently, because it could potentially create issues with those services.

yes we remap all the service i have attached a screenshot, this sample to migrate from virtualizor to proxmox  .

 

 

[Paul]

Just now, Blesta Addons said:

yes we remap all the service i have attached a screenshot, this sample to migrate from virtualizor to proxmox  .

 

 

Ah, very nice! So when you change it for a specific service, you can enter the new details for the new service fields.

[Blesta Addons]

Just now, Paul said:

Ah, very nice! So when you change it for a specific service, you can enter the new details for the new service fields.

Yes, the first idea was to create a map file for very module, but it was very complicated to match every field with source/destination module, as some module hs unique field and others has multiple ....ect , so finnaly we have opted for this solution to be sure the change service will not give any issue in the future .

[Blesta Addons]

Our second step now is to change the module for the package, normally what is the field we should take care of them if we want to change the package module ?

meta, module_row, module_row_id ?