April 11, 2026 • 7 min read
Switching CRMs is brutal. Not because the new software is hard to learn — most teams figure that out in a week. The brutal part is the migration. The data export. The field mapping. The integrations that need to be rewired. And sitting quietly at the bottom of every migration checklist, the task everyone underestimates: templates.
The Template Migration Problem
Every sales team has templates. Follow-up after a demo. Response to a pricing inquiry. Check-in after a proposal. The "just circling back" email that somehow accounts for 30% of all outbound communication.
These templates are the DNA of your sales process. They encode how your team talks to customers. The tone, the structure, the rhythm, the product references, the closing lines — years of iteration compressed into reusable blocks of text.
And when you switch CRMs, you lose them. Or more precisely, you have to move them by hand.
Best case: your old CRM has an export feature. You get a CSV or JSON file with template names, subjects, and bodies. You open the new CRM and start importing them one by one, fixing formatting issues, re-linking product references, adjusting variables from {FirstName} to {{customer_name}}. This takes a day. Maybe two if your library is large.
Average case: your old CRM exports templates but strips the formatting, corrupts the variables, or flattens the folder structure. You spend a day cleaning up a spreadsheet before you can even start importing.
Worst case: your old CRM has no template export. Your templates live inside their proprietary editor with no extraction path. You open the old system in one browser tab and the new system in another, and you start copying and pasting. Template by template. Field by field. For every. Single. One.
In all three cases, you're doing manual labor to reconstruct knowledge that already exists — in your team's sent emails.
The Templates Already Exist
Here is the thing nobody talks about during CRM migrations: the templates are not really in the CRM. The CRM has copies of the templates. The originals live in your team's outbox.
Every template started as an email someone wrote from scratch. Then they wrote a similar one the next day. And the day after that. Eventually someone noticed the pattern, extracted the common structure, replaced the names with variables, and saved it as a template. The CRM template is a snapshot of a pattern that emerged organically from real sales conversations.
So when you switch CRMs and lose the templates, you don't need to export them from the old system. You need to rediscover them from the source: the emails themselves.
AI Template Discovery
Today we're shipping a feature that eliminates template migration entirely. It's called AI Template Discovery, and it works like this:
Step 1 — Pick the mailboxes. In AI Settings, go to the Templates tab and select which team members' Gmail accounts to scan. You might start with your top rep, or select the whole team.
Step 2 — Set a budget. Choose how many sent emails the AI should read. Start with 200 for a quick scan, or go to 2,000 for deep historical coverage.
Step 3 — Press Start.
The AI reads your team's sent emails backward through time. It strips signatures, removes quoted text, and extracts the actual reply content. Then it groups similar messages — emails that say essentially the same thing to different people — and identifies the underlying pattern.
For each pattern it finds, it generates a clean template. Variables where names appeared. Placeholders where products were referenced. Usage notes explaining when a rep would typically send this message. If the content mentions a specific product from your catalog, the template is automatically tagged.
Before adding anything to your library, the AI checks each discovered template against your existing templates. If something similar already exists, it skips it. No duplicates.
Everything lands in a moderation queue where you can approve, edit, or reject each discovery. Or flip on auto-approve and let the AI populate your library directly.
The Budget Is a Dial, Not a Cliff
One detail that matters: the budget is resumable.
When you set a budget of 200 emails, the AI scans the 200 most recent sent emails. If it finds good patterns, great. If you want to go deeper, increase the budget to 500. The AI doesn't restart — it picks up exactly where it left off and continues backward through your email history.
This is important because template patterns aren't uniformly distributed. Your team might have shifted messaging three months ago after a product launch. The templates from before the launch are different. Going further back discovers a different layer of patterns.
Start small. Review the results. Increase the budget. Repeat. Each pass uncovers more of your team's communication DNA.
Why This Matters Beyond Migration
Template Discovery isn't just a migration tool. It's useful in three scenarios that every sales org encounters:
New CRM onboarding. The obvious case. You just signed up for Slokoto. Your templates are in another system (or in no system — just muscle memory). Run a discovery scan and have a working template library in minutes instead of days.
New hire onboarding. A new rep joins the team. They don't know the messaging patterns yet. Run discovery against the top performer's mailbox. The new hire gets a template library that encodes the team's best practices — extracted from real conversations, not a training document nobody reads.
Template drift detection. Your team has templates, but nobody's updated them in six months. Meanwhile, the actual messaging has evolved. Run discovery and compare what the AI finds against what's in your library. The gaps tell you which templates need updating and which new patterns have emerged that deserve to be formalized.
What Good Discovery Looks Like
We tested this internally with real sales mailboxes. Here's what the AI typically finds:
High-confidence patterns — the follow-up after no response, the pricing breakdown email, the demo scheduling message. These show up in almost every sales team's outbox with high occurrence counts. The AI nails these.
Product-specific responses — emails that explain a particular product's features, handle a common objection, or compare against a competitor. These get auto-tagged with the right product from your catalog.
Stage-specific templates — different messaging for different pipeline stages. Early-stage outreach looks nothing like late-stage negotiation. The AI picks up on these distinctions and generates separate templates for each.
The templates you didn't know you had — patterns that nobody consciously templated. The way your team handles a scheduling conflict. The language they use when a deal goes cold. Informal templates that were never formalized because nobody noticed the repetition.
What It Doesn't Do
Transparency matters, so here's what Discovery is not:
It is not a bulk email importer. It doesn't copy your old templates from another system. It discovers patterns from scratch by reading actual sent email.
It is not perfect. AI pattern detection works on repetition. If a template was only used twice in your email history, the AI might miss it. Increase the budget to give it more data.
It does not read inbound email. Discovery only scans outbound messages — what your team sent. Customer emails are never included in the pattern detection.
It does not run automatically. You start a scan manually and review the results. There is no background crawler mining your email without your knowledge.
The Migration Tax Is Over
Every CRM switch has carried a hidden tax: the manual labor of reconstructing your team's communication patterns in a new system. Export, clean, import, fix, test, repeat. It's tedious, error-prone, and it punishes teams for having a rich template library — the more templates you have, the more painful the migration.
AI Template Discovery eliminates that tax. Your templates aren't in your old CRM. They're in your email. They've been there all along. You just needed AI to read them.
Connect your Gmail. Set a budget. Press Start. Your template library builds itself.
This is part of a series on building AI-native sales software. Previously: Your CRM Runs AI Backwards — why AI should trigger on customer signals, not rep actions. Also: The Last Form Builder You'll Ever Touch — how AI generates lead capture forms from your website.