Directoryz

Map CSV headers to directory fields

Header mapping should connect meanings, not just similar names. Two columns with the word location may represent different concepts.

Directoryz editorial guide · Updated September 7, 2026

Put it into practice

Create a mapping table with source column, destination field, transformation, and example. Review ambiguous mappings before importing.

Worked example · illustrative

What this looks like

A column named Region might describe sales territory rather than office address. Map it to service coverage only after checking the source.

Before you move on

Does every mapped column retain its original meaning?

Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.

A repeatable workflow

  1. Keep an untouched source copy.
  2. Test changes on a small sample.
  3. Compare imported records with the original data.

Your working notes

Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.

Where Directoryz fits

Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.

Foundations and templates →