AURADATA GUIDES

Review business-data files before using them

Exporting a file is only one step. Before importing a CSV into a spreadsheet or business system, check what each column means, whether identifiers changed and whether repeated records are being counted as new opportunities.

Keep the original and a change log

Save the file as received and work on a separate copy. Record the source, export date and purpose. If you normalize city names or merge records, keep the reason so that the change can be reviewed or reversed.

A filename is not evidence of freshness. Keep an actual verification date separately when one is available.

Import phone numbers and identifiers as text

Spreadsheet software may remove a leading zero or turn a long identifier into scientific notation. Choose a text column type during CSV import, before accepting the preview. Formatting a damaged value afterward will not restore its original digits.

Use UTF-8 and inspect a sample of Arabic names. If all fields appear in one column, check the delimiter. Do not save a replacement until the characters, column counts and identifier lengths are correct.

Review duplicates in the context of the task

CaseBetter decisionReason
Same name, different addressCheck for separate branchesA name alone is not a unique identifier
Same source URL, different spellingReview and normalize after confirming identityThe rows may describe the same business
One phone number used by several branchesPreserve branch contextPhone numbers are not always unique
A partial and a more complete recordMerge only after checking identity and sourceSimple deletion can lose valid information

Separate missing, incorrect and irrelevant values

A missing website may mean the source did not provide one. An incomplete phone number needs verification. A business outside your sector may have accurate data but be irrelevant to your list. Use specific review reasons instead of labeling every case ‘bad data.’

Leave unknown fields blank or use a documented missing-value convention. Do not infer a person's email from a company naming pattern and present it as a confirmed fact.

Run an acceptance check

  • Compare row counts before and after processing and explain exclusions.
  • Check Arabic characters, identifier lengths and leading zeros.
  • Review a sample of merged rows and missing fields.
  • Preserve source links and the reasons for edits.
  • Export only the fields needed for the permitted task.

Where AuraData helps

Supported tools let you choose available fields, review results and export CSV. Google Maps searches can use deduplication. These features do not replace a documented quality review or imply a universal data-cleaning service for every database.

Frequently asked questions

Can I restore a lost leading zero by formatting the cell?+

Formatting alone does not recover information already lost. Return to the original file and import that column as text.

Should I delete every repeated business name?+

No. First check whether the rows are branches, different companies or true duplicates.

Choose the workflow before the plan

Review the source, required fields and usage limits, then compare point plans.

Compare AuraData plans ↗