Before you begin
What you’ll need
- Imports module enabled
- Member and sensitive-data permissions
- A UTF-8 CSV with one header row
01
Prepare the source file
Keep the first import small enough to inspect and preserve stable source identifiers whenever possible.
- Use one row per intended member record and a single header row.
- Include display name and, when available, member number, email, phone, address, plan, paid-through date, delivery mode, and source ID.
- Leave unknown values blank instead of inventing placeholder email addresses or dates.
- Normalize obvious formatting problems, but do not remove duplicate rows before the review workflow can explain them.
02
Map and preview
The preview is the place to discover what the system will create before any member, term, or payment record is written.
- Upload the CSV and map each source column to a MembershipPortal field.
- Choose a default plan only when rows without an explicit plan should receive it.
- Run validation and review normalized values, missing required fields, invalid dates, and invalid email formats.
- Compare the preview totals with the source file before continuing.
03
Resolve duplicate and shared-email warnings
A matching email is evidence for review, not proof that two records are the same person.
- Link to an existing member only after verifying member number, name, address, and relevant history.
- Keep separate records when a household shares an email or an institution has multiple contacts.
- Skip a source row when it should not create or update a member.
- Do not merge records merely to clear the queue; preserve uncertainty for a later correction when necessary.
04
Apply and reconcile
Applying the job creates reviewed records through trusted commands and keeps row-level outcomes.
- Apply only after every blocking validation error and duplicate decision is resolved.
- Review created, linked, skipped, and failed row counts.
- Compare member, term, and payment totals with the approved preview.
- Export or retain the row-level result for migration records.
- If the untouched import must be removed, use the bounded rollback workflow before staff edit or use the imported records downstream.