Migrate off Qualified.ai — in 21 days
The week-by-week playbook used by HubSpot, Pipedrive, Dynamics, and Attio teams moving to Twig Sera. Includes the audit step that catches content gaps before they hit a customer, the pilot-week protocol that kept Klarna from happening to you, and CRM-specific integration notes at the bottom.
Audit + connect
- Export your last 90 days of Qualified chat transcripts. These are the single highest-leverage training input for Sera — they encode what your team actually qualifies on.
- List every Qualified routing rule, playbook, and integration. Map each to a Sera intent.
- Install the Sera widget on a staging or canary route. Do not remove Qualified yet.
- Connect your CRM (HubSpot / Pipedrive / Dynamics / Attio / Close / Folk) via OAuth. Map custom fields.
- Connect your calendar (Calendly, HubSpot Meetings, Chili Piper) for booking handoffs.
Human-review pilot
- Move Sera to a public path or 10–20% traffic slice. Keep Qualified live on the rest.
- Every Sera response is drafted but a human reviews before send. Track override rate. Target: under 5% by end of week.
- Fix content gaps (missing policy, wrong pricing, stale product info). The fix is in the knowledge base, not the prompt.
- Calibrate the confidence threshold — too low and Sera answers things it shouldn't; too high and it escalates everything.
- Pull a daily 20-conversation sample with the sales team. Adjust intent classifier and refusal patterns.
Autonomous on tier-1
- Promote Sera to autonomous on tier-1 intents: pricing questions, demo qualification, integration questions, product capability lookups.
- Keep complex intents (custom contract terms, security review, hardship cases) on human escalation with full context handoff.
- Add voice channel — Sera answers an inbound phone number. Wire it to your existing calendar.
- Run Sera and Qualified in parallel on the same widget surface for the final week of validation.
- Set a calendar invite for the day Qualified gets switched off.
Switch off Qualified
- Remove the Qualified script tag. Sera is now the only AI SDR on the site.
- Verify HubSpot / Pipedrive / Dynamics / Attio activity logging is unbroken.
- Move escalation routing fully to Sera's handoff path (Slack channel or shared inbox).
- Send a one-paragraph note to the sales team summarizing what changed and where escalations now land.
- Schedule a 30-day post-cutover review: autonomous-resolution rate, CSAT delta, demo-book rate.
Notes by CRM
The 21-day plan is CRM-agnostic, but the integration step differs. Quick notes per CRM below.
HubSpot
- Native OAuth. Sera reads contacts, deals, lifecycle stage, custom properties.
- Lead create or update writes back to HubSpot in real time. Lifecycle stage transitions trigger HubSpot workflows.
- Qualified's account-level visitor identification was Salesforce-leaning anyway — for HubSpot teams, Sera's reverse-IP + enrichment fills the same role.
- Most HubSpot teams reach feature parity in 14–28 days.
Pipedrive
- Native OAuth. Sera creates deals in the right pipeline + stage, attaches the contact, and logs the conversation as an activity.
- Round-robin and territory routing run before deal creation so ownership is correct from the start.
- Pipedrive shops typically migrate in 14–21 days — less integration surface area than HubSpot or Salesforce.
Microsoft Dynamics
- Dynamics integration runs through the Dataverse + custom connector. Setup is heavier than HubSpot or Pipedrive — typically 1 week of integration work in addition to the 21-day migration.
- Enterprise Dynamics teams almost always run inbound voice in addition to chat — that's the strongest argument for Sera over Qualified post-acquisition.
- If you're on Dynamics 365 Sales + Customer Service, the AI agent works across both surfaces.
- Plan for a 30-day timeline for full cutover rather than 21.
Attio · Close · Folk
- All three have native REST APIs. Sera integrates via direct API for contact and deal create + update. No OAuth marketplace listing yet — typically 2–3 days of setup work.
- These CRMs serve technical / early-stage teams. The evaluation cycle is short — most teams pilot and decide inside 14 days.
- Qualified's investment in these CRMs was always thin. Post-acquisition, it's effectively zero. The migration is mostly low-risk and the upside is uncapped active product.
People also ask
Why 21 days and not 7?+
Most of the 21 days is content audit, transcript review, and the human-review pilot — not technical setup. The technical install (Sera widget + CRM connection) takes hours, not weeks. The week-long human-review pilot is what catches hallucinations and content gaps cheaply, before they hit a customer. Skipping it is the most common failure mode we see in self-driven migrations.
Can we go faster?+
Yes if you skip the pilot or run autonomous from day one. We don't recommend it — the pilot week is where teams catch their actual content gaps. The Klarna walk-back happened in part because they skipped this phase. A faster migration is a more fragile one.
Do we need to coordinate with Qualified to migrate?+
No. Qualified contracts are typically grandfathered. You don't need to give Qualified notice; you just need to remove the Qualified script tag at cutover. You can run both in parallel during weeks 2–3 with no conflict.
What happens to our Qualified chat history?+
It stays in Qualified's database. You can export it via Qualified's admin panel during the contract period — we recommend doing that in week 1 as a precaution. Sera starts a fresh conversation history from cutover.
Who runs the migration on Twig's side?+
A Twig AI Specialist runs the kickoff call, the content audit, and the week-2 calibration session. You're not on your own — managed migration is included at $5/ticket pricing, not a separate fee.
Run this plan with us
30-min call to scope the migration. A Twig AI Specialist runs the audit + pilot week with you. No extra cost — managed migration is included.
