Our documentation has moved!

You are currently viewing a legacy version of our help articles.
For the most up-to-date version, please use the new Chargify Help & Support Site.
Follow

Clone Chargify Sites

Chargify makes it easy to run many sites/businesses in one account. There are several reasons you might do this, and we just made it a lot easier to make new sites. Here are some use cases:

 

  1. Cloning simplifies moving from test phase to production. Say you have a development site in Chargify with 50 products, a handful of product families, taxes - well, you get the picture; lots of configuration. Eventually everything is correctly set up and tested. You don't have to go through all of that work again to set up a production site - just clone the dev site!
  2. You have a set of products that belong to one brand, and you want to sell to another market under a different brand. Clone the site and change only what you need.
  3. You have a set of products that you wish to sell in another currency. Clone the whole site then just change the currency.


Site cloning is a great way to speed site creation and reduce errors when migrating. It also lets you keep your existing test site for future testing and debug.

 

How do I use it?

 

Just click the 'Clone' link on the site tile as shown below:

 

Screen_Shot_2014-02-27_at_6.11.55_PM.png

 

Then choose your cloning options:

 

Screen_Shot_2014-02-23_at_11.02.38_AM.png

 

The name field is the new name of the site that you want to create, and the subdomain field is the Chargify subdomain you wish to use (it must be unique to Chargify).

Using the toggles, you can choose which parts of the configuration to copy from the existing site to the new site. That configuration includes: Products, Components, Coupons, Custom Fields, Taxes, and Settings.

Subscriptions will not be copied over to the new clone. If need be, you may export the Subscriptions from your existing site and import them to the cloned version.  

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

8 Comments

  • 0
    Avatar
    Ryan Kelly

    OMG, we've been wanting this feature forever. We often need to clone current production site ID's over to resellers and the manual process of doing this was a bear. We actually found a piece of code on github that was supposed to accomplish this but required much modification.

    I LOVE THIS!!!!

  • 0
    Avatar
    Michael Conyers

    Excellent!

  • 0
    Avatar
    Steven Das

    I tried this procedure today, but it failed to copy over any of my products or components to the cloned site (which kind of misses the point...).

    Has this been tested recently?

  • 0
    Avatar
    Steven Das

    Ah, sorry; never mind!  It was just _slow _in copying over the products and components, and it took ~5 minutes for them to become visible in the cloned site.

  • 0
    Avatar
    Steven Das

    Bit of feedback on this feature:  it would be particularly powerful if, when cloning a site, the cloned site preserved all of the old component ID's auto generated by Chargify.

    The entire reason I looked into this feature was that right now, my colleagues and I have to change over not only the API v2 credentials, but also every single component ID when we switch from test to production.  If cloning actually preserved these component IDs from the original site to the clone, this problem would be solved automatically.

  • 0
    Avatar
    Tim Shnaider

    It would be sweet if it retained IDs on clone, but they are unique across the Chargify platform, not per site, so can't be re-used.

  • 0
    Avatar
    Jeremy Rowe

    Thanks for the feedback regarding the component ID's. Tim is right, they are unique in the system and we will not be able to copy them over.

  • 0
    Avatar
    Simon Stockdale

    Am I right in thinking that after I clone my first site four times for each of the other currencies, I'll need to make add any new products or make changes to any existing products five times over?

Please sign in to leave a comment.
Powered by Zendesk