Migration guide

Migrate from your incumbent chatbot to SLAtech

Per-vendor migration playbooks for Intercom Fin, Drift, Chatbase, Tidio Lyro and Botpress. Export paths, mapping to SLAtech shape, channel re-wire steps and time estimates per vendor. Pairs with the buyer guide and comparison matrix.

Per-vendor playbooks

From Intercom Fin

Why migrate: Per-resolution billing penalises successful deflection; US-only hosting; Hebrew / Russian first-class support is absent.

Export path: Export Articles via the Intercom Help Center API (`GET /articles`). Conversation history via the Conversations API. CSV download supported for a subset.

Import to SLAtech: Articles map to SLAtech FAQ entries (Markdown). Conversation history uploads via a Worker job — JSONL ingest pipeline accepts the Intercom shape. CRM webhooks reconnect by pointing to SLAtech's `lead.captured` event (HubSpot, Salesforce, Pipedrive native).

⏱ Knowledge migration: ~2 hours for a typical 200-article export. End-to-end switchover including channel re-wire: ~1 business day.

From Drift

Why migrate: Web-widget centric; legacy per-conversation pricing; channel coverage limited compared with modern messaging platforms.

Export path: Drift Playbook export via the Drift Conversation API (`GET /conversations`). Knowledge entries via the Playbook editor's JSON export. Web-widget config re-creatable from screenshot.

Import to SLAtech: Playbook flows translate to SLAtech intent rules + FAQ pairs; the vertical-graduation engine surfaces unmatched traffic. Multi-channel rewire: Telegram + WhatsApp Business onboarding (45 minutes total). Calendar sync re-binds to Google Calendar / Outlook on the Pro tier.

⏱ Knowledge migration: ~3 hours for typical Drift Playbook complexity. End-to-end: ~1.5 business days.

From Chatbase

Why migrate: Iframe-only widget; no native messaging channels; LLM-provider key passthrough means buyer absorbs token cost.

Export path: Chatbase knowledge sources are PDF / text uploads + crawled URLs. Re-export via the original PDF / URL list. Conversation history not always exportable depending on tier.

Import to SLAtech: Re-upload sources to SLAtech ingest pipeline (PDF / DOCX / URL crawler). Native multi-channel ships immediately — web + Telegram + WhatsApp Business in the Pro tier. Token cost included in the flat-tier price; no separate language-model billing.

⏱ Knowledge migration: ~1 hour for typical Chatbase corpus. End-to-end: ~half business day.

From Tidio Lyro

Why migrate: Conversation cap on lower tiers; English-first multilingual support; per-vertical posture is absent.

Export path: Tidio Conversation API (`GET /v1/conversations`) for history; knowledge entries via the Lyro training UI's CSV export. Visitor identifiers exportable via the Contact API.

Import to SLAtech: Conversation history ingests via JSONL. Knowledge entries map to FAQ pairs. Conversation cap dissolves on SLAtech (unlimited within reasonable use on flat-tier). Vertical-specialised verticals (Med, Beauty, Hospitality, Sales, Legal, Event, Fitness, Edu) available if industry-tuned posture is preferred over generic SMB shape.

⏱ Knowledge migration: ~2 hours. End-to-end: ~1 business day.

From Botpress

Why migrate: Self-hosted ops burden; visual flow editor locks knowledge in a proprietary format; Hebrew RTL support is community-supplied.

Export path: Botpress flow export via Studio (`.bpfs` archive). Knowledge sources are uploaded files re-exportable via the file API. Bot configuration JSON via the Admin API.

Import to SLAtech: Visual flows decompose to SLAtech intent + FAQ shape — the LLM-routed retrieval pipeline often replaces multi-step flows entirely. Self-host ops burden disappears (SLAtech is a fully managed cloud with an Enterprise single-tenant option). Hebrew + Russian RTL polish ships first-class.

⏱ Flow translation: ~4 hours for a typical Botpress bot. End-to-end including self-host decommission: ~2 business days.

Common migration process

  1. 1. Inventory the incumbent

    List every knowledge source, conversation history bucket, channel endpoint and CRM integration that depends on the incumbent. Decision: keep, rebuild or retire.

  2. 2. Export everything per the playbook above

    Use the incumbent's documented API or CSV export. Validate the export by opening a sample manually — exports often skip rich-text formatting, attached images or conversation metadata.

  3. 3. Map to SLAtech shape

    Knowledge → FAQ pairs or Markdown articles. Conversations → JSONL. Channel endpoints → SLAtech channel onboarding wizard. CRM webhooks → SLAtech `lead.captured` event payload.

  4. 4. Run parallel for one week

    Configure SLAtech bot on a subdomain or second widget slot; route 10-20% of live traffic to SLAtech. Compare answers side-by-side. Adjust the SLAtech knowledge corpus where retrieval misses.

  5. 5. Cutover + 30-day retention

    Switch primary widget src to SLAtech. Keep incumbent paid up for 30 days as a safety net. Lead-capture webhook points to the same CRM throughout. SLAtech eval scoreboard runs nightly so quality regressions are caught automatically.

Ready to plan your migration?

30-second product-fit quiz, or talk to the founder for a tailored migration plan.

Take the quiz info@slatech.ai

Buyer evaluation tools

Four self-serve tools for evaluating SLAtech (or any AI chatbot vendor) without a sales call:

Eval scoreboard 200-question per-vertical methodology TCO calculator Annual savings + payback period Vendor compare-tool Filter 16 vendors by 6 criteria Vendor checklist 30 procurement due-diligence questions