Skip to content

Knowledgebase

Change, duplicate or convert an application hosting plan

hosting-suite, development

Application settings control how a plan is presented and how future installations are created. Changing those settings does not automatically rebuild existing websites. Treat product design, hosting package changes and application installation as separate decisions.

01 Edit an existing application plan

  1. Open the plan in App Hosting and review its current application settings, server placement, package and customer tools.
  2. Identify whether the change concerns future installations, the customer's available tools or the resources of existing accounts.
  3. Update the relevant settings. Review installation limits, HTTPS, language, PHP policy and customer installation permissions together.
  4. If changing the hosting package, decide whether to select Move existing accounts too. This is an explicit request to apply a package change to existing accounts.
  5. Save, then test a current service and a new test order. Confirm both behave as intended.

Changing a default installation title, folder or language does not rewrite the content of a site that already exists. Tool changes can appear when the customer next loads the manager. Package changes need successful provider-side processing and should be checked on the server.

02 Duplicate a plan safely

Use duplication when creating a related tier with different pricing, limits or tools. The duplicated plan starts hidden so it can be reviewed before customers order it. Check its name, product group, billing cycles, server placement, welcome message and application policy. Do not assume every copied value is suitable for the new tier.

03 Convert an existing hosting product

Conversion is intended for a compatible Hosting Suite product that should become a product tied to a selected application. Confirm its server group and application availability first. Converting changes the customer experience for services on that product, so test with a limited product before moving a large customer base.

Conversion does not automatically install the selected application into every existing account. Inspect each service and use Continue setup where appropriate. Check for existing websites and populated paths before installation. The welcome email is not automatically rewritten by conversion, so update it separately if it describes the previous experience.

What should support verify?

Check that existing customers retain the intended tools, package resources and site access. Confirm new orders use the new defaults. Record which accounts were moved to a different package and investigate any failed provider action individually. If a conversion needs to be reversed, first establish what has actually changed on the server; simply restoring a product label cannot undo a package change or remove an installed application.

Sources and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support