All articles
Getting started

One source of truth: a checklist for your first import

Your data probably lives in five spreadsheets and two phones. A short checklist to bring it into one place cleanly, the first time.

2 October 2026 · 1 min read

Every team starts with scattered data: an Excel file per salesperson, a contacts export, a list someone keeps on their phone. Moving it into one system is the moment to clean it, because messy data imported once stays messy forever.

Before you import

  • One file per kind of thing: people in one, companies in another.
  • One row per Entry and one column per detail; no merged cells.
  • A column that identifies each row uniquely, such as email for people or domain for companies.
  • Consistent values: one spelling per value, not a mix of “Riyadh”, “RUH” and “الرياض” in one column.

Import companies first

If your people file names each person’s company, import companies first. Relio then links each person to their company by name. Importing through the Relio assistant? If a company in the file is not in Relio yet, it asks whether to add it or leave it out, rather than leaving you forty failed rows to find later.

Let matching prevent duplicates

Choose the unique column, email for people or domain for companies, as the match. Importing the same file twice then updates Entries instead of creating copies, which makes it safe to fix a sheet and import it again.

Check before you write

Relio checks the file before importing and tells you how many rows will be added, updated or refused, and why. Fix the few problems in the sheet, or download the error report, correct it and import just those rows.

Attach the file to the Relio assistant instead and it will map the columns for you; you confirm before anything is added. Either way, the goal is the same: one place your whole team trusts.

More articles