2026 Migration Checklist: Moving from onlyTG to TG-Staff: Bots, Agents, Scripts, and Routing

If your team is using onlyTG to manage Telegram customer support but finds its capabilities in agent collaboration, session routing, or content control gradually insufficient, migrating to TG-Staff is a worthwhile upgrade. TG-Staff not only offers more comprehensive agent management, a visual flow editor, and session routing capabilities but also includes built-in content moderation and encrypted wallet address monitoring for Web3 teams.

This article provides an actionable migration checklist to help you smoothly transition from onlyTG to TG-Staff, avoiding data loss, agent downtime, or service interruptions for users.

Pre-Migration Preparation: Confirm Your onlyTG Subscription Status and Back Up Data

Before diving into TG-Staff, spend 15 minutes on the following preparation steps—this is the most overlooked yet critical part of the entire migration process.

Export Bot Token and API Credentials from onlyTG

Bot Token is the unique credential connecting your bot to the customer service platform. You’ll need it regardless of which platform you migrate to.

1. Log in to BotFather, find your bot, and use the /mybots command to enter bot settings.
2. Click API Token or copy the token string directly. If onlyTG’s console has displayed the token, take a screenshot as backup.
3. If you configured third-party APIs (e.g., Google Translate, DeepL keys) in onlyTG, export those as well.

Note: The Bot Token is equivalent to the bot’s admin password; do not share it publicly. After migration, you can re-enter this token in TG-Staff to complete authorization.

Backup Script Templates and User Segmentation Rules

Welcome messages, menu buttons, multi-step conversation flows, and user tag groups in onlyTG typically do not sync automatically to the new platform. You need to manually export:

• Script Templates: Copy all bot auto-reply text content, including conditional branching logic. Save as screenshots or in a Markdown file.
• User Segmentation Rules: Record existing tags and grouping conditions (e.g., “Active Users,” “VIP Customers”). TG-Staff’s Pro version supports user profiles and segmentation; you can recreate these rules later in the console.

Step 1: Create a Project and Authorize the Bot in TG-Staff

After completing the backup, log in to the TG-Staff Console, register, and start a 3-day free trial.

Quick Authorization Using the Bot Token

1. Click “Projects” in the left menu, then click “Create Project.”
2. Enter a project name (recommend matching the bot name in onlyTG for team recognition).
3. Paste the token you obtained from BotFather into the “Bot Token” input field.
4. Click “Authorize.” TG-Staff will automatically pull the bot’s avatar, name, and description.

The entire process takes less than a minute. No additional steps in BotFather are needed—TG-Staff directly takes over the bot’s webhook address.

Verify Bot Online Status and Message Send/Receive

After authorization, the bot status will show as “Online” in the project details. It’s recommended to immediately perform a message send/receive test:

1. Send a message to your bot on Telegram (e.g., “Hello”).
2. In TG-Staff’s “Conversations” panel, a new conversation should appear immediately.
3. Log in to the web portal as an agent, reply to this message, and check if the user end receives it correctly.

If the message path works, TG-Staff has successfully taken over the bot. At this point, onlyTG’s bot is still running, but it’s recommended to disconnect onlyTG’s bot service as soon as possible to avoid dual-platform responses.

Step 2: Rebuild Customer Service Agent Team and Permission Configuration

onlyTG’s agent system is typically based on Telegram groups or simple account sharing, while TG-Staff provides independent agent accounts, project-level permissions, and session assignment records.

Invite Agents and Assign Independent Accounts

1. In the console under “Agent Management”, click “Invite Agent”.
2. Enter the agent’s email address (each agent needs a unique email to log into the web portal).
3. Set the agent’s “Project Permissions”: configure which projects the agent can see and whether they have editing permissions.
4. After receiving the invitation email, the agent can set a password and log in.

Compared to onlyTG, TG-Staff’s advantages are:

• Each agent has their own login account, making operations traceable.
• Supports project-level permission isolation, suitable for multi-bot teams.
• The professional version also offers private notes, preventing interference between agents.

Align with onlyTG Agent Roles

If your onlyTG team has roles like “Admin”, “Customer Service Lead”, or “Regular Agent”, you can mirror them in TG-Staff through permission configuration. For example, a lead can view all conversations, while regular agents can only see their assigned conversations.

Step 3: Migrate Scripts and Routing Rules

This is the most labor-intensive part of the migration process, but TG-Staff’s visual command flow editor can significantly reduce the rebuilding effort.

Visual Command Flow: Rebuild Bot Interactions with No Code

TG-Staff’s command flow editor uses a drag-and-drop node design, allowing you to build the bot’s automated reply logic without writing any code.

1. In the console under “Command Flow”, click “New Flow”.
2. Drag the “Welcome Message” node from the left panel onto the canvas, and enter your welcome text from onlyTG.
3. Drag the “Menu” node, configure button text and navigation logic (e.g., “View Prices” → “Send Price Card”).
4. Drag the “Conditional” node to route users based on keywords to different replies.

Compared to onlyTG’s text-based configuration, TG-Staff’s drag-and-drop interface is more intuitive, especially for multi-step interactions (e.g., surveys, ticket submission). You can copy scripts from onlyTG into the corresponding nodes.

Configure Session Routing and Diversion Links

Session routing determines how user messages are assigned to agents. TG-Staff offers two assignment modes:

• Round Robin (default): Assigns new sessions sequentially to authorized agents, suitable for teams with stable agent numbers.
• Online First: Prioritizes currently online agents; if all are offline, falls back to round robin, suitable for teams with variable schedules.

In “Project Settings” → “Session Routing”, you can select the mode and specify which agents participate.

Additionally, TG-Staff’s Diversion Link is a unique traffic acquisition tool. You can create a short link (e.g., https://app.tg-staff.com/abc123) that, when clicked, captures the user’s IP, browser info, and URL parameters before redirecting to your bot. This is useful for ad attribution and multi-channel tracking—onlyTG typically lacks built-in features like this.

Step 4: Migrate Content Moderation and Compliance Configurations (Pro Plan)

If your team deals with Web3, cryptocurrency, or financial services, content moderation is a critical part of the migration. The TG-Staff Pro plan includes a built-in content moderation module that precisely monitors messages sent by agents, preventing accidental or unauthorized transmission of sensitive information.

Configure Risk Phrases and Wallet Address Monitoring

1. In the console, go to “Content Moderation” → “Risk Phrases” and click “Create Phrase.”
2. Enter a phrase name (e.g., “Wallet Address Blacklist”).
3. Add risk keywords: You can enter full TRC20/ERC20/BTC addresses or address fragments (e.g., T9yD14). TG-Staff supports prefix matching and exact matching.
4. Associate the risk phrase with a specific project and enable “Agent Outbound Message Monitoring.”
5. Set the trigger action: Choose either “Popup Confirmation” or “Block Sending.”

For example, if your exchange bot agents frequently need to manually respond to user withdrawal requests, configuring wallet address monitoring can prevent agents from mistakenly sending incorrect receiving addresses or deliberately requesting extra fees from users. This feature typically requires custom development or third-party plugins in onlyTG.

Audit and Alerts: View Trigger Logs

Once an agent triggers a moderation rule, you can view detailed logs under “Content Moderation” → “Trigger Logs,” including:

• Triggering agent
• Associated session
• Trigger time
• Risk word matched

These logs can be used for compliance audits, employee training, or dispute resolution. After migration, it is recommended to create a test risk word (e.g., test-risk) and have an agent send a message containing it to verify that moderation is working correctly.

Step 5: Test Full Chain and Switch to Production Traffic

Before the official switch, perform a complete end-to-end test. Below is a checklist you can print or copy into your project management tool to verify each item.

After testing is complete, perform the following steps to switch officially:

1. Stop the Bot service in onlyTG (or revoke the Bot Token).
2. In TG-Staff, confirm that all agents are logged in and online.
3. Notify the customer service team: the new platform is live, stop using the old platform.
4. Update your ad creatives and social media links to point to the new diversion link from TG-Staff.

FAQ

Q: After migrating to TG-Staff, can the onlyTG Bot still be used?

A: Yes. TG-Staff uses the same Bot Token to take over the Bot; the onlyTG Bot will not become invalid immediately. It is recommended to stop the onlyTG Bot service only after completing all tests in TG-Staff to avoid confusion caused by both platforms responding simultaneously.

Q: Can user chat history from onlyTG be imported into TG-Staff?

A: TG-Staff currently does not support directly importing historical chat records from onlyTG. After migration, new conversations will be stored in TG-Staff. It is recommended to export important conversation records from onlyTG as a backup for future reference.

Q: Will the migration affect normal use by Telegram users?

A: If done correctly, users will hardly notice. You only need to authorize the Bot Token in TG-Staff and configure agents. When users send messages, they will automatically enter the TG-Staff conversation queue. It is recommended to switch during off-peak hours and notify the customer service team in advance.

Q: How is the diversion link feature in TG-Staff different from onlyTG?

A: TG-Staff’s diversion link is a short link under an official domain that captures visitor IP, browser information, and URL parameters, making it suitable for ad attribution. onlyTG may not have similar built-in attribution capabilities. After migration, it is recommended to regenerate diversion links and update ad creatives.

Q: Does TG-Staff support cryptocurrency payments?

A: Yes. In addition to Stripe credit card payments, TG-Staff also accepts USDT (TRC20) on-chain payments, suitable for teams that prefer cryptocurrency. You can select the USDT payment method in the console under “My Subscription”.

---

Migrating to TG-Staff is not a complex process. As long as you follow the checklist above step by step, most teams can complete the switch within 1–2 hours. If you encounter any issues during migration, you can refer to the official migration documentation or contact the support Bot for real-time assistance.

Sign up for TG-Staff now and start your 3-day free trial: https://app.tg-staff.com/