volbor

Looking for something?

↑↓navigateEnteropenEscclose

Choose language

Get started

Migrating from Another Service: Fresh Channels, No History Assumed

Switching platforms does not automatically migrate chat histories. volbor starts with a clean workspace and freshly connected channels. If your previous provider allows exporting conversation archives, keep that backup safely on your end. Until you open a specific historical thread inside your new Unified Inbox and see the messages with your own eyes, treat history as not migrated.

During the cutover, the most dangerous pitfall is running two auto-responders simultaneously on the same channel.

Get startedLearn more
  1. 01
    Two bots replying at once

    customers receive both the old and new greeting simultaneously, leaving them confused about where to reply.

  2. 02
    Assuming history is migrated after clicking export

    you downloaded a raw export file, but it's not in the Inbox. Your team begins greeting existing clients like strangers without realizing it.

  3. 03
    Disconnecting the channel before testing the new setup

    incoming customer messages vanish into thin air for several hours during cutover.

  4. 04
    Active bookings and pending payments stranded in the old tool

    your new workspace is blind to past appointments and orders until you recreate the corresponding automated workflows.

Common Pitfalls During Migration

  1. 01

    Two bots replying at once

    customers receive both the old and new greeting simultaneously, leaving them confused about where to reply.

  2. 02

    Assuming history is migrated after clicking export

    you downloaded a raw export file, but it's not in the Inbox. Your team begins greeting existing clients like strangers without realizing it.

  3. 03

    Disconnecting the channel before testing the new setup

    incoming customer messages vanish into thin air for several hours during cutover.

  4. 04

    Active bookings and pending payments stranded in the old tool

    your new workspace is blind to past appointments and orders until you recreate the corresponding automated workflows.

Step-by-Step Migration Playbook

  1. 01

    1. Set up your workspace and test on a staging channel

    Follow the quick start guide on an unannounced channel or a duplicate staging bot if the messenger supports it. Keep your production channel active until round-trip test messages are verified in the Unified Inbox.

  2. 02

    2. Disable auto-replies in your legacy service

    Retain your old software purely for read-only historical reference if supported. Automated replies must originate from a single source. If your old tool lacks a read-only mode, schedule a brief cutover window and instruct staff to handle inquiries manually during that hour.

  3. 03

    3. Reconnect the production channel and test immediately

    Send a test message from a separate personal account as a real customer. The reply from your new workspace must appear in that exact conversation. If it doesn't, revert immediately if possible and check our delivery troubleshooting guide. Never use paying customers as your guinea pigs.

  4. 04

    4. Decide how to handle past conversation records

    Export files serve as your historical archive. Do not promise your team that past chats will be searchable in the new Unified Inbox until those threads are actively imported and opened. Route all incoming conversations exclusively through volbor to prevent fragmented threads.

Payments, Bookings, and Custom Systems

Booking flows and payment checkout sequences must be configured anew in your workspace. Fulfill outstanding legacy orders within your previous platform or manually transfer them using a verified spreadsheet checklist. If events need to sync with your internal database or CRM, configure that through API & webhooks rather than assuming it happens as a byproduct of switching chat tools.

Frequently Asked Questions

Will past chat histories transfer automatically?

Do not count on it. Until a historical conversation is explicitly present and opened in your new Unified Inbox, assume it is not there. Store your legacy platform's data export as an independent offline archive.

Can we run both tools in parallel for a week?

Only if the old tool does not send automated outbound messages or bot replies. Two conflicting auto-responders cause far more chaos than a brief, controlled manual window.

What should we tell our customers during the transition?

If the bot username or phone number stays the same, no public announcement is necessary—unless response times or conversational tone change. If you are changing usernames or numbers, configure the old bot to send a one-time redirect link before going permanently silent.

Do we need a software engineer to migrate our chats?

No, if you are simply reconnecting channels and staffing them with human agents. Yes, if your previous platform relied on custom backend webhooks or ERP integrations that must be recreated.

What happens to our existing agent accounts and logins?

Invite support agents to your new workspace and assign permissions according to your access control policy rather than sharing a single password. User accounts from your previous vendor do not carry over into volbor.

Helpful Resources and Related Solutions

  • Quick Start GuideWhy you need it: Complete an end-to-end test conversation before cutting off your old channel.
    What happens without it: You switch production channels blind without verifying connectivity.
  • Unified InboxWhy you need it: Ensure incoming conversations are immediately visible to active agents.
    What happens without it: Your channel is live, but your team has nowhere to reply.
  • Message Delivery TroubleshootingWhy you need it: Troubleshoot immediately if test messages fail to arrive after cutover.
    What happens without it: Channel downtime gets mistaken for an unexpected lull in customer demand.
  • Webhooks and APIWhy you need it: Re-establish downstream event streams to your internal database and CRM.
    What happens without it: Chats flow into the inbox, but your order fulfillment system remains blind.
  • Security & PermissionsWhy you need it: Assign discrete role-based access to reps instead of sharing credentials under pressure.
    What happens without it: Every team member has unrestricted visibility across all client conversations during the migration scramble.
  • Go-Live Launch PlanWhy you need it: Explicitly designate a queue owner in your new workspace.
    What happens without it: Operational rules remain tied to the old platform while messages flood into the new inbox.