Import CRM records with a preview before committing

A spreadsheet import is a good time to make your customer data clearer. Start with a small, understandable file and review what Klaq says it will create before committing the import.

The short version

CRM CSV import and export require an eligible paid workspace. Choose the record type, prepare the supported columns, inspect the validation preview, resolve row errors, and commit the import once.

Choose the destination before preparing the file

Decide whether the rows represent leads, contacts, companies, deals, or another supported record type in the CRM workflow you are using. The same name in a spreadsheet can refer to a person, a business, or an opportunity; those should not be treated as interchangeable.

Use the import interface and supported format to determine the columns. Do not add made-up columns and assume the importer will store them as custom fields.

Clean the facts you can verify

Review names, contact information, and relationships. Remove rows you know are repeated and clarify fields that are being used for more than one purpose.

If you are importing assignments, make sure the referenced people are current workspace members and the action is available to your role and plan. Lead visibility continues to apply to imported records.

Keep the first import narrow enough to understand. A file that is difficult to explain before importing will usually be difficult to manage afterward.

Use the preview as a decision point

Klaq validates the input and provides a preview with row errors. Fix those errors in the source file, then preview the corrected version again.

A preview is not a completed import. Check what is being accepted, what is rejected, and whether the resulting record type matches your intention before committing.

The commit creates the accepted operation atomically and uses retry protection. If a response is unclear, inspect the outcome rather than changing the request just to force another import.

Review the records in context

After the import, search for a few known records and check their details, relationships, and assignment visibility. Confirm that the data is useful in the CRM views your team actually uses.

For exports, remember that the selected filters determine the records included. A filtered export is not necessarily a complete backup of every CRM record.

Common questions

Does import give Free workspaces extra capacity?

No. Workspace limits and feature entitlements still apply. Import is a data-entry workflow, not a way around them.

Does exporting a filtered list export only the visible page?

Klaq's CRM export uses the matching filtered set across pages, subject to its technical export limit.

Explore CRM and review shared customer identity before merging information from different sources.