Narrative 13: Import - Data mapping

Narrative 13: Import - Data mapping

Behind the scenes of a successful ticketing system: BTS Series

Narrative 13: Importing your data


When importing data into an application, it is crucial to prevent data loss or duplication. These types of errors can hinder the development of a clean and well-organized database, which is essential for effective data management and security.

Zoho Desk provides robust functionality for importing your data. The system intelligently automates the mapping of modules and fields to reduce the risk of data loss and maintain data integrity. Users have the advantage of verifying the field mappings in advance, thus adding an extra layer of security to the import process.

This capability is essential not only for clarity but also in mitigating the challenges associated with user adoption. For instance, clients can be accurately mapped to the "Contact name" field, while company names align with the "Account name" field to maintain an organized database, which helps ensure user trust in the system. 

Related knowledge base article: Importing data into Zoho Desk

Quote

Prerequisites

  1. Users can upload a .csv file or a .zip file containing multiple .csv files. 
  2. The .zip file must be named, for example, Contacts.zip, Accounts.zip, etc.

What are Identifier Fields?  

Identifier fields are fields used to find and match existing records when importing data into the product. They also help link related records, like connecting a contact’s name with their email address.

Each module supports different unique identifier fields for identification, as described in the table below:.  

Modules

Unique Identifier Fields

Accounts
​

Account ID

Account External ID

Account Name

Contacts

Contact ID

Contact External ID

Last Name

First Name

Email

Phone Number

Mobile

Tickets

Ticket ID

Ticket External ID

Ticket Number

Products

Product ID

Product External ID

Product Name

Tasks

TaskId

Task External ID

Calls

Call ID

Call External ID

Events

Event ID

Event External ID

Article Translation

Translation: External ID

Translation ID

Custom Modules

​

Record External ID

Custom Module Name

Quote

Points to remember: 

  1.  These fields help find matching records. 
  2.  If multiple records match the value, the first matching record will be selected automatically. 
  3. This can lead to unexpected matches or data being updated in the wrong record if you're not careful. 

Background:

  • Some users expressed a preference for matching Contacts by Last Name instead of Email, highlighting the importance of flexibility in their workflow. 
  • Other users approached matching through the use of a custom field, emphasizing the need for tailored solutions to fit their unique requirements. 
  • We also heard from many users who requested that the functionality be enhanced by updating existing records with the relevant entity's Zoho Desk ID to streamline their processes and improve data accuracy.

Working with the Identifier Field

When importing data into Zoho Desk, the Identifier Field is important because it helps identify existing records and avoid duplicate entries. 

Commonly used identifier fields

  • Find By is used to identify an existing record during the import process.
  • Map By is utilized to link a child record to a parent record, for instance, by linking a Contact to a Ticket.
You can now select specific fields for matching, providing enhanced control and customization during bulk processes or integrations. This functionality enables more precise data handling, ensuring that the information aligns with your specific requirements. By tailoring the matching criteria, you can streamline processes, enhance efficiency, and provide better outcomes for your team. This flexibility enables you to harness the full potential of your data.

Improvements in user experience 

Transparent process and status tracking 

We’ve implemented a straightforward, step-by-step process for data imports, complete with real-time status updates for each stage. This transparency enables users to monitor import progress and understand the current state of the process.

Unique identifiers for entity mapping 

New fields have been introduced to help users identify if a parent entity already exists when importing related child entities. For example, users can seamlessly map a contact to an existing account in Zoho Desk to streamline the import process while minimizing the risk of duplicate entries.

Enhanced error handling and log accessibility

We’ve made significant improvements in error handling by allowing users to download detailed error logs right from the history page in case of import failures. This enhancement provides users with greater insight into any issues and facilitates faster troubleshooting and resolution.

Support for custom modules

The import UI has been revamped to support custom modules, providing users with greater flexibility and customization options. This enables a more personalized and efficient data import experience.

Coming up soon

Custom unique fields

Identifying key data points, such as a Customer ID in the Contact Module, ensures that every customer has a distinct reference, which streamlines ticket management and resolution. By establishing these fields as identifiers, support agents can quickly access and update customer records, enhancing response times and accuracy.

External ID fields 

Integration with various systems often generates External ID fields, such as CRM ID, Invoice ID, and Bug ID. Utilizingthese fields as identifiers enables agents to cross-reference relevant records seamlessly. When records need to be updated or retrieved from different systems, these unique identifiers are crucial in maintaining data consistency across platforms.

Composite identifier fields

Often, relying solely on a single identifier may not be sufficient to pinpoint a customer accurately or a record.Implementing multiple fields as composite identifiers can enhance data integrity and accuracy. For example, considering both the Last Name and Email of a contact can significantly reduce errors in data retrieval and ensure that support inquiries are directed and resolved correctly.

Wrapping up

Using these features positions support teams to operate more effectively and improve overall customer interactions. For instance, a large corporation merging client data from multiple legacy systems into Zoho Desk modules will benefit significantly from automatic field mapping to ensure that contact and account names are accurately aligned. This attention to detail not only improves the user experience but also enhances overall data integrity during the merging process.


Please stay tuned for more in the Desk behind-the-scenes series.

 

Regards,

 

Kavya Rao

The Zoho Desk Team