Bulk upload

Importing your sphere from a spreadsheet, the four-step wizard, what it accepts, and the 2,000-record limit.

Bulk upload brings your contacts in from wherever they live now. It is built to accept messy data and fix it, rather than reject the file and make you clean it up.

UploadCSV or ExcelMap columnsauto-detectedReview fixesnothing to doConfirmtag and importStep 3 fixes your data for you, it is a review, not a chore.
Four steps. Step 3 is a review of fixes already made, not a list of chores.

#Step 1, upload

Bulk Upload Contacts

Import contacts from a CSV or Excel file.

Import HistoryClose
Step 1 of 4
1Upload2Map Columns3Review & Fix4Confirm & Import
Contact source
Google ContactsApple ContactsOutlook / MicrosoftActiveCampaignCustom CSV
Drag & drop your file hereorChoose File

Supported: CSV (.csv), Excel (.xlsx, .xls), max 2,000 records

Accepted
File typesCSV (.csv) and Excel (.xlsx, .xls)
Contact sourceGoogle Contacts, Apple Contacts, Outlook / Microsoft, ActiveCampaign, or a custom CSV
SizeUp to 2,000 records per file
Choose the right source

Telling it the file came from Google or Outlook lets it apply the right column-detection rules for that export format. Pick Custom CSV only if none of them apply.

#Known bounces are flagged

Every address in your file is checked against the EasyDigz bounce list, and a message shows the result straight away, for example "45 known bounces found, they will not be emailed." Those contacts are still added to Accounts, but they are never emailed. If you have a newer address for any of them, update it on their account. See Bounces and unsubscribes.

Over 2,000 rows, the rest is left behind

A larger file is not rejected, the first 2,000 records are processed and you are told how many the file contained. Split the file yourself if you need all of them, or nothing beyond row 2,000 arrives.

#Step 2, map columns

EasyDigz reads your headers and matches them to its own fields. Review and adjust. See Mapping your columns.

#Step 3, review fixes

Data problems are corrected automatically and shown to you as a summary. Nothing to do unless you disagree. Rows missing an email, a phone, or both are flagged here too, No email or Cannot be contacted, never filled in with made-up details. You can type a missing email or phone straight into the cell before importing. See What the importer fixes for you.

If your file had no issues at all, this step is skipped entirely.

#Potential matches

If a row looks like it could already exist in your Accounts, the Potential Matches panel opens automatically before you can continue. Each candidate is scored and labelled Definitive or Review: Definitive means an identifier (email or phone) and a compatible name both matched, and is safe to merge on sight; Review means only one of those matched, and needs your own side-by-side check of name, email, phone and address before you decide.

ChoiceWhat it does
MergeOnly the fields present in your uploaded row overwrite the existing account, a blank field in your file leaves the existing value untouched. If the existing contact already has different tags, you choose what happens to them, below
SkipLeaves the existing account untouched and does not import the row as a new one
Do not approve a Review match on name alone

A matching surname is not enough by itself, check the email and phone too before merging.

#Tags when contacts merge

Previously, merging dropped a contact's existing tags without warning. Now, if the contacts being merged already have different tags, you are asked first, including when you use Merge All.

ChoiceWhat happens
Keep both (recommended)Existing tags stay and the new tags are added
Keep new tags onlyExisting tags are replaced by the tags chosen for this upload
Keep previous tags onlyExisting tags stay; the new tags are not added
Keep both, but remove some tagsPick tags to take off these contacts

Each option shows a before-and-after preview. You are warned if a tag being removed is used by a scheduled email or trigger. One answer applies to every contact in the prompt, there is no prompt if only one side has tags, Lead is always kept, and the import history records your choice.

#Step 4, confirm and import

  1. 1

    In Assign tags to these contacts, pick or create the tags for this import.

    Open the dropdown, search your tags, or type a new name to create one. Lead is always applied and locked, so every contact gets Lead plus whatever you pick, for example Lead + Buyer. Give every import its own specific tag as well, it is your only reliable way to find or undo that batch later, see Import history.

  2. 2

    Preview the list one last time.

    Details are grouped into Name, Contact, Address and Business columns, one row per contact. The header stays put as you scroll, you can page through and choose how many rows to show, and anything fixed or trimmed is shown in red with a short label.

  3. 3

    Click Import Now.

#It runs in the background

You can close the window and carry on working. A progress bar stays visible as you move around, and you get a notification with a summary, imported, skipped, merged, when it finishes.

New contacts show as Subscribed unless they opted out before.

#Fixing an upload afterwards

Uploaded the wrong file, or forgot the tags? In Import history, Undo upload removes the contacts that upload created, and Manage tags adds or removes tags on its contacts, no support request needed.

#For the cleanest import

  • A full name, a valid email and a properly formatted phone number for every row. A row missing either one still imports, flagged, but that contact cannot be emailed or called until you add it.
  • Unique email addresses within the file.
  • Files split to 2,000 rows or fewer.
  • A combined name column is fine, it is split into first and last name, but check the preview for unusual names.
  • Even messy data will import, the fixes exist for exactly that, but the less it has to guess, the better the result.
  • Send your first campaign to a small part of a new list before sending to all of it. Only known bounces are caught on upload.

Last updated 30 October 2026