Notion Manual Import

Notion Manual Import prepares another module's confirmed field list for a Notion database. It owns the CSV, property mapping, option lists, import steps and verification for the Notion output. It defines no new business table: names and order come from the same canonical fields used by the owning module's SQL, JSON Schema and spreadsheet artifacts.

Manual outputs require no workspace connection. The workflow recommends one CSV, one separate mapping table and a short import path because CSV does not carry Notion property types. The user imports and configures the database; the text helper does not itself upload files, create properties or establish relations. A separately requested connected build uses verified tools and destination information and reports only confirmed changes.

Use it whenever Notion is selected as an output, when a user wants a manual template, CSV or setup instructions, or when direct creation is unavailable. It reuses database names, types, options, relations, currency, dates and IDs already confirmed by the existing module. It does not force a connected integration or automation.

If the source field list is missing or ambiguous, identify which database to prepare before continuing. Do not guess a schema or claim a completed Notion action based on a static mapping. Legal, tax and payroll review remains necessary before an imported database drives real decisions.

The default CSV is header-only, encoded as UTF-8 with a byte order mark. Example rows require an explicit request and remain obviously synthetic. A header row looks like this as:

Field 1,Field 2,Field 3

Those illustrative names are replaced by the actual confirmed fields. Emit only the requested pieces: a CSV alone, mapping alone, instructions alone, or the complete package with options and verification. Keep explanatory prose outside machine-readable data.

The mapping assigns one suitable existing field to Title and discloses any technical title field needed when none is suitable. Text and long text stay Text; numbers use Number; money uses Number with a user-chosen currency format. Percentages supplied on a zero-to-100 scale are converted to fractions before percent formatting. Dates and datetimes use Date, checkboxes use Checkbox, select and multi-select fields use their respective types, and URLs, email, phone, person and files use the corresponding properties.

External IDs are preserved as Text. A separate generated Unique ID is added only on request, without inventing a prefix or replacing the Title. Option lists come from the existing module, with user-supplied values taking precedence; starting sets are not presented as a settled taxonomy. Calculated values preserve whether the owning module defines them as entered, formula-based or computed elsewhere. No business formula is invented.

Use Notion's CSV import action to create the database, confirm the destination and column mapping, and avoid creating a duplicate first. For an existing database, use merge or import only when intended and check for duplicates. If a header-only CSV is rejected, create its properties manually rather than adding fake records. UI labels may differ by version; the instructions identify actions.

After import, configure properties in order: Title, dates, numbers, currency, select fields, status fields, IDs and relations. Relations need both databases to exist, conversion of the Text field to Relation, selection of the target and manual checking of linked records. Rollups, formulas, permissions and sharing require later manual configuration.

Verify the database name, fields, property types, date and currency formatting, select and status options, ID setup and relations against the existing database. A currency format does not choose the business currency, and a text reference does not prove a working link. The imported database remains unverified until these checks match.