Complete Migration Checklist: From OnlyTG Echo to TG-Staff — Bots, Scripts, Bulk Messaging, Agents, and Routing Links

If you are using OnlyTG Echo to manage Telegram Bot customer service but have encountered agent collaboration bottlenecks, lack of user attribution tracking, or insufficient compliance controls as your team grows, migrating to TG-Staff might be worth considering. This checklist breaks down the complete migration process from OnlyTG Echo to TG-Staff step by step, covering Bot integration, script reconstruction, bulk messaging data migration, agent configuration, and routing link setup, helping your team transition smoothly with minimal data loss or service interruption.

Why Migrate from OnlyTG Echo to TG-Staff? — Core Capability Comparison

Before starting the migration, clarify the actual benefits. OnlyTG Echo performs well in single-Bot auto-reply scenarios, but when business requires multi-agent collaboration, multi-channel attribution, or compliance control, its limitations become apparent.

Feature Dimension	OnlyTG Echo	TG-Staff
Agent Management	Typically single account operation, no independent agent portal	Independent agent accounts login to web portal, supports 3/5/20 agent quotas
Conversation Routing	No advanced routing rules	Supports two routing strategies: round-robin and online-first
Routing Links (Attribution)	No built-in short links to capture visitor info	Provides official domain short links that can capture IP, browser, UTM parameters
Content Moderation	None	Pro version supports pre-message risk word detection, including crypto wallet address monitoring
Auto Translation	Basic version has limitations	Standard version includes AI translation; Pro version supports Google, DeepL professional translation
Bulk Messaging	May rely on third-party tools	Built-in bulk messaging with user segmentation
Multi-Project Management	Limited	Supports multiple Bot projects per plan

Core benefits of migration: Upgrade from single-point operation to team collaboration → From reactive response to proactive attribution → From no control to compliance management. If you face the following scenarios, migration is valuable:

• Your team has 2+ people handling Bot inquiries simultaneously, requiring session transfer and collaboration features.
• You use UTM parameters in ad campaigns to track conversions and need routing link attribution.
• Your business involves cryptocurrencies or sensitive fields, requiring monitoring of wallet addresses in agent messages.

Pre-Migration Preparation: Account, Data, and Team Alignment

The key to successful migration lies in preparation. Do not skip this step.

Backup Critical Data from OnlyTG Echo

Before rebuilding configurations in TG-Staff, export the following data from OnlyTG Echo:

• Bot Token: Obtain from BotFather or copy from OnlyTG Echo settings. Note: The token is top secret; do not leak it.
• Script Templates: Including welcome messages, menu buttons, multi-turn dialogue text and conditional logic. Screenshot or export as plain text.
• Bulk Messaging User ID List: If OnlyTG Echo supports export, export all user IDs or export by segment. Important: TG bulk messaging requires users to have sent a message to the Bot to be reachable; ensure the list is valid.
• Agent List and Permissions: Record each agent’s username, email, and the Bot projects they are responsible for.
• User Profile Tags: If tags have been set in OnlyTG Echo, export tag names and associated user IDs.

Register TG-Staff and Confirm Plan

1. Visit https://app.tg-staff.com/ to register an account, automatically receiving a 3-day free trial.
2. Choose a plan based on team size:
   • Standard (~$8.99/month): Suitable for 2–3 person teams, includes routing links, conversation routing, 3 agent slots.
   • Pro (~$16.99/month): Suitable for teams of 5+ people, additionally provides content moderation (including wallet address monitoring), unlimited translation, user profiles, and other advanced features.
3. If the team needs to manage multiple Bots simultaneously, confirm the number of projects supported by the plan. Specific pricing is subject to the official website plan page.

Step 1: Bot Migration — Connect to the Telegram Bot API

This is the most critical step that directly determines the success of the migration.

Add the Bot to the TG-Staff Console

1. Log in to the TG-Staff Console → Click “New Project”.
2. Enter your Bot Token (obtained from BotFather, format like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11).
3. The system will automatically verify the token’s validity and sync the bot’s name and description. You can also edit the bot’s avatar, name, and description directly in the console without going back to BotFather.
4. If your OnlyTG Echo manages multiple bots, repeat the above steps for each bot to create a project.

Verify Bot Functionality

After adding, send a message to the bot using a test account to confirm:

• The message appears in the TG-Staff real-time chat interface.
• If a welcome message is configured (next step), check if it triggers correctly.
• After an agent replies, the user receives it properly.

If OnlyTG Echo has custom keyboards or inline buttons, you need to rebuild them in TG-Staff (see next step).

Step 2: Rebuild Scripts and Command Flows

The script logic (welcome messages, menus, multi-turn conversations) in OnlyTG Echo cannot be automatically migrated to TG-Staff. You need to use TG-Staff’s visual command flow editor to rebuild them.

1. Go to Project in the console → Click “Command Flow”.
2. Drag nodes onto the canvas, configure welcome text, button text, and navigation logic.
3. If OnlyTG Echo has multi-step interactions (e.g., collect user info → send confirmation → transfer to human), create multiple nodes and connect them with the same logic.
4. Save and publish the flow, then trigger the bot with a test account to verify each step executes as expected.

Tip: TG-Staff’s flow editor is no-code, so even operators without programming experience can use it. Start with simple scenarios (e.g., welcome + menu) and gradually add complexity.

Step 3: Migrate Broadcast Data and Segment Users

Broadcasts are an important tool for operations. Migration steps:

1. Organize the previously backed-up user ID list into plain text format (one user ID per line).
2. In TG-Staff console → “Broadcasts”, click “Create Broadcast”.
3. Select the target user segment (e.g., “All Users” or custom segments). If OnlyTG Echo has tags, manually create corresponding segments in TG-Staff and import user IDs.
4. Compose the message content, supporting text, images, buttons, etc.
5. It is recommended to test with 50–100 users first to confirm delivery success rate and message format, then execute full broadcast.

Note: Telegram has rate limits on bot broadcasts (about 30 messages/second), but TG-Staff has built-in rate limiting to avoid triggering restrictions. If you have a large user base (>100k), send in batches.

Step 4: Configure Agents and Session Routing

This is a core advantage of TG-Staff over OnlyTG Echo: multi-agent customer support.

Create Agent Accounts and Permissions

1. In console → “Agent Management”, click “Add Agent”.
2. Enter the agent’s email or username; the system sends an invitation link.
3. Assign project permissions to each agent: they can view sessions of only one bot or all bots.
4. Agents log in via an independent web portal (https://app.tg-staff.com/), no need to share account passwords.

Configure Routing Rules and Test

1. Go to Project Settings → “Session Routing”.
2. Select a routing rule:
   • Round Robin: Distributes sequentially among available agents, suitable for balanced daily workloads.
   • Online First: Prioritizes agents currently online, ideal for quick responses during peak hours.
3. Set agent scope: choose “All Agents” or “Specific Agents” (e.g., only senior agents handle complex issues).
4. Send messages with multiple test accounts and observe if sessions are assigned to different agents according to the rule. If no agent is online, the system queues or falls back to round robin.

Note: Agents from OnlyTG Echo cannot be directly migrated to TG-Staff; each agent needs to re-register. Notify your agent team to prepare emails or usernames before migration.

Step 5: Migrate Diversion Links and Rebuild Ad Attribution

If you used short link tracking in OnlyTG Echo, TG-Staff’s Diversion Links offer more powerful attribution capabilities.

1. In console → “Diversion Links”, create a new link.
2. Enter the original URL (usually the bot’s t.me link); the system generates a short link in https://app.tg-staff.com/{code} format.
3. Bind tracking parameters: add custom parameters like ?utm_source=facebook&campaign_id=123 after the link; the system automatically captures visitor IP, browser info, and URL parameters.
4. Replace the original links in ads, social media, and emails with the generated short links.

Test flow: Click the referral link → automatically redirect to the Bot → send a message → check if the source information is displayed in the agent’s user profile. If everything is normal, the referral attribution chain has been rebuilt.

Post-migration Checklist and Common Troubleshooting

After completing the above steps, use this checklist to confirm all components are working:

• Bot responds normally: After the user sends a message, it is displayed in real-time on the agent side.
• Script flow is correct: Welcome message, menus, and multi-turn conversations execute as expected.
• Agent login works: Each agent can log into the web portal with a unique account.
• Chat routing is effective: Messages are assigned to the correct agent according to rules, with no missed or incorrect assignments.
• Bulk messaging test passes: Small-scale bulk messaging succeeds, with no failures or duplicates.
• Referral link redirects correctly: Clicking the short link leads to the Bot, and the user profile shows source information.
• Auto-translation (if applicable) works: After the agent sends a message, the user sees the translated content.
• Content moderation (Pro version) works: When the agent sends a message containing risky words, a second confirmation is triggered or the message is blocked.

Common Troubleshooting:

Issue	Possible Cause	Solution
Bot unresponsive	Invalid token or Bot suspended	Retrieve a new token from BotFather, check if the token in TG-Staff is correct
Bulk messaging fails	Invalid user ID or Telegram rate limit	Verify the user ID format is correct, send in batches (1000 messages per batch)
Routing ineffective	Incorrect routing rules or agents offline	Check if routing rules are set to “Online First”, confirm agents are logged in
Referral link returns 404	Link expired or project deleted	Regenerate the referral link and replace the old one

Frequently Asked Questions

Q: Can data from OnlyTG Echo (e.g., user profiles, chat history) be automatically imported into TG-Staff?

A: TG-Staff currently does not support automatic data import from OnlyTG Echo. It is recommended to manually export the user ID list, script templates, and agent list before migration, and then reconfigure them via the console. Chat history cannot be migrated, but new conversations after the Bot is connected will be displayed normally.

Q: Will my Telegram Bot experience downtime during migration?

A: There will be a brief switchover window. It is recommended to operate during off-peak hours: first pause the Bot response in OnlyTG Echo, then add the same Bot Token in TG-Staff and activate it. The entire process usually takes 5–10 minutes. It is recommended to notify users of the maintenance in advance.

Q: Does TG-Staff support managing multiple Bots simultaneously? How is it different from OnlyTG Echo?

A: Yes. TG-Staff supports different numbers of Bot projects depending on the plan (see the official website for the exact numbers for Standard and Pro plans). Compared to OnlyTG Echo, TG-Staff offers more flexible multi-agent collaboration, routing rules (Round Robin / Online First), and referral link attribution, making it more suitable for teams operating multiple Bots.

Q: Will the existing bulk messaging list and sending frequency be affected after migration?

A: The bulk messaging list needs to be re-imported into TG-Staff. TG-Staff’s bulk messaging feature supports sending by user segments and has built-in rate limits (following Telegram’s official limits). After migration, it is recommended to test on a small scale first (e.g., 50–100 messages) to confirm the delivery success rate before performing full-scale bulk messaging.

Q: I am a paid user of OnlyTG Echo. Will I get the same or better features after migrating to TG-Staff?

A: It depends on the plan you choose. The TG-Staff Standard plan (approximately 8.99/month) already includes core features such as real-time two-way chat, chat routing, and referral links; the Pro plan (approximately16.99/month) additionally provides content moderation (including encrypted wallet address monitoring), unlimited translation, user profiles, and other advanced features. It is recommended to use the 3-day free trial to compare and test, and subscribe only after confirming it meets your needs.

---

Start migration now: Register for a 3-day free trial of TG-Staff → https://app.tg-staff.com/

Get detailed operation guide: Refer to TG-Staff documentation → https://docs.tg-staff.com/

Encounter issues during migration? Contact customer service Bot → @tgstaff_robot