Templates & worksheets · Copyable CSV template

Prepare a directory CSV that imports cleanly and safely

A concrete header set and preflight process for moving reviewed records into a directory without turning import errors into public content errors.

CSV PREFLIGHT
01Map02Validate03Verify
Direct answer

The practical answer first

A directory CSV import should use UTF-8 encoding, one header row, stable field names, one listing per row, explicit required values, normalized URLs and controlled options, and a predictable representation for blanks and booleans. Validate duplicates and a small batch before the full import, then review public results and retain a rollback export.

Who this is for

For operators migrating spreadsheets, combining partner files, or preparing the first bulk load into a directory platform.

When to use it

Copy the headers and preflight steps, then align them with the chosen platform's current template and field dictionary before importing.

01

Freeze the target schema first

Create the directory's shared fields and select options before transforming source columns. Map every source header to a target field, intentional omission, or review queue. Do not add fields during import merely because a spreadsheet contains them; each public value needs purpose and ownership.

  • Use stable machine-friendly headers.
  • Document required and controlled values.
  • Separate public data from internal source notes.
02

Normalize values without inventing facts

Trim whitespace, preserve meaningful capitalization, convert URLs to absolute form, map booleans consistently, standardize category and select values, and leave unknown values blank for review. Keep source originals in a controlled backup so transformations can be traced and corrected.

  • Do not infer credentials or availability.
  • Use one delimiter and proper CSV quoting.
  • Remove formulas and executable spreadsheet content.
03

Validate identity and row quality

Check stable IDs if available, duplicate names and domains, required values, malformed URLs, invalid categories, unexpected select options, character encoding, overlong content, and image rights. Create an exception file rather than forcing bad rows through default values.

  • Sample every source and category.
  • Resolve duplicate ownership before import.
  • Keep rejected rows with clear reasons.
04

Import in stages and verify output

Export the current directory first, import a small representative batch, inspect cards, listing pages, search, categories, and private fields, then proceed in controlled batches. Compare accepted and rejected counts, record the import version, and run a post-import quality sample before publishing.

  • Use a staging directory or draft state when available.
  • Never assume import equals publication approval.
  • Retain the source, transformed file, and result log.
field set

Copyable CSV starter

Use this as a conceptual header set and adapt exact keys to the current platform template. Asterisks identify the usual minimum fields.

  1. 01
    Headers

    name* , short_description* , website_url* , category* , full_description , image_url , featured.

  2. 02
    Custom

    custom_specialty , custom_region , custom_pricing_model , custom_language , custom_accepting_inquiries.

  3. 03
    Rules

    UTF-8; comma delimiter; quoted multiline text; absolute https URLs; true or false booleans; blank unknowns.

  4. 04
    Preflight

    required values; duplicate domain; URL status; allowed category; select options; content length; rights.

  5. 05
    Record

    source_file; transform_version; imported_at; accepted_rows; rejected_rows; reviewer; rollback_export.

FAQ

Frequently asked questions

Can Directoryz import and export CSV files?

Yes. Directoryz supports standard CSV import and export. Use the current product template for exact headers and test a representative batch before a large operation.

Does Directoryz provide live Google Sheets or Airtable sync?

No. Treat spreadsheets and external tables as explicit import sources. Do not promise automatic synchronization or external refresh that the product does not provide.

How should multiple categories be represented?

Follow the current importer specification and the directory's flat category policy rather than inventing a separator. Validate the exact representation in a small test import.

Run a controlled import

Load a representative CSV before the full dataset

Create the target fields in Directoryz, download the current template, import a small batch, inspect public output, and retain standard CSV exports for portability.

Start a CSV import