Guest Import
Bulk-load guests without breaking the list
Guest Import is best for first entry or large cleanup batches. It should create usable guest records, not just unfinished rows. After import, always review Manage Guests before using RSVP, cards, envelopes, SMS, or reports.
Bulk import
Households
Cleanup pass
Import workflow
- Download or follow the guest-list template.
- Keep one logical guest or household member per row depending on the template rules.
- Use consistent names, emails, phones, mailing addresses, RSVP groupings, and special-event fields.
- Run the import, then immediately review Manage Guests.
- Fix household grouping and missing data before using Invitation or Envelope Studio.
Data quality rules
| Column | Rule |
|---|
| Names | Use real guest names, not placeholders, because the guest portal and reports depend on display names. |
| Households | Keep household/group values consistent so families and couples RSVP together correctly. |
| Emails | One bad or missing email can block email delivery for that guest. |
| Phones | Use SMS-capable numbers if the notification module will be used. |
| Addresses | Use complete mailing addresses for envelopes and printed invitations. |
| Plus-ones | Mark clearly so RSVP and seating do not double-count or hide them. |
After-import test
- Refresh the page after import.
- Open Manage Guests and verify names, not IDs.
- Open one guest-facing RSVP link and confirm household behavior.
- Run the report view to compare expected guest count against imported count.
Avoid this
Do not import over bad data repeatedlyIf an import looks wrong, stop and fix the source file or remove bad rows first. Re-importing the same flawed structure can create duplicate households and noisy reports.
Need more help?
If you have tried the checks on this page and the issue still is not resolved, open a support ticket with the couple/site name, the page you were using, and what you expected to happen.