Importing your data

Rizer CRM allows you to import data from external sources, making it easy to migrate your existing customer and business information into the system. This guide will walk you through the process of preparing and importing your data using a CSV (Comma-Separated Values) file.

To import your data into Rizer CRM:

1. Log in to your Rizer CRM account.
2. Navigate to the Import section inside Settings.
3. Download the empty CSV example file
4. Follow the examples and add your data accordingly
5. Review the data and ensure everything is correct.
6. Click “Import” to begin the Import process.
7. Wait for the import to complete. Rizer CRM will provide a summary of the imported records and any errors encountered.

Best Practices

• Always back up your existing CRM data before performing an import.
• Start with a small test import to ensure your file is formatted correctly.
• After import, review a sample of the imported data to ensure accuracy.

Preparing Your Import File

Rizer CRM accepts CSV files for data import. Here’s what you need to know about the file format:

• The first row should contain column headers that match the field names in Rizer CRM.
• Each subsequent row represents a single record (e.g., a company or a contact).
• Fields are separated by commas.
• If a field contains a comma, enclose the entire field in double quotes.

Supported Fields

Rizer CRM supports a wide range of fields for both entities (companies) and contacts. Here’s a breakdown of the supported fields:

Entity (Company) Fields

• entity.name: Company name
• entity.bound: Inbound or Outbound classification
• entity.website: Company website URL
• entity.country_code: Two-letter country code – Full list here: https://en.wikipedia.org/wiki/ISO_3166-2
• entity.language_code: Two-letter language code – Full list here: https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes
• entity.state: State or province – Only needed for US based addresses – Full list here: https://en.wikipedia.org/wiki/List_of_U.S._state_and_territory_abbreviations
• entity.postal_code: Postal or ZIP code
• entity.city: City name
• entity.street_number: Street number
• entity.street_name: Street name
• entity.floor: Floor number
• entity.room_number: Room or suite number
• entity.timezone: Timezone (e.g., “America/New_York”) – Full list here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
• entity.activity_type: Type of business activity from the Rizer predefined list – contact support@rizer.io for more details

Entity Contact Methods

• entity.contact_methods.calling.mobile_work.phone_country_code.1: Country code for work mobile
• entity.contact_methods.calling.mobile_work.phone_number.1: Work mobile number
• entity.contact_methods.calling.landline_work.phone_country_code.1: Country code for work landline
• entity.contact_methods.calling.landline_work.phone_number.1: Work landline number
• entity.contact_methods.calling.skype.skype.1: Skype username
• entity.contact_methods.messaging.email_work.email.1: Work email address
• entity.contact_methods.messaging.fax_work.phone_country_code.1: Country code for work fax
• entity.contact_methods.messaging.fax_work.phone_number.1: Work fax number

Contact Fields

For each contact (up to 2 in the CSV example), the following fields are supported:

• contact.{n}.language_code: Contact’s preferred language – Allows for a two-letter language code – Full list here: https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes
• contact.{n}.timezone: Contact’s timezone (e.g., “America/New_York”) – Full list here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
• contact.{n}.first_name: First name
• contact.{n}.last_name: Last name
• contact.{n}.job_title: Job title
• contact.{n}.social_facebook: Facebook profile URL
• contact.{n}.social_twitter: Twitter profile URL
• contact.{n}.social_linkedin: LinkedIn profile URL

Contact Methods

• contact.{n}.contact_methods.calling.mobile_work.phone_country_code.1: Country code for work mobile
• contact.{n}.contact_methods.calling.mobile_work.phone_number.1: Work mobile number
• contact.{n}.contact_methods.calling.landline_work.phone_country_code.1: Country code for work landline
• contact.{n}.contact_methods.calling.landline_work.phone_number.1: Work landline number
• contact.{n}.contact_methods.calling.mobile_personal.phone_country_code.1: Country code for personal mobile
• contact.{n}.contact_methods.calling.mobile_personal.phone_number.1: Personal mobile number
• contact.{n}.contact_methods.calling.landline_personal.phone_country_code.1: Country code for personal landline
• contact.{n}.contact_methods.calling.landline_personal.phone_number.1: Personal landline number
• contact.{n}.contact_methods.calling.skype.skype.1: Skype username
• contact.{n}.contact_methods.messaging.email_work.email.1: Work email address
• contact.{n}.contact_methods.messaging.email_personal.email.1: Personal email address
• contact.{n}.contact_methods.messaging.fax_work.phone_country_code.1: Country code for work fax
• contact.{n}.contact_methods.messaging.fax_work.phone_number.1: Work fax number
• contact.{n}.contact_methods.messaging.fax_personal.phone_country_code.1: Country code for personal fax
• contact.{n}.contact_methods.messaging.fax_personal.phone_number.1: Personal fax number

Note: You can replace {n} with the contact number (e.g., 1, 2, etc.) and add more than just one contact person.

Troubleshooting

If you encounter issues during the import process:

• Check that your CSV file is properly formatted and all required fields are included.
• Ensure that date fields are in the correct format (typically YYYY-MM-DD).
• Verify that phone numbers include the country code and are in the correct format.
• Look for any special characters or formatting that might cause issues, especially in text fields.
• Check if contry or language codes are correct
• Make sure you are using the correct inbound or outbound terminology

In case of errors, Rizer CRM will notify you of a failed import and suggest possible solutions. After you fix the problems you can retry the import.