Life. Work. More together.
Emnaro — Around you like a partner
Data and operations

Import reviewed spreadsheets and export table data

Use source templates, bounded validation and explicit confirmation without bypassing permissions or posted history.

Use source templates, bounded validation and explicit confirmation without bypassing permissions or posted history.

Understand what an export contains#

Excel and CSV actions beside a table download only its currently visible page and visible data columns. They do not load hidden records or fetch another user’s private data. Action controls and secret values are excluded. Use an app’s dedicated full export, where available, for its authorised filtered record set.

Excel exports use text cells to preserve identifiers and prevent formulas from executing. CSV export neutralises formula-leading text. Import templates are distinct from presentation exports: an exported table is not automatically a valid import file.

Use the template for the correct source#

Open Import & sample CSV beside a supported table, or Data transfer studio. Eligible destinations are configured CRM contacts, To Do tasks, Inventory items, Inventory warehouses and blank private Projects. The list reflects your current app and write permissions.

Other operational tables, immutable history and government/payment results use their original source workflows. An Import options link explains available destinations; it does not allow a direct write to the table you were viewing.

  1. Choose an eligible destination and read what the operation creates.
  2. Download its sample CSV. Replace every fictional record and keep the exact column names and order.
  3. Save UTF-8 CSV or a simple XLSX workbook. Use no more than 100 data rows and a 1 MB file. XLSX reads its first worksheet.
  4. Upload and preview. Resolve every row-level validation issue before continuing.
  5. Review the complete file and explicit confirmation, then confirm the import.

Prepare values deliberately#

Keep barcodes, phone numbers and record IDs as text in Excel so leading zeroes survive. Use ISO country and currency codes where the template requires them. Dates use YYYY-MM-DD; a time-zone field uses its IANA identifier. CRM roles use a vertical bar, for example customer|vendor, and must be enabled in CRM setup.

For tasks, use an existing list ID you can write to, one of its configured status keys and a supported priority. Tasks are unassigned on import. Project imports create private blank projects with billing off; you must deliberately share or enable billing later. Inventory item import creates no stock receipt or valuation.

XLS files, formulas, macros, external workbook links and data connections are not supported. Replace formulas with reviewed values and remove unrelated sheets before uploading.

Preview and confirmation are separate operations#

Preview runs the normal source validation transactionally and rolls back its trial records. No contacts, tasks, projects or inventory records are created until confirmation. If any row fails, correct the file and upload a new preview.

A valid preview lasts one hour. Confirmation rechecks current permissions and business rules, and commits all rows together. A failed commit creates none of the batch’s records. Retrying the same confirmed batch does not create duplicates. Uploading another file intentionally starts another batch, so check existing records first.

Import payloads are encrypted and removed after their seven-day retention window. Demo workspace deletion removes its associated import data. These temporary payloads are not an archival backup.

Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.