Migrating from OnlyTG or Teleform to TG-Staff: A Unified Guide for Bots, Broadcasting, Agents, and Diversion Links

If your team is using OnlyTG or Teleform to operate Telegram Bot customer service and broadcasting but is gradually feeling functional bottlenecks—low agent collaboration efficiency, lack of internal control mechanisms, and limited diversion capabilities—then migrating to a more complete platform is the logical next step. TG-Staff integrates Bot management, agent conversations, diversion links, content moderation, and bulk messaging into a single console, making it ideal for B2B SaaS teams that need remote customer service, multilingual support, and compliance controls.

This article is a unified guide for migrating from OnlyTG or Teleform, covering the complete process from Bot binding to agent configuration, from broadcasting migration to internal control settings. Whether you are migrating from OnlyTG or Teleform, the core steps are consistent, and all operations can be verified through TG-Staff’s free trial.

Why Migrate from OnlyTG or Teleform to TG-Staff

OnlyTG and Teleform helped many teams quickly set up Telegram Bot customer service in the early days, but as business scales, several common pain points begin to emerge:

• Weak agent collaboration: OnlyTG’s agent features are basic, not supporting multiple agents handling different conversations simultaneously, nor enabling conversation transfers or note collaboration. Teleform leans toward form collection, with limited support for customer service scenarios.
• Insufficient diversion capabilities: Both lack flexible conversation diversion rules (e.g., round-robin assignment, online-first) and cannot provide short links for ad attribution (diversion links).
• Lack of internal controls: For Web3, cryptocurrency, exchange, and similar teams, agents mistakenly sending payment addresses or violating content is a high-risk behavior. OnlyTG and Teleform have no content moderation features.
• Fragmented multi-project management: Multiple Bots require switching between different platforms or projects, lacking unified data statistics and user profiles.

TG-Staff integrates these features into one console: real-time two-way chat, agent account management, conversation diversion, diversion links, visual command flows, bulk messaging, automatic translation, content moderation (including crypto wallet address monitoring), and Stripe/USDT subscription payments. Migrating from OnlyTG or Teleform essentially unifies scattered tools into one platform, reducing switching costs while gaining internal control and data capabilities.

Pre-Migration Preparation: Checklist and Key Checkpoints

Migration is not a one-time operation; you need to prepare materials in advance and confirm permissions. The following checklist should be reviewed item by item before starting:

Item	Description	Notes
Bot Token	Obtain or reset from BotFather	Ensure the token is not expired; if still in use on the old platform, bind it on the new platform for testing before revoking
User Data	User lists, conversation history, group information from OnlyTG/Teleform	Export as CSV or JSON; note ID format compatibility
Broadcast Templates	Common broadcast messages, welcome messages, command configurations	Suggest organizing into text files to rebuild in TG-Staff’s visual flow later
Agent List	Current agents’ emails, roles, permission scopes	Agent accounts need to be recreated in TG-Staff after migration
Diversion Links	Short links or redirect links from the old platform	After migration, replace with new links generated by TG-Staff
Internal Control Rules	Existing risk word lists, monitoring rules	Can be reconfigured in TG-Staff Pro version

Bot Token Acquisition and Permission Confirmation

1. Open Telegram and search for @BotFather.
2. Enter /mybots and select your Bot.
3. Click API Token and copy the token string. If the token is leaked or needs to be reset, click Revoke current token to generate a new one.
4. Ensure that in BotFather, your Bot has Inline Mode enabled (if needed) and Group Privacy set to Disabled (if the Bot needs to read group messages).

The token is the Bot’s “password”; do not share it publicly. After binding the token, TG-Staff will automatically configure messaging permissions without additional setup.

Existing Data Export and Cleanup

• OnlyTG Users: Export the user list (typically as CSV) from the OnlyTG console, including user ID, username, and first interaction time. Note that OnlyTG user IDs may contain extra prefixes that need to be cleaned before import.
• Teleform Data: Teleform response data can be exported as CSV or Excel in the form settings. It is recommended to keep only active users (those who interacted in the last 30 days) to reduce irrelevant data.
• Commands and Welcome Messages: Screenshot or copy the command configurations and welcome message texts from OnlyTG/Teleform. TG-Staff’s visual command flow supports drag-and-drop setup without coding.

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

After preparation, go to the TG-Staff console to start binding the Bot. The whole process takes about 5 minutes and requires no development knowledge.

Project Creation and Bot Token Binding

1. Visit https://app.tg-staff.com/ and register an account (free trial for 3 days).
2. After logging in, click New Project and enter a project name (e.g., “Main Customer Service Bot”).
3. In the Bot Token field, paste the token copied from BotFather.
4. Click Verify; TG-Staff will automatically check the token validity and connect the Bot.
5. Upon successful verification, the system will prompt “Bot connected successfully.” The Bot is now receiving messages.

If verification fails, check whether the token is fully copied or if it was reset in BotFather. If the original platform is still in use, it is recommended to test the binding in TG-Staff first, confirm message sending/receiving, and then revoke the old platform.

Edit Bot Profile (No BotFather Needed)

TG-Staff console directly supports modifying the Bot’s avatar, name, and description without going to BotFather. In the project settings, find the Bot Profile section:

• Avatar: Upload a PNG/JPG image, recommended 512×512 pixels.
• Name: Modify the Bot’s display name in Telegram.
• Description: Edit the Bot’s “About” text (shown when users click on the Bot’s profile).

After modification, click Save; TG-Staff will automatically call the Telegram API to update without additional steps.

Step 2: Migrate Broadcast Templates and Bulk Messaging

Broadcasting is a core scenario for customer service and operations. To migrate broadcast templates from OnlyTG or Teleform, follow these steps:

1. Organize Templates: Copy broadcast history, welcome messages, and notification templates from the original platform to a text file. If the original platform supports exporting broadcast records, export them as well.
2. Rebuild in TG-Staff: In the console, enter the Visual Command Flow, drag a “Send Message” node, and paste the template content. Supports text, inline keyboards, and Markdown formatting.
3. Test Broadcast: First send a test broadcast using a test Bot to ensure the format (e.g., Markdown links, button redirects) is correct.
4. Send by Segment: In the Bulk Messaging module, select a user segment (e.g., “Active users in the last 7 days” or “VIP users”), choose a template, and click Send.

Step 3: Configure Agent and Conversation Routing

For multi-agent teams, ensure each agent has an independent account and conversations are automatically assigned to the right person. TG-Staff’s agent and conversation routing configuration is as follows.

Create Agent Accounts and Assign Permissions

1. In the console, go to Agent Management → Add Agent.
2. Enter the agent’s login email and password (or choose registration via invitation link).
3. In Permission Settings, select the projects (e.g., only “Customer Service Main Bot”) and functional scope (e.g., view conversations only, transfer conversations, edit commands) the agent can operate.
4. Click Save; the agent will receive a login email (or log in directly via the link).

Agent quotas are limited by plan: Free trial supports 3 agents, Standard supports 3/5, Professional supports 20. See the official plan page for details.

Configure Routing Rules and Diversion Links

• Routing Rules: In project settings → Conversation Routing, select a strategy:
  • Round Robin (default): Cycles through authorized agents in order, suitable for teams with fixed agent numbers.
  • Online First: Prioritizes online agents; falls back to round robin if all are offline. Suitable for teams with variable agent schedules.
• Diversion Link: In the Diversion Link module, click Generate Link and select the target project. TG-Staff generates a short link in the format https://app.tg-staff.com/{code}. Replace old links in ads and social media with this link; when users click it, they first enter TG-Staff’s capture page (recording IP, browser info, URL parameters), then are redirected to the bot to start the conversation.

Step 4: Internal Control and Content Moderation (Professional)

For Web3, cryptocurrency, exchange, or any compliance-focused teams, content moderation is a crucial step after migration. TG-Staff Professional offers internal control management, allowing you to configure risk phrases and monitor agent messages.

1. In the console, go to Internal Control → Risk Phrases.
2. Click New Phrase, enter a name (e.g., “Payment Address Monitoring”).
3. Add keywords: e.g., TRC20 address prefix (starting with T), ERC20 address prefix (starting with 0x), or specific wallet address fragments.
4. In Associated Projects, select the bots to monitor.
5. Configure trigger actions: choose “Popup Confirmation” or “Block Sending”.
6. After saving, when an agent in the project sends a message containing a risk phrase, the system will pop up a warning or directly block the send. All trigger records can be viewed in Trigger Logs, including agent, conversation, trigger time, and risk phrase.

Internal control is suitable for scenarios where you need to prevent agents from mistakenly sending payment addresses, sensitive links, or prohibited content. Free trial and Standard plans do not include this feature; Professional users can enable it immediately.

Post-Migration Verification and Team Training

After completing all configurations, it is recommended to verify each item according to the following checklist to ensure no steps are missed:

Team Training Tips:

• Familiarize agents with the web chat interface: sending messages, viewing user profiles, using notes (Pro version).
• Explain session transfer operations: click “Transfer” in session details and select the target agent.
• Emphasize internal control rules: inform agents which content is monitored to avoid violations.

FAQ

Q: When migrating from OnlyTG to TG-Staff, do I need to reapply for a Bot Token?
A: No. Just confirm the token is not expired in BotFather, then enter it directly in the TG-Staff console. If the original platform is still in use, it’s recommended to bind and test on the new platform before revoking the old one.

Q: Can Teleform broadcast templates be directly imported into TG-Staff?
A: Currently, TG-Staff does not support one-click import of broadcast templates. We recommend copying the template content into the visual command flow to rebuild, or manually copying using a text file. For complex templates, contact @tgstaff_robot for assistance.

Q: Will users lose messages during migration?
A: No. The old platform’s bot continues running during migration. After binding the token in TG-Staff, new messages will start being received. We recommend switching during off-peak hours and keeping the old platform for 24 hours as a fallback.

Q: Can diversion links still be used after migration?
A: Short links from the original platform need to be regenerated. TG-Staff provides diversion links in the format https://app.tg-staff.com/{code}. Replace old links in ads and social media.

Q: Can I complete migration testing during the free trial?
A: Yes. After registration, you get a 3-day free trial, supporting 1 bot, up to 3 agents, and basic features—enough for single-bot migration testing. For multi-bot or Pro features, purchase the Standard or Pro plan.

---

Next Steps

• Register for TG-Staff free trial now: https://app.tg-staff.com/
• Read full documentation: https://docs.tg-staff.com/
• For migration issues, contact support bot: @tgstaff_robot