> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/css/producthero-migration/migrate-from-producthero-to-channable.md).

# Migrate from Producthero to Channable

Learn what happens when your Producthero account moves to Channable, and what to expect.

[Producthero and Channable](https://www.channable.com/press/channable-acquires-producthero) are joining forces to provide you with a more powerful, all-in-one multichannel eCommerce platform. As part of that, we're moving every Producthero customer to Channable CSS in batches.&#x20;

{% hint style="warning" %}
You don't need to do anything [until we email you](#what-to-expect).
{% endhint %}

{% hint style="info" %}

#### Are you an agency?

After migrating and setting up your account, follow [Organize agency clients after migrating](https://helpcenter.channable.com/css/producthero-migration/migrate-from-producthero-to-channable/organize-agency-clients-after-migrating.md).
{% endhint %}

### What to expect

We'll email you three times:

1. **Your migration period**, with the dates we'll move your account.
2. **Account migrated**, when your account is in Channable.
3. **Switch confirmed**, when Google has switched your merchants from Producthero CSS to Channable CSS.

{% hint style="info" %}
We send these to your Producthero admin billing email address, or to the address that accepted Channable's Terms and Conditions and Privacy Policy.
{% endhint %}

### What happens to your account

{% columns %}
{% column %}
**Your optimizations will move with you**

Your Google connection, supplemental source, and optimizations all move to Channable and keep working.
{% endcolumn %}

{% column %}
**Your ads keep running**

The migration and switch to Channable CSS won't pause or change your paid Shopping campaigns.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column %}
**We request the CSS switch for you**

You don't need to approve a switch in Merchant Center.
{% endcolumn %}

{% column %}
**You move to** [**Channable CSS pricing**](#what-happens-to-your-account)

Each active shop is added to your plan: a standalone Merchant Center account, or a registered sub-account in a multi-client account.
{% endcolumn %}
{% endcolumns %}

### What you'll need to do

After the third email, follow [Complete your migration from Producthero](https://helpcenter.channable.com/css/producthero-migration/migrate-from-producthero-to-channable/complete-your-migration-from-producthero.md).

### Billing during the move

* Producthero sends up to two final invoices.
* Channable sends your first invoice at the end of the month you migrate. After that, we invoice on the 20th of each month for the following month.
* You won't pay Producthero and Channable for the same period.

For payment methods and invoices, see [Billing and payment](https://helpcenter.channable.com/account-billing/manage-your-subscription/billing-and-payment).

### Migrate sooner

We're moving accounts in an order based on how each one is set up. To ask for an earlier date, email Producthero support at <support@producthero.com>. They'll check whether your account can move sooner.

### Get help

* **Before your migration:** <support@producthero.com>
* **After your migration:** <support@channable.com> or +31 (0)30 260 08 21

For quick answers, see:

{% content-ref url="/pages/CYyXB1jfeaOGuPLrLTOo" %}
[Producthero to Channable migration FAQs](https://helpcenter.channable.com/css/producthero-migration/producthero-to-channable-migration-faqs.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/css/producthero-migration/migrate-from-producthero-to-channable.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
