Transferring the user base between different Leeloo.AI platform accounts

Transferring the user base between different Leeloo.AI platform accounts

UA

image-20240611-123449.png

US

image-20240611-123805.png

RU

image-20240611-131051.png

UA

image-20240611-123449.png

US

image-20240611-123805.png

RU

image-20240611-131051.png

1. Introduction

Definition

“Transferring the user base between different Leeloo.AI platform accounts” is the operation of migrating subscribers and their connected bot from one platform account to another. It is a tool of the Manage stage that allows the accumulated subscriber base and continuity of communication to be preserved when the legal or operational account is changed.

Technically the transfer consists of two linked operations: (1) disconnecting the bot on the source account and connecting the same bot on the destination account — without creating a new bot on the messenger side, (2) exporting the list of subscribers from the Audience module on the source account and importing the same file on the destination account. The transfer touches the Audience, Communication Channels, Sales Tunnels modules and LGT — on the destination account a prepared tunnel and LGT are required, into which the imported users will be subscribed.

The B2B operator (company owner or Leeloo.AI administrator) is the only party that initiates and performs the transfer. The operator contacts platform technical support to coordinate the source and destination account emails, filters the base by the required bot in Audience, launches the export, prepares the import file and re-subscribes users through mass actions. All steps are performed manually through the platform UI — there is no automatic transfer between accounts.

Audience section

The B2C client (subscriber) does not interact directly with the transfer procedure — for the subscriber the operation is transparent. After migration the same bot in the messenger continues to work with the same chat_id, the message history on the messenger side is preserved together with access to all previously purchased products — provided the operator correctly prepares the import file with a populated social_id. Indirectly the client benefits — after migration the bots resume communication on the destination account without requiring a new subscription.

The Client's Card of each transferred subscriber is recreated on the destination account using the social_id key — this is the subscriber's identifier on the messenger side by which the platform uniquely maps the user to their communication channel. The name, email and phone fields from the import file are written to the card; subscription and deal history from the source account is NOT carried over to the new account (this is a constraint of the operation — only the subscriber itself and its channel binding are transferred).

After reading this you will understand:

  • when a user base transfer is appropriate and what preparation steps must be performed before starting;

  • how to contact technical support and coordinate the source and destination account emails;

  • how to filter the subscriber base by a specific bot using the "By Communication Channel" filter in the Audience module;

  • how to export the filtered base via mass actions and prepare the import file with the required columns name, social_id, email, phone;

  • how to correctly connect the same bot on the destination account without creating a new bot in the messenger;

  • how to import the prepared file and subscribe the transferred users to the sales tunnel and LGT of the destination account.

Purpose

The key role of the operation is to ensure continuity of B2B operations and continuity of relationships with subscribers when the Leeloo.AI account is changed. USP: the only standard mechanism of the platform that allows the accumulated base and connected messenger channels to be preserved without losing access to subscribers on the messenger side.

At the Manage stage the transfer is a data-and-infrastructure management operation: the operator controls which account serves the base, moves the communication channel, and maintains the integrity of the Client's Card through the social_id key. Job-to-be-done — migrate the subscriber base and connected bot between Leeloo.AI accounts without losing access to subscribers and without requiring a new subscription.

At the Engage stage the transfer plays a supporting role — after the import completes, the bot on the destination account resumes communication with subscribers through the connected tunnel and LGT. Job-to-be-done — restore active operation of bots and sales tunnels on the new account immediately after the import, without losing re-engagement opportunities.

2. Preparing for the transfer

Before any technical steps the operator must coordinate the transfer with Leeloo.AI technical support. Support will verify access to both accounts and record the operation in the platform's internal logs.

Write to technical support and specify from which account to which account the user transfer is planned. Provide the emails of both accounts — the source (where the base is transferred from) and the destination (where it is transferred to). Email coordination is mandatory — without it the transfer is not started.

Both accounts must be active and belong to your company. If the destination account has not yet been created — create it and confirm access before contacting support.

3. Exporting the base from the source account

Switch to the source Leeloo.AI account and open the Audience module — the base of all subscribers of the account is stored here. The next actions are performed sequentially through the standard Audience filter panel and mass actions.

  1. Go to the "Audience" section.

Audience section
  1. Open the "+ More" button on the filter panel — it opens the full list of available Audience filters.

  1. Apply the "By Communication Channel" filter and select exactly one bot — the one whose users need to be transferred. Click the "Apply" button in the top right corner of the panel.

By Communication Channel filter
  1. Launch the export of the filtered base via "Mass Actions" → "Export". In the export parameters dialog, select the type "By Communication Channel" — the system will produce a file containing all subscribers of the selected bot.

Set the export time to the current (nearest available), otherwise the task will be scheduled for nighttime by default — 02:00. Without an explicit time the file will not appear during the working day.

4. Preparing the import file

The file downloaded from the source account must be brought into the format accepted by the destination account's importer. The format is strictly fixed — deviations cause import to fail or produce errors in the Client's Card mapping.

  1. Open the downloaded file and bring it to the form shown in the example template. The file must contain exactly four columns with the headers: name, social_id, email, phone.

File structure: one row = one subscriber. Column name — subscriber name displayed in the Client's Card; social_id — identifier on the messenger side (Telegram chat_id, Facebook PSID, etc.); email and phone — contact details if they exist in the base.

If the base has no emails or phone numbers — leave the corresponding cells completely empty. Do not insert dashes (—), zeros, N/A or any other placeholders — this will break the import. social_id is required for every row — it is the key by which the platform uniquely matches the subscriber to the communication channel.

5. Connecting the bot on the destination account

Before importing the base, the same bot that exists on the source account must be connected to the destination account — this is a mandatory condition for the transferred subscribers to be linked to their communication channel. Open the "Communication Channels" section on the destination account and connect the bot following the instruction for the corresponding channel type (Telegram, Facebook Messenger, Instagram, WhatsApp, Viber, SMS, Email).

Do not create a new bot on the messenger side. Use the connection details of the already existing bot (the same token / API key / number). Creating a new bot will change the social_id of subscribers and make matching with the exported base impossible.

6. Importing the base on the destination account

After the bot is connected and the file is prepared, perform the import on the destination account.

  1. On the destination account open the "Audience" module and launch "Mass Actions" → "Import".

  2. In the import dialog upload the prepared file.

  3. Select the bot — previously transferred and connected on the destination account.

  4. Select the sales tunnel and LGT into which the imported users will be subscribed.

  5. Launch the import and wait for the task to complete.

After the import completes, the subscriber base will appear in the "Audience" module of the destination account. The bot will resume communication via the selected tunnel — this is the return point to the Engage stage.

Related instructions

Instruction

Purpose

Instruction

Purpose

Export

Detailed description of the "Export" mass action in the Audience module: export types, file formats, scheduling and limitations.

Import

Detailed description of the "Import" mass action: file structure, column validation, choosing bot/tunnel/LGT on subscription.

Подключение чат-ботов к платформе Leeloo.AI

Connecting bots in communication channels — step-by-step instructions for Telegram, Facebook Messenger, Instagram, WhatsApp, Viber, SMS and Email.

Default tunnel (Туннель по умолчанию)

Sales Tunnels — configuring the subscriber path that will be applied to imported users on the destination account.

Key terms

Term

Explanation

Term

Explanation

User base transfer

Migration of subscribers and the connected bot from one Leeloo.AI account to another through the chain "disconnect bot + export base + connect bot + import base". Also: Перенос базы пользователей / Перенесення бази користувачів.

social_id

Unique identifier of the subscriber on the messenger side (Telegram chat_id, Facebook PSID, etc.). The key by which the platform maps the user to a communication channel during import.

name

Subscriber name — required column in the import file, displayed in the Client's Card on the destination account.

email

Subscriber email — optional column in the import file. If the base has no email, the cell stays empty.

phone

Subscriber phone — optional column in the import file. If the phone is missing, the cell stays empty (no dashes or placeholders).

Bot

Messenger bot connected to a communication channel (Telegram, Facebook, Instagram, WhatsApp, Viber). During the transfer, the same bot is disconnected on the source account and connected on the destination — without creating a new bot on the messenger side.

Platform account

A legal and operational unit in Leeloo.AI — a separate workspace with its own subscribers, bots, tunnels and LGT. The transfer is performed between two such accounts belonging to the same company.

Technical support

Leeloo.AI service that coordinates the emails of the source and destination accounts and records the transfer operation in the platform's internal logs.

Audience

Platform module that stores the base of all subscribers of the account; offers filters and mass actions (export, import, segmentation).

Communication Channel

Connected messenger or email provider (Telegram, Facebook, Instagram, WhatsApp, Viber, SMS, Email). Foundation of the platform — no channel means no subscriber.

Mass Actions

Operations performed on the filtered selection of subscribers in Audience: Export, Import, Subscribe/Unsubscribe to a tunnel, Move between tunnels, Delete.

LGT

Lead Generation Tool — subscriber capture tool (Mini Landing Page, QR Code, Widget, Pop-up, Form, FB Ad, Subscribe Button, Smart Response). On import the LGT through which the subscriber "entered" the tunnel is specified.

Sales Tunnel

Scenario of automated communication with the subscriber. On import the tunnel into which the imported users will be subscribed is specified.

Client's Card

Central data spine of the platform — subscriber card where all data about the client converges. On import a new card is created by social_id with the fields name/email/phone.

Manage

Customer lifecycle stage (PRD §2.3) — management of the accumulated subscriber base and communication infrastructure. User base transfer is an operation of this stage.