Source
List ownership, import & exit — found from sitemap — Omnisend
Checked for Omnisend on 16 Nov 2026
- Page
- http://support.omnisend.com/en/articles/3838659-import-contacts-from-a-file
- Checked
- 16 Nov 2026, 14:03 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:d5eba7d4b71cf2b811cdae7bfee8e21652baa1ef644e868b06ddaf755e26631c
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Import file formats Report an error
“The file must be in .csv, .xls, .xlsx, or .ods format and contain only one sheet.”
-
Import max properties Report an error
“A single file can contain up to 200 contact properties, with each column representing one property. For more, split your data into multiple files.”
-
Import required identifier Report an error
“Each contact must include either an email address or a phone number.”
-
Import paste limit Report an error
“Go to Audience → Contacts → Add or update contacts → Paste contact details to type or paste contact information directly – no file required. You can add up to 500 contacts this way.”
-
Import default properties Report an error
“Personal data: Email address, Phone number, First name, Last name, Birthdate, Gender. Address: City, State/Province/Region, Country, Country code, Postal/Zip code. Opt-in status: Email opt-in date, Email opt-out date, SMS opt-in date, SMS opt-out date.”
-
Import custom properties Report an error
“You can either select an existing custom property or click Create New to add a new property.”
-
Import custom property naming rules Report an error
“Only Latin characters, numbers, and the underscore (_) are allowed Maximum length is 128 characters Names are case-sensitive”
-
Import automation trigger note Report an error
“If your file includes both email address and phone number, it’s best to map them as default properties, not custom ones. If mapped as custom properties, they will not trigger automation workflows.”
-
Import auto tags Report an error
“When you import contacts, Omnisend automatically adds two tags: source: manual import imported from a file on DD/MM/YY HH:MM:SS”
-
Import segment creation Report an error
“you can also create a segment immediately based on: Import date and time: The segment will be named Contacts imported via <manual_import_type> on <date_of_import>. Custom name: The segment will appear under Audience → Segments with the name you choose.”
-
Import duplicate handling Report an error
“Update subscription status and contacts’ properties (Recommended): This option updates both the subscription status and any mapped contact properties in the import file. Update contacts’ properties only: This updates only the mapped contact details (e.g., name, phone number, etc.) but keeps the existing subscription status unchanged. Update subscription status only: This updates the subscription status while keeping all other contact details as they are. Do nothing: This option prevents any changes to existing contacts. Only new contacts will be imported.”
-
Import empty field overwrite Report an error
“If enabled, any fields left blank in the import file will clear the corresponding existing values for the contact. If disabled (default), existing values remain unchanged even if the import file has blank fields.”
-
Import report Report an error
“Click View to see the detailed report which shows the number of new and existing contacts added and the number of good/bad emails/phone numbers found.”
-
Import non subscribed option Report an error
“If either of the checkboxes is left unchecked, contacts will be imported as non-subscribed.”
-
Import duplicate email phone skip Report an error
“If you are importing contacts with both an email and a phone number, any duplicate in either field will cause that contact to be skipped.”
-
No duplicate contacts Report an error
“Yes. Omnisend doesn't create duplicate contacts. When you import a file with contacts that already exist (matching email or phone number), the system updates their information instead.”
-
Store sync vs import Report an error
“Store sync automatically and continuously syncs contacts acquired through your store from orders, cart activity, account registrations, etc. On the other hand, file import is a manual, one-time upload for historical data, migrations from other platforms, or bulk updates to existing contacts.”
-
Address single field Report an error
“Omnisend only supports one Address field. If your file includes separate Address 1 and Address 2 values, combine them into a single comma-separated string: Address 1, Address 2.”
-
Import timestamp format Report an error
“Use ISO 8601 format for dates and times (e.g., 2020-02-29T14:23Z). Dates without a time default to 12:00 PM. Future-dated opt-in or opt-out timestamps won’t be saved.”
-
Import opt out status rule Report an error
“If you map an opt-out date that is later than the opt-in date, the contact will be imported with an unsubscribed status.”
-
Import utf8 encoding Report an error
“If non-Latin characters display incorrectly, save the .csv file in UTF-8 format and upload your contacts again.”
-
Migration guides Report an error
“Import Mailchimp Contacts to Omnisend Export Contacts to a File Migrate from Active Campaign to Omnisend Import Klaviyo Contacts & Segments to Omnisend Migrate from Yotpo to Omnisend”
-
Export contacts Report an error
“Export Contacts to a File”
Scores citing this record
- The CRM Manager List ownership, import & exit
- The Data Protection Officer List ownership, import & exit
- The Shop Owner Integrations & API
- The Integrator List ownership, import & exit
- The Skeptic List ownership, import & exit