---
title: "Drift Sunset 2027: Export Chat History and Pick a Replacement"
slug: drift-sunset-export-chat-history-and-pick-a-replacement
date: 2026-11-16
author: Abdul Wahab
categories: [Migration Guide, Help Desk]
excerpt: "Drift retires January 31, 2027 with data deleted May 1. Export contacts, conversation transcripts, and playbook docs before the deadline — plus how to pick the right replacement."
tldr: "Drift retires January 31, 2027 with data deleted May 1, 2027. Export contacts via CSV now, start API transcript extraction immediately (it is rate-limited), and match your replacement to the job Drift actually did."
canonical: https://clonepartner.com/blog/drift-sunset-export-chat-history-and-pick-a-replacement
---

# Drift Sunset 2027: Export Chat History and Pick a Replacement


# Drift Sunset 2027: Export Chat History and Pick a Replacement

Drift retires on **January 31, 2027**, or at the end of your contract if that comes first, according to Salesloft's Drift Sunset FAQ ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)). The chat widget, Drift Email, and every custom integration built on the Drift API stop working on that date. Any data you haven't exported is permanently deleted on **May 1, 2027**. Export contacts as CSV and pull conversation transcripts through the API now, then pick a replacement by the job Drift actually did for you.

This article covers the verified timeline, exactly what data to pull out, how to extract it through the API, the hidden cost of rebuilding playbooks, GDPR/CCPA implications of the deletion deadline, and which replacement platform fits based on what Drift was actually doing for you.

> [!NOTE]
> **Disclosure:** ClonePartner provides paid migration services for teams moving off Drift. We've done our best to keep this analysis balanced.

## What Is Happening to Drift?

**Drift is being sunset by Clari + Salesloft**, which announced the gradual retirement in March 2026, naming 1mind as the successor under an exclusive agreement ([salesloft.com](https://www.salesloft.com/company/newsroom/1-mind-partnership)). Existing Drift customers are being *referred* to 1mind — not migrated. 1mind did not acquire Drift or its data.

Here is the verified timeline, sourced from the March 2026 announcement and Salesloft's Drift Sunset FAQ ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)):

| Date | Event |
|---|---|
| February 2024 | Salesloft acquires Drift |
| August 2025 | Drift security breach disclosed |
| December 2025 | Clari + Salesloft merger closes |
| March 2026 | Gradual sunset announced; 1mind named as successor |
| October 26, 2026 | Current version of Salesloft's Drift Sunset FAQ published, with firm dates |
| **January 31, 2027** | **Drift retired: chat widget, Drift Email, and API integrations stop** |
| Through April 30, 2027 | Remaining data stored offline (not accessible via product) |
| **May 1, 2027** | **All unexported Drift data permanently deleted** |

Salesloft's FAQ states that access ends on January 31, 2027 "or on the end date of your current contract, whichever comes first." If your contract expires before that date, your access ends earlier. Contracts running past January 2027 do not keep Drift alive: Salesloft says your account team reviews those case by case. Confirm your own end date with Salesloft in writing.

**What happens to conversations in flight on January 31?** Salesloft has not published explicit handling for active conversations open at the moment of shutdown. Any conversation not closed and exported before January 31 should be treated as potentially unrecoverable. Do not rely on the offline storage window (February–April 2027) as a fallback for active conversation data.

## What Data Lives Inside Drift?

Before exporting anything, map the objects. Drift holds five categories of data that matter for migration and compliance:

- **Contacts and leads** — email, name, company, custom attributes, enrichment data, and segment membership. A contact can be anonymous (identified only by a cookie or IP) or known (tied to an email address).
- **Conversation history** — full chat transcripts with timestamps, assignees, tags, and thread structure. A conversation in Drift is a parent object; individual messages, bot prompts, and human handoffs are child objects tied to a conversation ID.
- **Playbooks and routing rules** — bot flows, branching logic, widget configuration, and lead-routing configurations. These do not export in a portable format.
- **Meeting-booking history** — booked meetings, calendar integrations, and CQL (Conversation Qualified Lead) scores.
- **Drift Email data** — Drift Email (formerly Siftrock) processes replies to your marketing emails, so it holds reply-handling rules and the contact updates it found in replies (covered separately below).

Each category exports differently. Some don't export at all.

## GDPR, CCPA, and the May 1 Deletion Deadline

The May 1, 2027 permanent deletion is not just an operational inconvenience — it has legal implications for companies subject to data retention regulations.

**GDPR (EU/UK).** Under Article 5(1)(e), personal data must not be kept longer than necessary, but controllers are also required to maintain records of processing activities and may have contractual or legal obligations to retain certain communications. If Drift conversation transcripts constitute records of consent, contract formation, or complaints, losing them on May 1 could leave you unable to demonstrate consent under Article 7(1). Data subjects also have rights of access under Article 15 — if a subject submits a SAR after May 1 and you have no exported copy, you cannot fulfill it.

**CCPA (California).** The CCPA requires businesses to disclose what personal information they have collected about a consumer upon request. If Drift held personal data about California residents and that data is deleted before you export it, you lose the ability to respond to consumer access requests. CCPA does not mandate retention, but it does require you to know what you held — and if regulators investigate a complaint from a California resident whose chat data was involved, "it was deleted when our vendor shut down" is not a safe harbor.

**Practical minimum.** Export and retain all conversation records involving named contacts for at least as long as your existing data retention policy requires. Consult your legal team on specific retention obligations before treating May 1 as a natural deletion date.

## How to Export Contacts and Leads From Drift

**Drift contact records export cleanly as CSV** from the dashboard — no API required. Go to **Visitors → All Contacts**, create a filter for the contacts you need, save it as a dynamic segment, and choose **Export CSV of segment** under **Manage members**. Drift emails you the CSV of those contacts and their attributes ([help.salesloft.com](https://help.salesloft.com/s/article/Drift---Export-Drift-Data?language=en_US)).

Before you export, reconcile against your CRM. Any leads Drift already synced to Salesforce, HubSpot, or Marketo are already in your CRM and don't need to be migrated separately. The contacts that exist *only* in Drift are the ones at risk.

> [!TIP]
> Run the export now — don't wait for a deadline that arrives with less lead time than your data volume requires.

## How to Export Conversation Transcripts From Drift

**Drift has no bulk export button for full conversation transcripts.** The only way to get them out is through the Drift API. Drift's developer documentation says it has no bulk export for all conversation data, mostly for performance reasons ([devdocs.drift.com](https://devdocs.drift.com/docs/how-to-export-conversations-from-drift)).

Drift's export guide offers conversation report data as a CSV from **Reports → Chat data**, and that report refreshes about every four hours ([help.salesloft.com](https://help.salesloft.com/s/article/Drift---Export-Drift-Data?language=en_US)). It is report data, not a transcript archive. For the full record, you need the API. The preference for extraction is always **API → JSON → CSV**: relying on CSV exports for chat data strips out metadata, flattens threading, and breaks agent attribution.

### The N+1 query problem

Extracting conversations via the Drift API introduces a classic **N+1 query problem**. You first get a list of conversation IDs, then hit multiple endpoints per conversation to get the actual data.

**1. Gather conversation IDs.** Two options per Drift's developer docs ([devdocs.drift.com](https://devdocs.drift.com/docs/how-to-export-conversations-from-drift)):
- **Conversation_Push webhook** — fires each time a conversation closes, giving you the conversation ID in real time. Drift describes it as the more performant option and the one its native integrations use.
- **List Conversations endpoint** (`GET /conversations/list`) — returns conversations paginated (up to 100 per page, default 25), ordered by most recently updated ([devdocs.drift.com](https://devdocs.drift.com/docs/list-conversations)). Use this for historical backfill.

**2. Pull full conversation data for each ID.** Loop through IDs and hit two endpoints per conversation:
- **Conversations endpoint** (`GET /conversations/{id}`) — returns metadata: participant IDs, tags, status, related playbook, timestamps.
- **Transcript endpoint** (`GET /conversations/{id}/transcript`) — returns a formatted text string of the full chat transcript. Drift also offers `GET /conversations/{id}/json_transcript`, which returns the transcript as raw JSON ([devdocs.drift.com](https://devdocs.drift.com/docs/retrieving-a-conversations-transcript)).

**3. Resolve numeric IDs.** The API returns numeric IDs for playbooks and users, not human-readable names. Resolve these through the Playbook and User APIs during export, or your archive will be unreadable.

### Sample API response structure

A `GET /conversations/{id}` response has this shape ([devdocs.drift.com](https://devdocs.drift.com/docs/retrieve-a-conversation)):

```json
{
  "data": {
    "id": 1234567890,
    "status": "closed",
    "participants": [112233, 445577],
    "contactId": 9876543210,
    "inboxId": 62491,
    "createdAt": 1700000000000,
    "updatedAt": 1700003600000,
    "relatedPlaybookId": 445566,
    "conversationTags": [
      { "color": "0960C5", "name": "enterprise" }
    ]
  }
}
```

Note: `participants` and `relatedPlaybookId` are numeric IDs. Resolve playbook names with `GET /playbooks/list`, which returns only enabled and active playbooks ([devdocs.drift.com](https://devdocs.drift.com/docs/get-playbooks)), and user names through the Users API. A `GET /conversations/{id}/transcript` response returns a formatted string, not structured JSON.

**What this means for migration:** If you need to know where a bot handed off to a human, pull the Messages endpoint (`GET /conversations/{id}/messages`) instead of, or as well as, the formatted transcript. It returns messages in pages of 50, and each message's `author` object carries a `type` (contact or user) and a `bot` flag ([devdocs.drift.com](https://devdocs.drift.com/docs/message-model)). Neither endpoint returns the playbook's branching logic, so document that separately before your access ends.

Drift provides an official reference implementation: a Node.js script in the [Driftt/Drift-Bulk-Export-Transcript](https://github.com/Driftt/Drift-Bulk-Export-Transcript) repository on GitHub. It requires a Drift App API key with `conversation_read`, `user_read`, and `contact_read` scopes ([devdocs.drift.com](https://devdocs.drift.com/docs/bulk-conversations-transcript-export)).

### The rate limit bottleneck

**Drift's default API rate limit is 600 requests per minute** ([devdocs.drift.com](https://devdocs.drift.com/docs/faqs)). That is the ceiling on extraction speed. Each conversation requires at minimum two API calls (detail + transcript), plus additional calls to resolve playbook and user IDs and to download attachments. Effective throughput for a full extraction is well under 300 conversations per minute.

If you have 50,000 historical conversations, you're looking at 100,000+ individual API calls at minimum — close to three hours at the default limit before any retries. Your extraction script must implement **exponential backoff** to handle HTTP 429 Too Many Requests responses. A naive script that blasts the endpoints will be throttled immediately, and if it doesn't retry correctly, you'll get silent data loss.

Retries, attachment downloads and ID lookups stretch that further, so this is not the single afternoon most teams assume. If conversation transcripts matter for compliance, training data, or dispute records, start the extraction now. Don't couple it to your replacement decision.

> [!WARNING]
> Salesloft has not committed to keeping Drift's API endpoints available after the January 31, 2027 retirement date. Its FAQ says custom API integrations built on the Drift API stop working at the sunset. Budget your extraction time accordingly.

## Identity Resolution and Attachment Handling

Extracting the text is only the first step. The data must be transformed so it makes sense in the target platform.

**Identity mapping.** A message in Drift has an `author` object with a numeric `id`, a `type`, and a `bot` flag. That numeric ID means nothing to your new platform. During migration, you must maintain an identity map that translates each Drift author ID to the corresponding agent ID in the target system (e.g., an Intercom `admin_id`). If the author was a bot, the message must be mapped to the target system's bot user or tagged as an automated message. Build this lookup table before you begin importing — retrofitting identity mapping after the fact requires a full re-import.

**Attachment handling.** Buyers and reps frequently upload files during chat. Drift hosts these files and lists them in the message payload with a `driftapi.com/attachments/{id}/data` URL that you download with your API token ([devdocs.drift.com](https://devdocs.drift.com/docs/retrieving-a-conversations-attachments)).

> [!WARNING]
> **The broken link trap:** If you migrate only the text of the chat, the attachment URLs will point to Drift's servers. When Drift shuts down, those links will 404, and the files will be gone forever.

A proper migration must intercept every attachment URL, download the binary file, upload it to the target platform's storage, and rewrite the URL in the migrated transcript payload. This is a multi-step transformation that must happen during migration, not after.

> [!NOTE]
> Most replacement platforms cannot import Drift conversation transcripts as native conversation records. In practice, historical transcripts land in an archive or are attached to contact records as notes — not as threaded conversations you can reply to. Set expectations internally before the migration.

## What Doesn't Export From Drift

Not everything comes out cleanly:

- **Playbook logic** — Drift playbooks have no native bulk export. The Playbook API only returns metadata for enabled and active playbooks, not a portable flow definition ([devdocs.drift.com](https://devdocs.drift.com/docs/get-playbooks)). You cannot export a JSON file of your Drift routing rules and import it into Intercom, Qualified, or 1mind. You must manually screenshot and document every playbook's branching logic. This becomes your requirements spec for the replacement platform.
- **Routing rules** — Lead routing configurations are proprietary to Drift's runtime and must be manually recreated.
- **Custom attribute definitions** — Drift's custom contact attribute schema doesn't map 1:1 to other platforms. Plan your attribute mapping before you run any import.
- **Playbook performance metrics** — These *can* be exported as CSV from the Playbook Performance chart under **Reports → Playbooks → Chat playbooks** ([help.salesloft.com](https://help.salesloft.com/s/article/Drift---Export-Drift-Data?language=en_US)), but the export is aggregate data, not per-conversation.
- **Bot branching logic behind transcripts** — As noted above, neither the transcript nor the messages endpoint returns the playbook branch that produced a given conversation path. It is not recoverable from historical export.

### Estimating playbook rebuild effort

The engineering effort to recreate playbook and routing logic in a new platform frequently exceeds the effort to move the actual conversation data. Use this rubric to rank rebuild scope before you select a replacement:

| Playbook complexity signal | Relative rebuild effort |
|---|---|
| Linear flow, 1–3 decision nodes, no CRM writes | Low |
| Branching flow, 4–8 nodes, 1–2 CRM field writes | Medium |
| Multi-path flow, 9+ nodes, 3+ CRM field writes, segment conditions | High |
| Account-based routing with firmographic conditions | High, per routing rule |

Count branches, not just playbooks: a single playbook with many branches can carry more rebuild work than several linear ones. Start scoping and the internal rebuild now — the replacement has to be live before your Drift access ends on January 31, 2027 or at your contract end, whichever comes first.

## Drift Email: What It Is and What to Export

Drift Email is a distinct product from the chat widget. It is the email reply management tool Drift acquired as Siftrock: it sorts the replies that land in a marketing inbox, separates human replies from automated ones such as out-of-office notices, routes the human replies to the right rep, and picks up unsubscribes and contact changes from replies ([mediapost.com](https://www.mediapost.com/publications/article/349092/drift-rebrands-its-email-marketing-tool-as-drift-e.html)). It is not a chat channel and not a conversation threading layer.

**What to capture before it stops:**
- The reply-processing and routing rules you configured, documented manually, because they are configuration rather than exportable records.
- The contact updates Drift Email has pushed to your marketing automation platform or CRM. Confirm they already landed there.
- Any Drift Email data you need beyond that. Salesloft's FAQ says export requests go through your Account Manager or Support ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)).

**The replacement:** Drift Email (Siftrock) stops on the sunset date along with the chat widget. Salesloft's FAQ names allGood as its recommended replacement for Drift Email ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)). Factor reply management into your replacement evaluation separately from chat.

## How to Choose a Drift Replacement

The right replacement depends on the job Drift was actually doing for your team. Drift spanned conversational marketing, sales chat, ABM, meeting booking, and email reply management, but most teams used it for one or two of those jobs. Because you have to rebuild playbooks anyway, this is the time to evaluate whether your conversational strategy has evolved beyond Drift's original scope.

### Replacement platform comparison

Prices are as of November 2026; check each vendor's pricing page before you commit.

| Platform | Best fit | Starting price | Salesforce native | AI agent pricing | Transcript import | Migration difficulty |
|---|---|---|---|---|---|---|
| **Qualified** | ABM + pipeline on Salesforce | Enterprise (undisclosed) | Yes (Salesforce-acquired 2026) | Piper AI, bundled | No native import | High — playbooks rebuild from scratch |
| **Intercom** | Blended sales + support, multi-channel | $29/seat/month (Essential, billed annually) | Via integration | Fin AI Agent: $0.99/outcome | Contacts + notes; not threaded | Medium — well-documented migration path |
| **HubSpot Chat + Customer Agent** | Inbound qualification, existing HubSpot CRM | Free (chat widget) | Via HubSpot CRM | Customer Agent: $0.50/resolved conversation | Contact records only | Low — if already on HubSpot |
| **1mind** | AI-driven inbound demos | Undisclosed, demo required | Unknown | Core product capability | Unknown | Unknown — no published migration docs |

### If Drift was your sales chat and pipeline tool on Salesforce

**Qualified** is the most direct functional replacement for Drift's ABM playbook: visitor intelligence, AI-driven lead routing, and meeting booking built natively on Salesforce. Salesforce completed its acquisition of Qualified on April 1, 2026, and said the deal would accelerate its Agentforce Sales and Agentforce Marketing products ([salesforce.com](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-qualified/)). If your pipeline workflow was Drift → Salesforce, Qualified is the closest like-for-like swap. Qualified does not publish pricing; expect enterprise-level contracts requiring a sales process.

### If Drift handled both sales chat and support

**Intercom** is the strongest option for blended sales and support workflows. It covers chat, email, SMS, WhatsApp, phone, and social. As of November 2026, Intercom's Fin AI Agent costs $0.99 per outcome, the Essential plan lists at $29/seat/month billed annually, and a 14-day free trial is available ([intercom.com](https://www.intercom.com/pricing)).

The Drift-to-Intercom migration is well-documented. The main pain points are transcript extraction (API rate limits), custom attribute mapping (different schemas), and playbook rebuild (manual). Our [Intercom vs Drift comparison](https://clonepartner.com/blog/blog/intercom-vs-drift-2026-the-operations-leads-decision-matrix) covers the full technical mapping.

### If you're already on HubSpot

**HubSpot Chat + Customer Agent** is the path of least resistance for teams whose CRM is already HubSpot. The chat widget is free. As of November 2026, HubSpot's Breeze Customer Agent costs $0.50 per resolved conversation and runs on Professional and Enterprise subscriptions ([hubspot.com](https://www.hubspot.com/company-news/hubspots-customer-agent-and-prospecting-agent-now-you-pay-when-the-task-is-complete)). No separate contract or vendor relationship to manage.

HubSpot Chat lacks Drift's ABM-level visitor targeting and the conversational AI depth of Intercom or Qualified. For simple meeting booking and inbound qualification it's adequate. For pipeline generation at scale, it is a step down in capability.

### What about 1mind?

**1mind** is the successor Salesloft named, but it's a referral partnership, not a migration path. Salesloft's FAQ recommends 1mind for Drift's chatbot functionality and allGood for Drift Email ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)). 1mind focuses narrowly on inbound qualification and AI-powered demos — it is not a full replacement for everything Drift did. It has no published pricing and requires a demo to evaluate. Do not default to it because Salesloft pointed you there; evaluate it against the specific jobs Drift was doing for your team.

For a wider comparison of customer communication platforms, see our [Intercom alternatives guide](https://clonepartner.com/blog/blog/intercom-alternatives-2026-costs-features-migration-paths).

## How Long Does a Drift Data Migration Take?

Keep two clocks strictly separate when planning this transition: the **data migration clock** and the **platform rebuild clock**. Conflating them is the most common planning mistake.

### The data migration clock

The data migration is the physical movement of your historical records, and it is the clock ClonePartner runs. Contact records export as CSV and import quickly — that's the easy part. Conversation transcripts are the bottleneck. At 600 requests per minute with multiple calls per conversation, a Drift account with 50,000+ conversations needs hours of continuous API extraction before you can begin the import.

Most migrations we run are completed within 1–5 business days, depending on data volume, complexity, and API rate limits. Small datasets (under 10,000 records) can finish in under 24 hours. The bulk history loads during the working days before go-live while your team keeps using Drift. On go-live Monday, Drift is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and your team logs in to the new platform that morning.

### The rebuild clock

This is your team's clock, not ours. Scoping, rebuilding playbooks, training staff, configuring the new widget, and running a parallel period depend entirely on your internal resources and cannot be compressed by faster data transfer. With Drift retiring on January 31, 2027 (or earlier, at your contract end), start the scoping conversation now.

## The Sequence That Reduces Risk

Here is the order of operations that minimizes data loss risk:

1. **Export contacts now.** CSV from Visitors → All Contacts. Takes minutes. Do it today as a safety net regardless of where you are in your replacement evaluation.
2. **Start API extraction of conversation transcripts.** This is the long pole in the tent. Budget hours of rate-limited calls for large accounts, plus time to rerun failures. Don't wait for the replacement decision to begin extraction — the data doesn't need to be in a new platform to be safe.
3. **Document every playbook and routing rule.** Screenshot each flow, note every branching condition, and list which CRM fields each playbook writes to. Use the complexity rubric above to estimate rebuild effort before you finalize a replacement decision.
4. **Document Drift Email reply rules** using the same approach as step 3. These need manual recreation in your reply management replacement.
5. **Revoke Drift OAuth tokens** you no longer need — especially if your organization was affected by the August 2025 security breach, after which Google's Threat Intelligence Group advised treating every token stored in or connected to Drift as potentially compromised ([cloud.google.com](https://cloud.google.com/blog/topics/threat-intelligence/data-theft-salesforce-instances-via-salesloft-drift)).
6. **Evaluate replacements** against the documented audit from steps 3–4, not against Drift's feature list. Confirm how each candidate handles transcript import and email reply management before committing.
7. **Run the replacement in parallel** for as long as your remaining Drift access allows before removing the Drift widget. This gives you a live validation period before the hard deadline.
8. **Import historical data** into the new platform, validating field mapping on a sample of 50–100 conversations before running the full import.

## What Happens If You Miss the Deadline?

After **January 31, 2027**, the Drift chat widget stops working on your website, Drift Email stops, and custom API integrations break. Salesloft says it keeps remaining data offline through April 30, 2027 so you can still request an export ([help.salesloft.com](https://help.salesloft.com/s/article/Drift-Sunset-FAQ?language=en_US)) — but that is offline storage, not a working product. You would need to ask your Account Manager or Salesloft Support for an export during that window, and there is no published SLA for how quickly Salesloft will respond to such requests. Ask Salesloft in writing how the window applies to your contract.

On **May 1, 2027**, Salesloft permanently deletes all remaining Drift data. The Sunset FAQ is explicit: this deletion is final and the data will not be recoverable.

The export deadlines are what actually matter. Have your data out before your access ends. The offline storage window is not a safety net you can plan around.

## How ClonePartner Handles Drift Migrations

ClonePartner is an engineer-led service that has executed 1,500+ successful migrations, rated 4.8/5 from 18 reviews on G2. We don't offer a self-serve tool — a dedicated migration engineer owns your project from scoping to cutover.

- **Fixed pricing:** One fixed price per project, starting at $500. No hourly billing, no per-record pricing.
- **Unlimited sample migrations:** We run sample migrations until the data mapping is right. Included in the fixed price.
- **Multi-stage validation:** Record-count parity, field-level validation, and referential integrity checks — so chats stay tied to the correct contacts.
- **Security:** SOC 2 Type II and ISO 27001 (independently audited). AES-256 at rest, TLS 1.2+ in transit. Staging databases are purged within 30 days of project close.

> Moving off Drift and need conversation history preserved? Book a free 30-minute scoping call. We'll review your Drift data volume, evaluate your target platform's API constraints, and provide a fixed-price proposal to secure your chat history before the platform goes dark.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### When is Drift shutting down?

Salesloft's Drift Sunset FAQ says Drift retires on January 31, 2027, or at your contract end date, whichever comes first. The chat widget, Drift Email, and custom API integrations all stop on that date. Unexported data is permanently deleted on May 1, 2027.

### How do I export my Drift conversation history?

Drift has no bulk export for full conversation transcripts. Contact records export as CSV from Visitors → All Contacts. Full transcripts require the Drift API: list conversation IDs via the List Conversations endpoint, then pull each transcript via GET /conversations/{id}/transcript. Drift's default rate limit is 600 requests per minute, so a large account's extraction runs for hours, not minutes.

### Can I export Drift playbooks to another platform?

No. Drift playbooks have no native bulk export. The Playbook API only returns metadata for enabled and active playbooks, not portable flow definitions. You must manually screenshot and document each playbook's branching logic and routing rules, then rebuild them in your new platform.

### What is the best Drift replacement in 2026?

It depends on what Drift was doing for you. For enterprise ABM on Salesforce, Qualified is the closest match. For blended sales and support with multi-channel reach, Intercom is the strongest option. For teams already on HubSpot, HubSpot Chat is the simplest path. 1mind is the named successor but covers a narrower use case focused on AI inbound qualification.

### What happens to my Drift data after the sunset?

After January 31, 2027, Salesloft keeps remaining Drift data offline through April 30, 2027. On May 1, 2027, all remaining data is permanently deleted. Salesloft's FAQ states this deletion is final and the data will not be recoverable. Export before your access ends.
