Import undo window and reason codes reference
Undo window
Section titled “Undo window”Every committed import has a 48-hour undo window that starts the moment the import completes (reaches completed status). After 48 hours, the undo option is no longer available from the interface and a manual reversal requires contacting support.
The 48-hour countdown is visible in the Undo available column on the import history screen. When the window expires, this column shows “Window expired — contact support” and the Undo this import action is removed from the row’s menu.
What undo actually does
Section titled “What undo actually does”- Created records — removed from your organization entirely. Member profiles, membership enrollments, and payment records that were created by the import are deleted.
- Updated records — restored to their state as of the moment before the import ran. The pre-import snapshot is kept in the batch manifest.
- Inline-created items — membership levels, custom fields, or tags created during column mapping are removed only if they are no longer referenced by any other member or import. If another import or a manual record already uses a level or tag, it is kept.
- No rows are ever truly deleted — cancelled or undone records stay in the audit log for traceability. They are not visible in normal member views.
Members with activity since the import
Section titled “Members with activity since the import”If any members who were imported have since logged in, paid, or registered for an event, MapleGather shows you a count before you confirm the undo and offers two choices:
- Keep those members, roll back the rest — (default, recommended) Members who have been active stay in your system; the others are removed.
- Roll back everything — including active members — All records from this import are removed. A second confirmation step is required for this path.
Reason codes
Section titled “Reason codes”A reason code is required when you request an undo. The reason is recorded in the audit log but not shown to members.
| Reason | When to use it |
|---|---|
| Wrong file | You uploaded the wrong file — perhaps a test export or a file for a different organization. |
| Mapping error | The column-to-field mappings were wrong and data ended up in the wrong fields. |
| Duplicate data | The import created duplicates that you’d rather roll back than merge. |
| Data quality | The source data had systematic problems (invalid formats, missing values) that affect too many rows to fix individually. |
| Org cutover delayed | Your planned cutover date has moved and you’re not ready to commit the data yet. |
| Other | None of the above apply. You’ll be asked to briefly describe the reason in a free-text field. |