Import CSV and Excel records

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment All supported models

Overview

Import Jobs uploads a durable CSV or XLSX source, maps its columns, validates rows and waits for confirmation before importing. Background processing records progress and row outcomes. The original small synchronous import path is separate.

Purpose

Load a reviewed dataset while identifying validation and duplicate problems before committing records.

Prerequisites

• Import access and the required create/edit rights on the target module.

• A clean CSV/XLSX file for a supported module such as Leads, Accounts, Contacts or Products.

• Approved duplicate handling and field mapping.

Procedure

1. Open Administration > Import Jobs and choose Upload import file.

2. Select the target module and source file. Review detected columns and sample rows.

3. Map source columns to supported CRM fields and choose the available duplicate handling policy. Save the mapping to queue validation.

4. Wait for Ready for confirmation. Inspect validation counts and row-level issues; correct the file or mapping if the preview does not match your intention.

5. Confirm the validated import only after review. Monitor processed, successful and rejected rows as the worker commits batches.

6. Download available error results with appropriate export permission. Correct rejected rows in a new source when necessary.

7. If you cancel, verify the terminal state and existing success count before deciding whether retry is appropriate.

Expected result

Validated rows are imported with durable job history and explicit row outcomes.

Screenshots and diagrams

SS-048 · Import jobs (empty). Demonstration capture, 28 October 2026. Select the image to enlarge.

Important notes

• Background imports are bounded to 10000 rows and 50 columns, with the configured upload-byte limit. The legacy synchronous import retains its smaller limit.

• Batches can commit up to 100 rows. Cancellation stops future processing; it does not undo already committed records.

• Changed mapping invalidates the prior preview and requires a new review.

• Completed histories are retained; a completed job cannot simply be reset.

Troubleshooting

• Validation does not progress: inspect worker health.

• Required field errors: check mapping, format and the published custom-field rules.

• Duplicate errors: apply the approved duplicate policy or correct the source.

• Retry risks duplicates: read prior row outcomes and committed counts before resubmitting.

Related articles

• Create and update CRM records

• Manage Leads

• Maintain the Products catalog

• Read System Health and verify service readiness