Table of contents
- Key benefits of preparing your CSV file
- What is a CSV file format?
- Structuring your file
- 1. Example of CSV format
- 2. Mandatory fields
- 3. Field formatting
- 4. Supported file type and size
- 5. Mandatory and optional fields for the import
- 6. Formatting guidelines by field type
- List of countries supported in CSV imports
- Supported time zones
- Frequently asked questions (FAQ)
Key benefits of preparing your CSV file
This article will help you format your CSV file correctly before importing it into Futuria CRM. By following this guide, you will avoid the common import errors, save time and make sure your data transfers smoothly into your CRM.
Taking the time to format the CSV file properly before importing makes sure your contact data is clean, complete and accurately mapped.
- Reduces the chance of import errors or failed uploads.
- Helps Futuria CRM map the fields automatically during the import.
- Enables contact deduplication and accurate updates.
- Supports custom fields and advanced segmentation.
- Saves time by avoiding data cleaning after the import.
- Increases the success rate of bulk uploads of contacts and opportunities.
What is a CSV file format?
CSV stands for "Comma-Separated Values". It is a simple file format used to store tabular data, such as spreadsheets or databases.
Each row in a CSV file represents a single record, and the fields within the record are separated by commas. It is one of the most widely used formats for importing and exporting data between different systems.
- CSV files typically have a
.csvextension. - You can create or edit them with tools such as Excel, Google Sheets or Notepad.
- Make sure the file contains only one worksheet to avoid import issues.
Example:
| First name | Last name | Phone | |
|---|---|---|---|
| Jane | Doe | +11234567890 | |
| John | Smith | +10987654321 |
Structuring your file
To guarantee accurate data mapping, structure your CSV file with column headers that match the standard or custom fields in Futuria CRM.
1. Example of CSV format
| First name | Last name | Phone | Company | Tags | Status | Created date | Additional phone | |
|---|---|---|---|---|---|---|---|---|
| John | Doe | +11234567890 | ABC Corp | VIP, Lead | New | 01/01/2024 | +17877123462 | |
| Jane | Smith | +15556667777 | XYZ Ltd | Customer | Active | 02/02/2024 | +17877123464 |
- Each row represents a single contact or opportunity.
- Each column represents a distinct property.
- The header row is mandatory in order to map the fields correctly.
2. Mandatory fields
To create or update a contact, at least one of the following fields is required:
- First name
- Email address
- Phone number
Note: to update contacts, you need a unique identifier (contact ID, email or phone) depending on your deduplication settings. For opportunities, include the opportunity ID if you are updating. Without it, a new one will be created.
3. Field formatting
Follow these specific formatting rules to avoid errors during the import:
| Field type | Accepted formats / Notes |
| Date picker (date fields) | DD/MM/YYYY, YYYY/MM/DD, DD-MM-YYYY, YYYY-MM-DD |
| Multiple selection / Checkbox | Commas: VIP, Lead, Semicolons: Gold; Silver, Full stops: Yes. No ❌ Slashes are not valid |
| Single option (drop-down menu) | One value only. Example: Blue |
| Contact owner | First name Last name — e.g. Logan Paul |
| Tags | Commas, semicolons or full stops. e.g. Blue, Yellow, Blue; Yellow |
| Phone number | E.164: +11234567890 (recommended); also 123-456-7890, (123) 456-7890 (US only) |
| Invalid phone formats | 1234567, abc1234567 |
| Number fields | 1.23, 1234, .123 |
| Currency fields | 1234, 1,234,234.33 |
| Contact followers | First name Last name, First name2 Last name2 — e.g. Adam Smith, David Lee |
| Additional emails | abc@email.com, abc1@email.com |
| Additional phone numbers | +1 7877123460, +1 7877123461 |
4. Supported file type and size
Your file has to meet a few basic requirements for a successful upload.
| Requirement | Details |
|---|---|
| File format | .csv only |
| Sheets allowed | One sheet per file |
| Maximum file size | 30 MB |
5. Mandatory and optional fields for the import
Including the right fields helps Futuria CRM identify and process your records accurately.
| Import action | Mandatory/optional fields | Notes |
| New contact | First name or Email, or Phone | At least one is mandatory |
| Update an existing contact | Contact ID or First name/Email/Phone | Depends on your duplication settings |
| Header row | Mandatory | Headers must match existing or custom fields in Futuria CRM |
6. Formatting guidelines by field type
To prevent import errors, follow these formatting rules for each data type in your CSV.
| Field type | Format | Example | Notes |
| Phone number | E.164 or standard US formats | +1 1234567890123-456-7890 |
Clean, consistent formatting |
| Email address | Standard format | name@example.com |
Must include @ and a domain |
| Date | Several formats accepted | 16/04/2025, 2025-04-16 |
Choose one format and stick to it |
| Multiple selection fields | Separate with ,, ;, or . |
Blue, Yellow, Green |
Must match the field options in the CRM |
| Additional emails | Comma separated | email1@example.com, email2@example.com |
Add in a separate column |
| Additional phones | Comma separated | 1234567890, 9876543210 |
Add in a separate column |
Tip: before importing your CSV, make sure the custom fields have already been created in your Futuria CRM account using the same labels and data types. For help on creating custom fields, see the overview of merge fields and custom values.
List of countries supported in CSV imports
This section contains a table of the country names accepted during CSV imports into Futuria CRM. These are the official country values to use in your CSV file when mapping a country field, whether standard or custom.
Use the exact country names or short codes listed below in your CSV file.
- Purpose: Futuria CRM validates country names during the import. If your CSV includes a
Countryfield, every row must match one of the exact names in this list. - Format: it must match exactly, respecting capitalisation and spelling. For example,
United Statesis accepted, butUSAorU.S.will cause an error. - Use with custom fields: if you are using a custom country field, you can still benefit from sticking to this list to maintain compatibility.
| Country name (Code) | Country name (Code) | Country name (Code) |
| Afghanistan (AF) | Albania (AL) | Algeria (DZ) |
| Andorra (AD) | Angola (AO) | Antigua and Barbuda (AG) |
| Argentina (AR) | Armenia (AM) | Australia (AU) |
| Austria (AT) | Azerbaijan (AZ) | Bahamas (BS) |
| Bahrain (BH) | Bangladesh (BD) | Barbados (BB) |
| Belarus (BY) | Belgium (BE) | Belize (BZ) |
| Benin (BJ) | Bhutan (BT) | Bolivia (BO) |
| Bosnia and Herzegovina (BA) | Botswana (BW) | Brazil (BR) |
| Brunei (BN) | Bulgaria (BG) | Burkina Faso (BF) |
| Burundi (BI) | Cabo Verde (CV) | Cambodia (KH) |
| Cameroon (CM) | Canada (CA) | Central African Republic (CF) |
| Chad (TD) | Chile (CL) | China (CN) |
| Colombia (CO) | Comoros (KM) | Congo (CG) |
| Congo (Kinshasa) (CD) | Costa Rica (CR) | Croatia (HR) |
| Cuba (CU) | Cyprus (CY) | Czech Republic (CZ) |
| Denmark (DK) | Djibouti (DJ) | Dominica (DM) |
| Dominican Republic (DO) | East Timor (TL) | Ecuador (EC) |
| Egypt (EG) | El Salvador (SV) | Equatorial Guinea (GQ) |
| Eritrea (ER) | Estonia (EE) | Eswatini (SZ) |
| Ethiopia (ET) | Fiji (FJ) | Finland (FI) |
| France (FR) | Gabon (GA) | Gambia (GM) |
| Georgia (GE) | Germany (DE) | Ghana (GH) |
| Greece (GR) | Grenada (GD) | Guatemala (GT) |
| Guinea (GN) | Guinea-Bissau (GW) | Guyana (GY) |
| Haiti (HT) | Honduras (HN) | Hungary (HU) |
| Iceland (IS) | India (IN) | Indonesia (ID) |
| Iran (IR) | Iraq (IQ) | Ireland (IE) |
| Israel (IL) | Italy (IT) | Jamaica (JM) |
| Japan (JP) | Jordan (JO) | Kazakhstan (KZ) |
| Kenya (KE) | Kiribati (KI) | Korea, North (KP) |
| Korea, South (KR) | Kosovo (XK) | Kuwait (KW) |
| Kyrgyzstan (KG) | Laos (LA) | Latvia (LV) |
| Lebanon (LB) | Lesotho (LS) | Liberia (LR) |
| Libya (LY) | Liechtenstein (LI) | Lithuania (LT) |
| Luxembourg (LU) | Madagascar (MG) | Malawi (MW) |
| Malaysia (MY) | Maldives (MV) | Mali (ML) |
| Malta (MT) | Marshall Islands (MH) | Mauritania (MR) |
| Mauritius (MU) | Mexico (MX) | Micronesia (FM) |
| Moldova (MD) | Monaco (MC) | Mongolia (MN) |
| Montenegro (ME) | Morocco (MA) | Mozambique (MZ) |
| Myanmar (MM) | Namibia (NA) | Nauru (NR) |
| Nepal (NP) | Netherlands (NL) | New Zealand (NZ) |
| Nicaragua (NI) | Niger (NE) | Nigeria (NG) |
| North Macedonia (MK) | Norway (NO) | Oman (OM) |
| Pakistan (PK) | Palau (PW) | Panama (PA) |
| Papua New Guinea (PG) | Paraguay (PY) | Peru (PE) |
| Philippines (PH) | Poland (PL) | Portugal (PT) |
| Qatar (QA) | Romania (RO) | Russia (RU) |
| Rwanda (RW) | Saint Kitts and Nevis (KN) | Saint Lucia (LC) |
| Saint Vincent and the Grenadines (VC) | Samoa (WS) | San Marino (SM) |
| Sao Tome and Principe (ST) | Saudi Arabia (SA) | Senegal (SN) |
| Serbia (RS) | Seychelles (SC) | Sierra Leone (SL) |
| Singapore (SG) | Slovakia (SK) | Slovenia (SI) |
| Solomon Islands (SB) | Somalia (SO) | South Africa (ZA) |
| South Sudan (SS) | Spain (ES) | Sri Lanka (LK) |
| Sudan (SD) | Suriname (SR) | Sweden (SE) |
| Switzerland (CH) | Syria (SY) | Taiwan (TW) |
| Tajikistan (TJ) | Tanzania (TZ) | Thailand (TH) |
| Togo (TG) | Tonga (TO) | Trinidad and Tobago (TT) |
| Tunisia (TN) | Turkey (TR) | Turkmenistan (TM) |
| Tuvalu (TV) | Uganda (UG) | Ukraine (UA) |
| United Arab Emirates (AE) | United Kingdom (GB) | United States (US) |
| Uruguay (UY) | Uzbekistan (UZ) | Vanuatu (VU) |
| Vatican City (VA) | Venezuela (VE) | Vietnam (VN) |
| Yemen (YE) | Zambia (ZM) | Zimbabwe (ZW) |
Supported time zones
Use one of the following time zone formats in your CSV. They are case sensitive and must match exactly.
| Time zone | Time zone | Time zone |
| Etc/GMT+12 | Pacific/Midway | Pacific/Honolulu |
| America/Juneau | US/Alaska | America/Dawson |
| America/Los_Angeles | America/Phoenix | America/Tijuana |
| US/Arizona | America/Belize | America/Boise |
| America/Chihuahua | America/Denver | America/Edmonton |
| America/Guatemala | America/Managua | America/Regina |
| Canada/Saskatchewan | US/Mountain | America/Bahia_Banderas |
| America/Bogota | America/Cancun | America/Chicago |
| America/Mexico City | US/Central | America/Caracas |
| America/Detroit | America/Indiana/Indianapolis | America/Louisville |
| America/Manaus | America/New_York | America/Santiago |
| America/Santo_Domingo | America/Toronto | US/East-Indiana |
| US/Eastern | America/Argentina/Buenos_Aires | America/Glace_Bay |
| America/Montevideo | America/Sao_Paulo | Canada/Atlantic |
| America/St_Johns | Canada/Newfoundland | America/Godthab |
| America/Noronha | Etc/GMT+2 | Atlantic/Cape_Verde |
| Atlantic/Azores | UTC | Africa/Algiers |
| Africa/Casablanca | Africa/Lagos | Atlantic/Canary |
| Europe/London | Africa/Cairo | Africa/Harare |
| Europe/Amsterdam | Europe/Belgrade | Europe/Brussels |
| Europe/Madrid | Europe/Oslo | Europe/Sarajevo |
| Africa/Nairobi | Asia/Amman | Asia/Baghdad |
| Asia/Jerusalem | Asia/Kuwait | Asia/Qatar |
| Europe/Athens | Europe/Bucharest | Europe/Helsinki |
| Europe/Moscow | Asia/Baku | Asia/Dubai |
| Asia/Kabul | Asia/Tehran | Asia/Karachi |
| Asia/Yekaterinburg | Asia/Colombo | Asia/Kolkata |
| Asia/Calcutta | Asia/Kathmandu | Asia/Almaty |
| Asia/Dhaka | Asia/Rangoon | Asia/Bangkok |
| Asia/Krasnoyarsk | Asia/Irkutsk | Asia/Kuala_Lumpur |
| Asia/Shanghai | Asia/Taipei | Australia/Perth |
| Asia/Seoul | Asia/Tokyo | Asia/Yakutsk |
| Australia/Adelaide | Australia/Darwin | Asia/Vladivostok |
| Australia/Brisbane | Australia/Canberra | Australia/Hobart |
| Australia/Sydney | Pacific/Guam | Asia/Magadan |
| Pacific/Auckland | Pacific/Fiji | Pacific/Tongatapu |
Frequently asked questions (FAQ)
Can I import contacts with more than one phone number or email?
Yes! Use separate columns such as Additional phone numbers and Additional email addresses, and separate the entries with a comma.
What happens if I include a field in the CSV that does not exist in Futuria CRM?
That field will be ignored, unless you map it to an existing standard or custom field during the import process.
Will Futuria CRM detect duplicates automatically?
Yes, depending on your duplicate detection settings, it can match on contact ID, phone or email and merge or skip the duplicates.
Can I update contacts with a CSV import?
Absolutely. Just make sure you include a field used for duplicate matching (such as contact ID, email or phone).
Do I need to clean up empty rows and columns?
Yes. It is best to remove any unnecessary data to avoid unexpected behaviour during the import.


