• First-Time Setup Tip: If setting up an account for the first time, consider importing customers, organizations, and properties before importing transaction data like jobs or projects.
  

Associations

• When importing multiple associated modules (e.g., Properties and Customers), please ensure that the unique field for the associated modules are mapped.
• Zuper supports one-to-many and many-to-many associations:
• Example: One Customer can be linked to multiple Properties. If a Customer Email appears in two rows of Property data, that Customer will be associated with both Properties upon import.

 In this step, select the module for Import, which can be a master or transaction module. For example, Select the “Customers” module and click the “Next” button. 

File Upload

Configure how your data will be imported, including primary key selection and conflict resolution.

Primary Key

• Use the “Unique field” column to choose a primary key during mapping to identify unique records and prevent duplicates. Note: This only applies to Transaction Modules.
• The primary key validates incoming records against existing data in the system and within the uploaded file.

Conflict Resolution Options

Select how Zuper handles records with matching primary keys:

1. Skip: When a record has the same unique ID as one existing in the system, it skips the record.
2. Merge: When a record has the same unique ID as one existing in the system, it updates that record.
3. Create Duplicates: A record with the same unique ID as one existing in the system creates a duplicate record.

Step 5: Data Import – Mapping Table

Map your uploaded file’s columns to Zuper fields using the mapping table.

• Multi-Module Uploads: All fields from selected modules appear in the table. Map each “File Column Header” to an “Import to Field” after choosing the “Import in Module.”
• Mandatory Fields: Must be mapped for the import to proceed. Unmapped mandatory fields will block the import and notify the user.
• Unmapped Columns: If some columns remain unmapped, confirm whether to proceed with partial mapping.

Saving Import Templates

• Save your mapping as a template (e.g., “HubSpot Contacts to Customers”) for reuse.
• Specify a name and save it after validation.

 Data Validation

• Mandatory Fields: Ensures all required fields for record creation are mapped.
• Field Values: Validates against acceptable values (e.g., dropdown options).
• Duplicates: Highlights duplicate primary keys in the file.
• Blank Fields: Skips blank values during import.

Import Process

Once the mapping is complete, click Import. The process runs asynchronously, and you’ll be notified of the status.

Choose "Allow subsequent triggers" to activate existing workflows and webhooks, keeping your data flow dynamic and integrated.

Select "Disable subsequent triggers" to prevent unwanted module interactions, ensuring a smooth and focused import process.

 

Tips for Success

• Ensure your file meets size and row limits.
• Include mandatory fields for primary and associated modules.
• Use templates for repetitive imports to save time.
• Validate data formats (e.g., dropdown values) before uploading.    
  

• Next Step: Skips Step 2 and takes you directly to Step 3: Configurations.
• If the uploaded file matches the template’s required format, the mapping in Step 5 will be pre-filled. Otherwise, you’ll be prompted to map fields and proceed manually.

Past Imports

1. Navigate to the Import Section:
• From your Zuper workspace, click on the "Past Imports" tab located under the "Import" section.
• You’ll see a list of all previous imports with details such as name, module, import date, and the user who performed the import.
2. View Import Details:
• Each entry in the "Past Imports" list displays:
• Name: The name of the import (e.g., "Asset Import 3").
• Module: The module associated with the import (e.g., "Asset").
• Imported On: The date and time of the import (e.g., 2025/02/25 02:04 PM).
• Imported By: The user who initiated the import (e.g., John Wick).
• Click on an import name to view more details if available.

• Total Records: The total number of records attempted to be imported (e.g., 1 record).
• Created Records: The number of new records successfully created (e.g., 0 records).
• Failed Records: The number of records that failed to import (e.g., 1 record).
• Merged Records: The number of existing records updated or merged (e.g., 0 records).

1. Identifying Errors:
• Check the "Failed Records" count in the Import Summary.
• The "Import Errors" panel will list the number of errors (e.g., 1 error) and the reason (e.g., "Invalid Data").
2. Downloading Error Details:
• Click the "Download errored rows as a file" link to export a file containing the failed records and error messages.
• Review the file to identify specific issues, such as missing fields, incorrect data formats, or validation errors.
3. Common Error Causes and Solutions:
• Invalid Data: Ensure all data fields match the required format and contain valid values. For example, check for empty mandatory fields or incorrect date formats.
• Mapping Issues: Verify that the custom field mapping aligns with the imported data structure.
• Duplicate Entries: Resolve duplicates by ensuring unique identifiers are correctly set.
4. Retrying the Import:
• Correct the errors in your data file based on the downloaded error report.
• Re-upload the corrected file using the "New" import option and monitor the results in the "Past Imports" section.

Best Practices

• Regularly review the "Past Imports" list to track import history and identify recurring issues.
• Save templates for frequently used imports to streamline the process.
• Clear filters when not in use to ensure you see the full import history.