Overview

Reference in progress; facts below marked verified vs TBD are intentional.

verified — Import Templates lets operators bulk-create or update end-user (singles) profiles from a spreadsheet. Each template stores how CSV columns map to profile attributes, preference fields, status history, photos, and sign-in fields. This is separate from Import CSV on SME Profiles, which creates matchmaker accounts only.

Open the list from the Admin menu entry labeled Import Templates. After you pick a template, map columns, and upload a file, profiles are created or updated on your current brand.

For day-to-day search and one-off edits, use End Users list and View end user. The list page summarizes the same template workflow under page actions.

Who can use this

RequirementMeaning
Import Templates List page permission verified — Without it, the menu entry and list are hidden.
Edit on the template page verified — Required to save template changes and to run Import Data.
View single (End Users) verified — The import API requires the same edit permission as changing an end-user profile.

Template list

verified — The list table shows:

ColumnMeaning
IDTemplate id (general code row).
NameDisplay name you chose when creating the template.
Column MappingsCount of rows in the template’s main column-mapping list (not counting preference-mapping rows).
Is ActiveWhether the template is marked active on the general code. Use this flag to tell operators which templates are still in use.

Click a row to open the editor. Create Import Template asks for a name, then opens a new template wizard.

Template editor

Left navigation cards on the template detail page.

SectionWhat you configure
Template Info Template name, delimiter, and default date format — see Template info fields.
Upload CSV verified — Upload a sample CSV so Admin can read header names and preview values. Use this while building mappings; production import uses Import Data (separate file picker).
Column Mappings verified — One row per spreadsheet column: map to a profile attribute or a special type (ID, status, photos, etc.). Unmapped or hidden columns are ignored on import.
Preference attributes mapping verified — Extra rows for preference-style answers (often age/height ranges with a gap) — see Preference mapping.
Process Logs verified — Appears after you start an import; streams live progress until completion or a blocking failure.

Save persists the template definition only — it does not import members. Use Import Data on the same page when mappings are ready.

Template info fields

FieldWhat to enterEffect on import
Name Short label operators recognize (for example “Legacy CRM export 2026”). verified — Shown on the template list and page title only.
Delimiter Character Usually a comma. Use another character only when multi-value cells in the sheet use that separator. verified — Splits multi-select and multi-value attribute cells; also used when force validation checks each part of a list value.
Date format (date format) Auto-detect, or pick DD/MM/YYYY, DD-MMM-YY, MM/DD/YYYY, or YYYY-MM-DD. verified — Default parser for date attributes and birthdate columns, and for optional Created / created columns that set the member’s join date.

Column mapping types

For each CSV column, choose a type before you pick a target attribute.

Type (Admin label)When to use itWhat happens on import
ID Exactly one column per template — your stable key for each row. verified — Required. If the cell looks like a member UUID, Admin updates that profile. Any other value is treated as an external ID stored on the profile. Empty ID → row error. New key → new profile + sign-in account.
Add Attribute Most bio, pref, and custom fields. verified — Maps through response rules (below) into profile answers. Sensitive fields (phone, email, birthdate, etc.) also update the member’s sign-in record. Imported values are marked so Admin can tell they came from CSV.
Status Current profile status column. verified — Match spreadsheet text to status labels using your response map (case-insensitive). Sets the profile’s current status id.
Images Photo URLs (one or more per cell). verified — After the profile row saves, Admin downloads each URL and attaches photos in order (first URL = primary ordinal 1).
Profile status updated date Historical “status changed on” date for migrations. verified — After save, inserts a status-history row (from pending → imported status) with this timestamp. Pair with Mark as profile status update by when you have legacy staff ids.
Profile status updated by Legacy backoffice user id for who recorded the status change. verified — Resolves numeric ids against current staff users or legacy id settings; invalid ids produce a row warning in process logs.

verified — Columns you mark hidden in the mapping UI are skipped on import (useful for reference columns in the sample file).

Response mapping and advanced options

For choice-style attributes, map each distinct spreadsheet value to the answer label Admin should store. For open-text attributes, you often map the column directly without a value table.

OptionMeaning
Response map rows verified — Source = text in the CSV cell; Target = stored answer (or status id for status columns). Use a $default source row to fill empty cells with a fixed default target.
Force validation verified — When enabled, every value (or each part of a multi-value cell) must match a known question answer. Unknown values add a row message in process logs and that attribute is skipped for the row.
Join columns verified — Merge extra CSV columns into one attribute (for example notes + sub-notes). Optional preserve column name prefixes each piece with the header name.
Pre-validation rules verified — Same eligibility engine as questionnaires: if rules fail for that profile, the column is skipped for that row (other columns still import).

verified — Name-type attributes are title-cased on save. Scale and range answers accept numbers; invalid birthdates produce an explicit row message.

Preference mapping

verified — Use Preference attributes mapping when preferences live in their own columns (common for age or height “center” values).

  • Pick a source column and a target preference attribute (same mapping tools as main columns).
  • Gap — When set, a single number in the sheet becomes a min/max pair: value minus gap and value plus gap (for example center 30 with gap 2 → 28–32). When gap is zero, split the cell on the delimiter for explicit min and max numbers.

Running an import

  1. Save the template at least once (new templates must be saved before import).
  2. Click Import Data and choose the production CSV file.
  3. verified — If the file has more than 10 data rows, Admin shows a confirmation dialog (Import Profiles) with the row count before processing starts.
  4. Watch Process Logs — progress includes backup, row batches, photo uploads, optional group creation, and search-token repair.

verified — Import runs in the background. Admin may show a success notice when the request is accepted; rely on process logs for the real completion message and any row-level warnings.

Partial failures and retries

verified — Many issues affect only one row or one field while the rest of the file continues:

  • Missing ID, invalid birthdate, unknown choice when force validation is on, bad status-history date or staff id, photo download failures.
  • Sign-in update failures for an existing member (Admin logs the row; profile data may still save).

Process log lines often start with Row N: (row numbers include the header — row 2 is the first data line).

Retry playbook

  1. Export or copy error lines from Process Logs.
  2. Fix those rows in the spreadsheet (or adjust mappings / response map).
  3. Re-import using the same ID column so existing members update instead of duplicating.
  4. For a catastrophic failure (bad file format, missing ID mapping, backup failure), the job stops early — fix the template or file before re-running.

verified — Before processing rows, the server takes a brand-level backup snapshot of profiles for disaster recovery (operators do not download this from the UI).

What happens after import

  • verified — New members get a sign-in account, start in pending status unless your status column sets another value, and are flagged for the standard return-to-onboarding flow.
  • verified — Updated rows write an attribute change log entry staff can audit on the profile.
  • verified — Every newly created member from the run is attached to a new inclusive group named like “Imported Users – …” (automatic — not a template toggle). Use Groups to rename the group or remove members if ops no longer want that default segment.
  • verified — Sensitive search tokens are repaired in the background for all profiles touched in the run (so imported members remain searchable).
  • verified — New and updated profiles appear on End Users list after refresh (managers may need to clear search to browse).
  • verified — Status history columns insert historical rows visible on View end user status history.
  • Matcher refresh and automated comms depend on which attributes and statuses changed — treat large imports as high impact and coordinate with ops before running on production brands.

Ops visibility

When the last singles CSV import completed.

verified — When a template import finishes successfully, Admin stores a brand-level timestamp (last profiles imported) in mobile app settings. That value is not shown on the End Users list.

verified — On the matchmaker mobile app home dashboard, brand administrators may see a single line under the quick actions with the formatted date of the last completed import. The row appears only when:

  • Your brand enables the show latest import date on matchmaker dashboard app feature, and
  • A completed import has written the timestamp (empty until the first successful template import).

Matchmakers who are not brand admins do not see this row. Updating SME rows via SME CSV import does not change this date — it tracks end-user profile template imports only.

SME onboarding ops: SME Profiles · Shidduch queue: Shidduch Requests.