Sanka
Back to SankaLogin

CSV Import and Export Cookbook

Use these practical patterns to prepare CSV files, update records safely, and reduce import errors.

Last updated: May 16, 2026

Guide overview

This page brings together the most useful CSV operating patterns across objects. Use it when you are importing master data, updating existing records, exporting records for cleanup, or training a team that works with CSV regularly.

Choose the import strategy

Decide the purpose of the file before you start editing it.
  • Create only: use this for new master data.
  • Update only: use this when records already exist in Sanka.
  • Export -> clean -> reimport: use this when you need to correct many existing records safely.
Recommended practice:
  • Separate create files and update files whenever possible.
  • For updates, include a stable key such as Record ID or another unique business key already stored in Sanka.

Prepare the file before upload

Before you upload:
  1. Start from the object template or a fresh export whenever possible.
  2. Keep one header row only.
  3. Keep date, amount, and text formats consistent across the whole file.
  4. Remove helper columns that should not be imported.
For large projects, keep one “working” spreadsheet and export a clean CSV from it each time instead of editing old CSV files repeatedly.
Most CSV issues come from unstable matching rules.Examples:
  • Use Record ID for updates when you already have it.
  • Use one stable key for related records, such as a company ID, item code, location code, or subscription key.
  • Make sure the same key format is used on both sides before you import associations.
If you are importing inventory operations, load the master data first:
  1. Items
  2. Locations
  3. Inventory or inventory transactions

Test with a small pilot first

Always test the mapping with a small sample before importing the full file.
  1. Upload 5 to 20 rows first.
  2. Check the created or updated records in the object view.
  3. Review the import history and error file if anything failed.
  4. Fix the mapping or source values before uploading the full file.
This saves far more time than correcting hundreds of rows after a full import.

Create a repeatable CSV workflow

Once a CSV process works, turn it into a repeatable team routine.
  • Save the source spreadsheet structure.
  • Reuse the same header names each time.
  • Save export templates for common review jobs.
  • Document which object key your team uses for updates.
If a team asks the same CSV question often, add the answer to your internal handoff note next to the template file so the next import starts faster.