Migrating to a new CMS creates a new data source. To avoid mixing catalogues, orders and contacts from two stores, connect the new website to a separate Kiliba account.

Before the migration

1. Request the Kiliba account intended for the new website, or access to it. Do not reuse the old account identifier in the new module.
2. Include the relevant customer data in your migration plan, especially consent, unsubscribe and exclusion statuses. They must remain consistent in the new CMS before Kiliba synchronises them.
3. List what must be configured again in the new account: sender, visual identity, scenarios, calendars and promotional codes.

Connect the new website

1. Follow Create your Kiliba account and connect your store.
2. Install and configure the relevant connector: PrestaShop, Shopify or Adobe Commerce (Magento).
3. In Kiliba, check that the expected store, products, contacts and orders appear in the new account.

Before reactivating campaigns

• Check the sender, links, templates and promotional codes.
• Review consent and blacklist statuses before sending.
• Activate scenarios only after validating the new catalogue and audience.

Do not disconnect the old website until these checks are complete. To coordinate the cutover or request an additional account, use the Submit a request form and include the previous CMS, the new CMS and the planned production date.