How to Import Your Gmail History Into a Shared Inbox
One of the biggest friction points when teams consider moving away from Gmail is the history question: "What happens to all our old conversations?"
It's a legitimate concern. Years of customer interactions — resolved issues, purchase histories, troubleshooting threads — live in that Gmail account. Starting fresh means losing context your team actually needs.
Smailor lets you import emails directly from an existing Gmail account. Your threads, context, and history carry over so your team doesn't start from zero.
Why email history matters more than people think
When a customer writes in, the first thing a good support agent does is look at what happened before. What did they buy? Have they contacted us about this before? Did we promise them something?
Without history, every returning customer is a stranger. You ask them to explain their situation again — which they find frustrating — or you answer without context, which leads to inconsistent responses.
This is why "just start fresh with a new tool" is rarely a real option for teams with existing customer relationships. The history isn't just nice to have — it's how you deliver consistent service.
What the Gmail import covers
When you connect your existing Gmail account to Smailor for import, you bring over:
Full email threads. Not just individual messages — entire conversations with the correct threading, so your team can read the full back-and-forth between your company and each customer.
Timestamps and metadata. Who sent what, and when. This matters for understanding response times and context ("this was sent right after the incident on March 12th").
Sender and recipient information. The customer's email address, the team address they contacted, and any CC'd parties.
Existing labels and categories (where applicable). If you've already organized your Gmail with labels for different issue types or accounts, that structure can carry across.
How the import process works
The import connects via Gmail's standard OAuth flow — you authorize Smailor to read your existing Gmail account, select what to import (all email or a filtered subset), and the import runs in the background.
You don't need to forward emails manually. You don't need to export and re-import CSV files. The connection is direct.
Once the import completes, your historical threads appear in Smailor alongside new incoming email, correctly attributed to the right customer addresses. Your team can search, browse, and reference that history exactly as if the conversations had always lived in Smailor.
What stays the same for your customers
Nothing changes on the customer side. They keep writing to the same address they always have ([email protected] or whatever you use). Smailor receives the email, routes it according to your rules, and your team responds — all from within Smailor.
From the customer's perspective, the tool change is invisible. They don't get a "we've moved platforms" message, they don't need to update any contact, and their email history with you is intact on your end.
A note on MX records
The email import covers historical threads from Gmail. Going forward, new email is routed through Smailor by updating your domain's MX records to point to Smailor's mail servers.
This is a one-time DNS change. Most registrars take under 5 minutes to update, and propagation typically completes within an hour. Smailor's setup docs walk through this step-by-step for all major registrars and DNS providers.
During the transition window, email continues to arrive in Gmail so nothing is lost, and once propagation completes, all new mail routes directly to Smailor.
When to import vs. when to start fresh
Import makes sense when:
- Your team has significant customer history that agents actively reference
- You have returning customers who expect you to know their context
- You're running subscription, SaaS, or ongoing-service business models where history is a core part of the relationship
Starting fresh may be fine when:
- You're a new team with no existing email history
- You're setting up a brand new support address
- Your volume is low enough that agents naturally remember frequent customers
For most teams moving from an established Gmail setup, import is the right call. The cost of losing context — re-explaining situations to customers who've been with you for years — is higher than the few hours the import takes.
Already using Google Workspace?
If your Gmail account is through Google Workspace (formerly G Suite), the import works the same way. You connect with your Google Workspace credentials and import from the relevant inbox.
Teams on Google Workspace often have more complex setups — aliases, multiple inboxes, group addresses — and Smailor's import handles these. You can select which address or inbox to import from rather than pulling everything indiscriminately.
The bottom line
Switching support tools is always a project. But "we can't lose our history" is no longer a reason to stay on a tool that doesn't work well for your team.
Smailor's Gmail import removes the history problem from the equation. You set up your shared inbox, import your existing threads, update your MX records, and continue where you left off — this time with assignments, internal notes, routing rules, and all the structure Gmail never gave you.