Import, Export & Data Issues

2 min read

Bad imports, missing exports, and duplicate records.

Overview

Data problems are cheap to fix early and expensive later. The two rules worth remembering: test-import a handful of rows first, and merge duplicates rather than deleting them.

Common Symptoms

Imported records have data in the wrong fields
Likely cause: Column mapping was wrong.
Fix: Re-import a small corrected batch. Always test five rows before running the full file.

Import created duplicate clients
Likely cause: The same client already existed under a different email.
Fix: Merge the records — deleting one takes its orders and invoices with it.

Export never arrived
Likely cause: Email-delivered exports depend on mail config.
Fix: Check spam, then fix SMTP. Orders & ratings downloads directly as .xlsx or .csv instead.

Export is missing rows you expected
Likely cause: Exports follow the active filters and status tab.
Fix: Hit Clear before exporting if you want the full data set.

Cannot export at all
Likely cause: Export is a separate permission per module.
Fix: Enable the module’s export permission on the role.

Report data looks wrong
Likely cause: The date-range filter, or department access scope narrowing what that member sees.
Fix: Check the range first, then whether their role has department scope on.

A record changed and nobody knows why
Likely cause: Someone with permission edited it.
Fix: Check the record’s history, or Settings → Activity Logs for the workspace-wide trail.

Tips & Best Practices

i

Never delete to fix a data problem. Merge, correct, or re-import — deletion is the one action that takes history with it.