Bring your list across. Rebuild the rest.
Most of a migration is a CSV file. The rest is the part nobody advertises: your sequences get rewritten, your sending history stays where it is, and every mailbox you connect begins its ramp again. This page separates the two before you spend an afternoon on it.
No payment method. No recurring charge. Your own SMTP, your own data.
- Import limit
- 20,000 rows per file
- Column mapping
- Automatic, with preview
- Duplicates
- Removed on import
- Mailboxes
- Your own SMTP and IMAP
Three starting points, one file format.
The route in is the same in all three cases: a CSV. What differs is how much cleaning the file needs before it is worth uploading.
Another cold email tool
Instantly, Smartlead, lemlist or something similar. Export the contacts you still intend to reach and bring them in as a CSV. The file is all that travels: sequences and sending history stay in the tool that recorded them.
A contact database
Apollo, Clay or another source you already pay for. Export your saved list and import it here. MyLeadTeam does not resell a contact database, so a list you exported stays a list you own.
A spreadsheet or a CRM export
The most common starting point and the least painful one. Any CSV with a header row works. Columns are matched automatically and you correct the mapping on screen before a single row is written.
Six kinds of data, and where each one lands.
Nothing arrives in a general pool. Everything you bring is scoped to one project, and a project is one client.
Leads and their details
The import takes up to 20,000 rows per file, maps your columns automatically and removes duplicates. Leads land in that project's pool and wait there. Nothing is researched, written or sent as a side effect of an import.
Do-not-contact addresses
The suppression list is built inside your organisation and checked before every send. It travels out as a CSV export rather than in: what you bring from another tool is a lead list, not a block list.
Mailboxes
You connect SMTP and IMAP accounts yourself, and passwords are encrypted with AES-256-GCM at rest. The mailbox is the same one you were using before. What it did inside the previous tool is not visible here.
Sending volume
Warmup starts its ramp from the beginning for every newly connected mailbox. That is the real cost of the move, and it is worth planning the switch around rather than discovering it in week one.
Knowledge base material
Case studies, positioning notes and old briefs go in as uploads. The knowledge base accepts PDF, DOCX, images and plain text, so this part is a file upload rather than a migration.
People and access
A project is one client. Team members hold one of four roles: owner, admin, member or viewer. Access is set up here rather than read from whatever your previous tool had configured.
Four steps, with a preview before the last one.
Nothing is written until the mapping is confirmed. The order exists so a bad file is caught on screen rather than inside a live campaign.
- 01
Export
Take the contacts out of your current tool, database or spreadsheet as a CSV with a header row. Bring only the people you still intend to contact. A migration is a good moment to drop the rows you have been carrying for no reason.
- 02
Upload the CSV
One file, up to 20,000 rows, into the project that represents that client. Leads are scoped to the project from the moment they arrive, so nothing lands in a pool shared with another client.
- 03
Map and preview
Columns are matched automatically and shown back to you. Correct anything the matcher got wrong and read the rows on screen. This is the step where a bad file is meant to be caught.
- 04
Import
Duplicates are removed and the leads land in the project pool. Nothing starts on its own afterwards: the pipeline waits until you point it at a campaign and start it yourself.
What does not come across
A migration page that lists only the parts that work is a sales page. These six are the parts that cost time. Read them before you export anything.
No sending history or statistics
Open rates, reply rates and past sends stay in the tool that recorded them. Reporting here starts at the first campaign you run here, which makes early numbers thin rather than flattering.
No sequence or template import
Sequences and templates are not carried across from another tool. You rewrite them in MyLeadTeam. That is more work on the first day and less on every day after, because the copy is then written against the approval gate the rest of the pipeline uses.
No mailbox reputation transfer
Reputation belongs to your domain, not to a platform. Even so, warmup restarts its ramp for every mailbox newly connected here, because MyLeadTeam has no record of what that mailbox was doing elsewhere.
No two-way CRM sync
There is no CRM integration in either direction. A lead that changes here does not change in your CRM, and a record that changes in your CRM does not change here.
No connector to your old tool
There is no ready-made connection to Instantly, Smartlead or Apollo. The exchange goes through CSV, which is slower to set up and far easier to inspect before it reaches a campaign.
No one-click undo
Nothing reverses an import in a single click. Deduplication limits the most common accident, but the plan for an import belongs before the upload rather than after it.
Before you export a single row.
Get started
Move one list across, and see what it costs.
Start with a single client, one CSV and one mailbox. The parts that do not migrate are all on this page, so nothing about the first week should be a surprise.
No payment method or recurring charge during early access.