Migration guide

Migrate from your incumbent chatbot к SLAtech

Q: How do I migrate from Intercom Fin к SLAtech?

Export Intercom Articles via the Help Center API; map к SLAtech FAQ entries (Markdown). Conversation history ingests via JSONL. CRM webhooks reconnect к SLAtech's lead.captured event. Knowledge migration ~2 hours; end-to-end including channel re-wire ~1 business day.

Q: How do I migrate from Drift к SLAtech?

Drift Playbook export via the Conversation API + Playbook JSON export. Flows translate к SLAtech intent rules + FAQ pairs; the vertical-graduation engine surfaces unmatched traffic. Multi-channel rewire (Telegram + WhatsApp Business) takes 45 minutes. End-to-end ~1.5 business days.

Q: How do I migrate from Chatbase к SLAtech?

Chatbase knowledge sources (PDFs, crawled URLs) re-upload к SLAtech's ingest pipeline. Native multi-channel ships immediately. Token cost included в the flat-tier price (no separate OpenAI billing). End-to-end ~half business day.

Q: How do I migrate from Botpress к SLAtech?

Botpress flow export via Studio (.bpfs archive). Visual flows decompose к SLAtech intent + FAQ shape — LLM-routed retrieval often replaces multi-step flows entirely. Self-host ops burden disappears. End-to-end including self-host decommission ~2 business days.

Q: What's the safest cutover plan?

Run parallel for one week — route 10-20% of live traffic к SLAtech; compare answers side-by-side; adjust knowledge corpus where retrieval misses. On cutover, keep incumbent paid up for 30 days as safety net. Lead-capture webhook points к the same CRM throughout.

Per-vendor migration playbooks for Intercom Fin, Drift, Chatbase, Tidio Lyro и Botpress. Export paths, mapping к SLAtech shape, channel re-wire steps и time estimates per vendor. Pairs с the buyer guide и 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 а subset.

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

⏱ Knowledge migration: ~2 hours для а 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 с 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 к SLAtech: Playbook flows translate к 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 к Google Calendar / Outlook на the Pro tier.

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

From Chatbase

Why migrate: Iframe-only widget; no native messaging channels; OpenAI 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 к SLAtech: Re-upload sources к SLAtech ingest pipeline (PDF / DOCX / URL crawler). Native multi-channel ships immediately — web + Telegram + WhatsApp Business в the Pro tier. Token cost included в the flat-tier price; no separate OpenAI billing.

⏱ Knowledge migration: ~1 hour для 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`) для history; knowledge entries via the Lyro training UI's CSV export. Visitor identifiers exportable via the Contact API.

Import к SLAtech: Conversation history ingests via JSONL. Knowledge entries map к 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 если 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 а 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 к SLAtech: Visual flows decompose к SLAtech intent + FAQ shape — the LLM-routed retrieval pipeline often replaces multi-step flows entirely. Self-host ops burden disappears (SLAtech is EU-hosted cloud с Enterprise single-tenant option). Hebrew + Russian RTL polish ships first-class.

⏱ Flow translation: ~4 hours для а typical Botpress bot. End-to-end including self-host decommission: ~2 business days.

Common migration process

1. Inventory the incumbent
List every knowledge source, conversation history bucket, channel endpoint и CRM integration that depends on the incumbent. Decision: keep, rebuild или retire.
2. Export everything per the playbook above
Use the incumbent's documented API или CSV export. Validate the export by opening а sample manually — exports often skip rich-text formatting, attached images или conversation metadata.
3. Map к SLAtech shape
Knowledge → FAQ pairs или Markdown articles. Conversations → JSONL. Channel endpoints → SLAtech channel onboarding wizard. CRM webhooks → SLAtech `lead.captured` event payload.
4. Run parallel for one week
Configure SLAtech bot on а subdomain или second widget slot; route 10-20% of live traffic к SLAtech. Compare answers side-by-side. Adjust the SLAtech knowledge corpus where retrieval misses.
5. Cutover + 30-day retention
Switch primary widget src к SLAtech. Keep incumbent paid up для 30 days as а safety net. Lead-capture webhook points к the same CRM throughout. SLAtech eval scoreboard runs nightly so quality regressions are caught automatically.

Ready к plan your migration?

30-second product-fit quiz, или talk к the founder for а tailored migration plan.

Take the quiz → [email protected]