OnlyTG Recorder to TG-Staff: Complete Workflow Migration Guide for Asset Library & Agent Collaboration

If your team has been using OnlyTG Recorder to manage Telegram Bot conversation assets and agent records, you may have encountered some bottlenecks: assets scattered across local files or chat logs, lack of real-time collaboration among agents, and inability to unify lead tracking. TG-Staff is not a simple replacement for OnlyTG Recorder, but a SaaS platform that integrates asset management, agent collaboration, automated workflows, and lead attribution. This article provides actionable migration steps based on real-world scenarios, helping you transition your workflow from OnlyTG Recorder to TG-Staff, upgrading your team from a “recording tool” to an “operations hub.”

Why Migrate from OnlyTG Recorder to TG-Staff?

OnlyTG Recorder excels in single-user recording of bot conversations, making it suitable for individuals or small teams for review and analysis. However, when your team expands, customer service demands increase, and multi-user collaboration is needed, its limitations become apparent:

Capability	OnlyTG Recorder	TG-Staff
Asset Management	Local files/manual copy	Cloud asset library with templates, tags, categories
Agent Collaboration	No built-in collaboration, requires external communication	Independent agent accounts, conversation transfer, note collaboration
Multi-Project Management	Each bot needs independent configuration	Manage multiple bot projects from a single console
Lead Attribution	None	Split links (magic links) capture IP, browser, URL parameters
Automation	None	Visual command flow editor, zero-code bot interaction
Translation & Risk Control	None	Automatic translation, content risk control (Pro version)

The core value of migration lies in centralizing assets scattered across local files, chat records, and Excel sheets into the TG-Staff console, enabling agents to handle all conversations from a single web interface, while improving conversion efficiency through split links and automated workflows.

Step 1: Export Assets and Configurations from OnlyTG Recorder

Before starting the migration, conduct a complete asset inventory. OnlyTG Recorder data typically exists as local files or chat records, requiring manual extraction of the following three core asset types.

Three Core Assets to Export

1. Bot conversation templates and flows: Capture or copy commonly used greetings, menu structures, and multi-step Q&A (e.g., FAQs, order inquiry processes) from OnlyTG Recorder. Organize by scenario, such as “Pre-sales Consultation,” “Post-sales Support,” and “FAQs.”

2. User profiles and historical conversation summaries: Although TG-Staff does not support direct import of chat records, you can export frequent user question types, common needs, and preference tags (e.g., “VIP User,” “Complaint User”) from OnlyTG Recorder. These can be used to rebuild the user tagging system in TG-Staff later.

3. Traffic sources and conversion data: If you tracked referral links from different channels (e.g., ad links, social media links) via OnlyTG Recorder, compile URLs, source channels, and attribution tags (e.g., utm_source, utm_campaign). This data will be used to recreate split links in TG-Staff.

Clean and Organize Exported Assets

After export, do not directly import into TG-Staff (as direct import is not supported). Instead, categorize by project and scenario, deduplicate, and standardize formats. For example:

• Convert frequently used reply templates into Markdown text for easy creation of message templates in TG-Staff.
• Organize conversation flow screenshots into flowcharts or textual descriptions for reconstruction in the visual command flow editor.
• Compile user tags into CSV or tables for manual addition in TG-Staff later.

Use a shared document (e.g., Notion or Feishu) to manage this migration checklist, ensuring all team members stay synchronized.

Step 2: Rebuild Asset Library and Bot Flows in TG-Staff

One of TG-Staff’s core advantages is its visual command flow editor, enabling zero-code construction of bot greetings, menus, and multi-step interactions. Unlike OnlyTG Recorder’s static assets, TG-Staff’s assets are dynamic and interconnected.

Visual Command Flow Editor Usage Guide

In the TG-Staff console, navigate to the “Command Flow” module and click “New Flow”:

1. Create a welcome node: Drag a “Send Message” node and input welcome text (supports Markdown, images, buttons). For example: “Welcome to our customer service center! Please select the category you need help with:”
2. Add menu buttons: Below the welcome node, add a “Button” node and configure button text and navigation logic. For example: three buttons for “Pre-sales Consultation,” “Post-sales Support,” and “FAQs,” each navigating to the corresponding sub-flow.
3. Build multi-step Q&A: For the “FAQs” sub-flow, drag multiple “Send Message” and “Wait for User Input” nodes to form a Q&A chain. For example: User clicks “FAQs” → Bot sends “Please select your question type” → User selects “Refund Process” → Bot sends refund steps.
4. Save and bind to bot: After creating the flow, save it and bind it to the corresponding bot project. TG-Staff automatically deploys the flow to the Telegram bot.

Media Library and Common Reply Templates

In TG-Staff’s “Media Library,” you can create reusable message templates. These templates support text, images, Markdown, and can be linked with command flows. For example:

• Create a “Refund Process” template containing refund steps, required materials, and customer service contact information.
• Create a “Logistics Inquiry” template including tracking number format and query links.

When an agent replies to a user in the conversation panel, they can directly select a template from the media library and send it with one click, greatly improving response efficiency.

Step 3: Configure Agent Team and Collaboration Rules

OnlyTG Recorder’s agent collaboration is almost nonexistent—each agent records independently, unable to see colleagues’ replies or session status in real time. TG-Staff provides a complete agent collaboration system. You need to configure agent accounts and routing rules based on team size.

Add Agents and Assign Permissions

In the TG-Staff console under “Agent Management,” click “Add Agent”:

• The Standard plan supports 3 agents, and the Professional plan supports 5 or 20 (see the official website pricing page for details).
• Each agent has an independent login account and password. After logging into the Web console, they can serve Telegram users.
• In “Project Permissions,” you can restrict the scope of projects each agent can operate. For example, assign Agent A to only the “Pre-sales Consultation” project and Agent B to only the “After-sales Support” project to prevent unauthorized access.

Configure Session Routing and Referral Links

Session routing rules determine how new users entering the Bot are assigned to agents:

• Round Robin (default): Polls agents with permissions in order, suitable for teams with a balanced number of agents.
• Online First: Prioritizes agents currently online; falls back to round robin when all are offline. It is recommended for most teams to choose “Online First” for the fastest user response.

At the same time, you need to create referral links (magic links) to replace the old traffic links in OnlyTG Recorder. In TG-Staff, referral links are official domain short links (e.g., https://app.tg-staff.com/{code}). When a user clicks the link, their IP, browser information, and URL parameters are captured first, then they are redirected to the Bot. This allows you to see the traffic effect of each channel in the backend and, combined with session routing, automatically handle consultation peaks.

Step 4: Post-Migration Testing and Acceptance Checklist

After migration, do not rush to switch to the production environment. Verify each item according to the following checklist:

• Bot Conversation Flow Test: Open the Bot in Telegram and test whether the welcome message, menu buttons, and multi-step Q&A work as expected.
• Agent Login and Collaboration Test: Log into the TG-Staff console with two different agent accounts, simulate receiving user messages simultaneously, and test session transfer and note collaboration features.
• Session Routing Test: Have two agents online and offline respectively to test if the “Online First” rule takes effect. When all are offline, check if new sessions fall back to round robin.
• Referral Link Attribution Test: Click referral links from different channels (e.g., ad links, social media links) and check if the backend correctly captures IP, browser information, and URL parameters.
• Auto-Translation and Content Moderation Verification (Professional plan): Send multilingual messages to test translation accuracy; add test keywords to risk phrases and verify the secondary confirmation and blocking logic when agents send messages.

If all the above tests pass, you can update the old traffic links to TG-Staff referral links and notify the team to officially switch.

Frequently Asked Questions

Q: Can chat logs from OnlyTG Recorder be directly imported into TG-Staff? A: Currently, TG-Staff does not support directly importing chat logs from OnlyTG Recorder. It is recommended to export historical conversation summaries as references before migration and rebuild user profiles and tag systems in TG-Staff.

Q: Does the old Bot need to be recreated after migration? A: No. You only need to connect the Bot Token to the TG-Staff console; the Bot itself will not change. However, the Bot’s conversation logic will be taken over by TG-Staff’s command flows. It is recommended to verify on a test Bot before migration.

Q: Can migration be completed within the free trial period? A: Yes. TG-Staff offers a 3-day free trial, which is sufficient to complete migration testing for a single project. It is recommended to plan the migration steps in advance, verify core functions during the trial, and then decide whether to subscribe.

Q: After the team migrates from OnlyTG Recorder, do agents need retraining? A: Basic training is needed. The TG-Staff Web console interface differs from OnlyTG Recorder, but the operation logic is more intuitive. It is recommended to arrange 1–2 hours of training, focusing on the conversation panel, tags, session transfer, and command flow usage.

Q: After migrating referral links, will the old links still work? A: Old links cannot automatically redirect. It is recommended to create new referral links in TG-Staff and update links on ads/social media channels. You can keep old links for a while, using 301 redirects or notifying users to update.

---

The migration from OnlyTG Recorder to TG-Staff is essentially an upgrade from a “recording tool” to an “operations platform.” Although it requires some initial configuration time, once completed, your team will benefit from more efficient media management, smoother agent collaboration, more accurate referral attribution, and more powerful automation capabilities. If you are considering migration, feel free to register for TG-Staff free trial and complete core function verification within 3 days. If you encounter any issues during migration, refer to the official documentation or contact customer service Bot @tgstaff_robot for support.