SendTo's list importer takes the slowest part of onboarding a client, turning their spreadsheet into a list you can actually send to, and gets it done in a few minutes. Day to day, you upload the file, check the mapping it suggests and get on with the campaign. It suits agencies and freelancers who take on small business clients whose contacts sit in spreadsheets, especially if you're onboarding someone new every month.
We make SendTo, so this sendto list import review is us testing our own tool. We ran three client lists through it, a florist's till export, a gym's member export and a trades firm's office spreadsheet, and we've written down what happened on screen. The mechanics get full credit. We're just as clear about the one thing no importer can do. It can't tell you whether the people on that spreadsheet ever agreed to hear from your client.
Below you'll find how the column mapping behaved, what happened when we cut the connection halfway through a big upload, why platform-wide suppression matters more to your other clients than to this one, and what happens to a list once it's in. If you searched for the Send To option on your computer's right-click menu, this page isn't about that. It reviews the contact importer in an email marketing platform.
Automatic column mapping gets the common fields right first time and leaves the odd ones for you to confirm
Mapping comes first because it decides whether onboarding takes five minutes or an evening. When you upload a file, SendTo reads the header row and suggests which field each column belongs to. You see the suggestions before anything is saved, and you can change any of them.
The florist's file came out of a till system with 1,840 rows and headers like "Email Address", "First Name", "Surname" and "Mobile". All four matched on the first pass. The gym's export had 12,600 rows with "email", "firstname", "lastname" and "phone_number" in lower case, and those matched straight away too. The trades firm was the messy one. An office manager had kept the sheet by hand for six years, so it had 640 rows under headers like "Name", "Contact", "Notes" and "Job date". The importer matched nothing it wasn't sure of, and asked us to decide.
We think that's the right behaviour. A wrong guess on "Contact" (is it an email, a phone number or the name of the person at a company?) is worse than no guess. The importer left those columns for a person to confirm, which took about a minute.
There are two obvious alternatives. The first is cleaning the file by hand in a spreadsheet before upload, renaming every header, deleting junk columns and saving a fresh copy. It works, but on the gym's file that's twenty minutes of fiddling before you've done anything useful for the client. The second is an importer that makes you match every column yourself from a dropdown, even the obvious ones. That's fine on a five-column file and tedious on a twenty-column one. The real point of this sendto list import review is that you only spend attention on the columns that need it.
Where the mapping needed a human: merged names, custom fields and date columns
Mapping reads headers, not meaning. Three things on our test lists showed where that line sits.
- Merged names. The trades firm's "Name" column held full names like "Dave Hughes" and, in a few rows, "Mr & Mrs Patel". The importer doesn't split one column into first and last names. If you map it to first name, your greeting reads "Hi Dave Hughes". We split the column in the spreadsheet first.
- Custom fields. The florist had "Fav flowers" and "Anniversary". Neither is a standard field, so we created custom fields for both. Only the client knew whether "Anniversary" was a wedding date or the date of a first order, and the answer changes what campaign you'd send.
- Date columns. The trades firm's "Job date" mixed 03/04/2022 with 2022-04-03 and the occasional "spring 22". A header tells the importer it's a date. It doesn't tell it which date someone meant.
Resumed uploads mean a dropped connection on a large list costs you nothing
We tested this the unkind way. We took the gym's 12,600-row export to a café with poor wifi, started the upload, and turned the laptop's wifi off about a third of the way through. When we reconnected, the upload picked up from where it had stopped and finished. It didn't start again from zero, and we didn't have to choose the file a second time.
That sounds small until you're the person it happens to. Picture a client call where you're sharing your screen and showing the gym owner their members going into the platform. The office wifi drops, or someone on the shared connection starts a video upload. With an importer that starts over, you either sit through the whole thing again with the client watching, or you promise to sort it later and lose the moment.
The old workaround is splitting a big file into chunks by hand, say four files of 3,000 rows each, so that no single upload runs long enough to time out. It works, but it gives you four chances to skip a row or upload the same chunk twice. With resumed uploads you send the whole file once and leave it alone.
To be exact about the claim, interrupted uploads resume. That's what we tested and what the platform does. It won't fix a file that's corrupted before it leaves your laptop, so if a client sends you an export that won't open in a spreadsheet, get a fresh export first.
Platform-wide suppression is the feature that protects your other clients, not just this one
Once an address has unsubscribed, bounced or complained, SendTo holds it back across the whole platform. If a client re-imports an old list with that address on it, the importer won't add it back as someone you can mail. The person already said no, or the address doesn't exist, and that stays true whichever spreadsheet it turns up in.
For an agency that's the important bit. Your clients share your sending reputation. The trades firm's old spreadsheet included addresses that had bounced when the florist mailed them months earlier, because the same people were customers of both. Without platform-wide suppression, one client's stale list damages the inbox placement of every other client you run. With it, an address that's been lost once stays lost. That fits with how SendTo spreads volume, which we cover in how multi-domain distribution shields client reputation. This year's bulk sender rules from the big mailbox providers expect spam complaints to stay under 0.3%, so mailing people who already complained is the last thing you want.
Suppression only knows what has happened on SendTo. If your client unsubscribed people at their old provider, those opt-outs don't travel with a plain contact export. Ask the client for the old provider's unsubscribe list and take those people out of the file before you upload.
That's the trade-off, and it's real. Clients like big numbers. A shop owner who has paid for a newsletter service for three years doesn't enjoy hearing that a few hundred of their contacts won't be mailed. We'd still rather explain that once than explain a blocked domain later.
What happens after import, verification and segments, finishes the job the importer starts
Getting the list in is step one. Before the first campaign goes out, SendTo verifies the imported addresses, so mistyped domains and dead mailboxes are caught before they bounce. If the client's sending domain is new, automated warmup starts its volume low and raises it over time, so a fresh domain doesn't suddenly push 12,600 emails on day one. We've written separately about whether automated list verification is necessary before agency campaigns, so we won't repeat that here.
Once a few campaigns have gone out, you can segment the imported list by behaviour. You can build a segment of people who clicked, people who opened but didn't click, and people who haven't opened at all. On the gym's list that gave us a clear next step after the first two sends. Clickers got the class timetable, openers who hadn't clicked got a shorter reminder, and non-openers got a single re-engagement email before we stopped mailing them.
That gap is the one software can't close. Mapping, resumed uploads, suppression and verification all deal with the mechanics of a list. Whether the people on it said yes is a question for your client, and we'd ask it before you even open the file.
Consent, field meaning and list age are still yours to check by hand
The importer takes any well-formed file you give it, and that's its job. It reads headers, maps columns, holds back suppressed addresses and resumes when the wifi drops. It has no way to know whether the florist's customers ticked a box at the till, or whether the trades firm's office manager typed in addresses from business cards picked up at a home show in 2018. That knowledge sits with your client, and the decision sits with you.
So, does importing a list make it GDPR compliant? No. An import moves contacts from one place to another. The consent either came with those people or it didn't, and no upload step changes that. We run the same four checks before every client import, and they take less time than the upload itself.
- Where each contact came from: Ask how each group of addresses was collected and whether consent was recorded at the time. A signup form with a timestamp is a record. A column of emails with no history is not. Under GDPR, you need to be able to show the basis for mailing someone, and the spreadsheet alone rarely shows it.
- Whether old purchase-only contacts need a re-permission email first: People who gave an email address only to get a receipt or a delivery update didn't sign up for a newsletter. Send them one plain email asking if they'd like to hear from the business, and mail only the ones who say yes.
- What each custom field actually means: "Anniversary", "Status" and "Notes" mean whatever the person who typed them meant. Ask before you build a segment or a merge field on them.
- How long since the list was last mailed: A list nobody has emailed for over a year carries more dead addresses, more forgotten signups and more people likely to hit the spam button. Mail the most recent contacts first and bring older ones in slowly.
Here's how that played out on our three lists. The florist's till had a marketing tick box at checkout, so 1,120 of the 1,763 importable contacts had a recorded yes and went straight into the first campaign. The other 643 had only ever got receipts, so they got one re-permission email. The trades firm's 640 rows had no consent record at all. Only the 230 people who had asked for a quote in the last two years got the re-permission email. We left the rest out, and the client agreed once we explained why. The "Notes" column settled it, because 41 rows said things like "do not contact" or "moved away". A header-reading importer would never pick those up.
If the client is unsure how to collect consent properly from now on, our piece on single opt-in versus double opt-in for GDPR-conscious small businesses sets out which method suits which kind of business. Point them to it before the next signup form goes live.
A five-minute pre-import conversation to have with every new client
We have this conversation on the onboarding call, before the file comes over. It's quicker than reading through a spreadsheet at 4pm on a Friday and guessing. These are the four questions we ask, word for word.
- "How did these people end up on your list, and did any of them tick a box saying yes to marketing?"
- "When did you last email this list, and what did you send?"
- "Is there anyone on here who has asked you to stop contacting them, here or at your old email provider?"
- "If I asked you what each column means, especially the ones you made up yourself, could you tell me?"
If the client can't answer the first question, send a re-permission email before any campaign. If the answer to the third is yes, get that unsubscribe export before you upload. Platform-wide suppression only knows what has happened on SendTo.
Once the list is in, fresh contacts should arrive through protected forms, not more spreadsheets
Importing is for the backlog. Once the florist's contacts were in, we didn't want a new spreadsheet from the till every month. New contacts should sign up themselves. SendTo's signup forms are protected against bots and embed on the client's website, or you can host them on a SendTo landing page if the site isn't ready. Double opt-in is optional, and you switch it on per form.
That changes how often you're importing at all. For the gym we put a form on the class timetable page and a hosted page behind a QR code at reception. New members joined the list in the platform with a timestamped signup, so there was nothing to map, nothing to resume and no consent question to chase later. The next time the gym's manager offered us an export, we said thanks and didn't need it. Our SendTo signup forms review covers how the bot protection and hosted pages held up in testing.
Price and plans: the importer comes with the platform, and you set what clients pay
The importer isn't an add-on. Mapping, resumed uploads and platform-wide suppression come with SendTo, alongside verification, warmup, segments, forms and the client portal. You don't pay per import or per mapped column.
The model works like this. As a partner, you pay SendTo a single flat platform fee. You then decide what each of your clients pays you each month, under your own brand and at your own prices. Clients buy their own sending usage on top of that subscription, so a gym mailing 12,600 members pays for its volume and a trades firm mailing 230 pays for far less. Your margin doesn't shrink when one client sends more.
We don't print prices in reviews because they change and articles don't. The current figures are on the SendTo pricing page.
Who should buy it and who should look elsewhere
This importer earns its place when you're onboarding several small business clients and each one arrives with a different spreadsheet. If you're an agency taking on a florist in March, a gym in April and a trades firm in May, the mapping saves you the hand-cleaning each time. Suppression keeps one client's old list from hurting the rest. Freelance marketers who keep being handed till exports and office spreadsheets get the same benefit at a smaller scale.
It also suits affiliates recommending a platform to agencies. Client onboarding is where an agency feels the work, and "columns map themselves and a dropped upload picks up where it stopped" is a sentence an agency owner understands straight away.
Look elsewhere if you're a single business with one clean list and no plans to resell email to anyone. You don't need a white-label platform, a client portal or partner billing. A simple single-business newsletter tool will do the job with less to set up. And if you have a handful of five-column files a year, hand-cleaning in a spreadsheet or an importer that makes you match every column yourself is perfectly fine.
Verdict
SendTo's list importer makes onboarding fast. On our three test lists, the common columns mapped on the first pass and the ambiguous ones waited for a person. A cut connection on a 12,600-row upload cost us nothing. Platform-wide suppression kept bounced and unsubscribed addresses from coming back through another client's file. For an agency sharing sending reputation across its clients, that last point protects the whole business and not just one list.
What's left is judgement, not software. Whether the people on the spreadsheet agreed to hear from your client, what "Anniversary" or "Notes" actually means, and whether a list nobody has mailed since 2021 should get a re-permission email first are your calls. Have the five-minute conversation, then let the importer do the rest.
If you know agencies who onboard small business clients every month, you can recommend SendTo to them and earn 20% of the partner subscription each one you refer pays SendTo, every month they keep paying. You don't get a share of what their own clients pay them. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal.
Join the SendTo affiliate programme


