Historical import data types reference
MapleGather can import four types of historical data from your previous system. This page describes each type, the required columns, and how the imported records behave in reports.
Overview
Section titled “Overview”All historical imports use the same upload → map → preview → commit pipeline as member imports, with the type selected at the start. All historical records are tagged mode=historical and excluded from new-revenue reports by default — they appear in the context of an individual member’s history but don’t affect your financial dashboards.
Historical payments (historical_payments)
Section titled “Historical payments (historical_payments)”| What it covers | Past dues, donations, and event fees paid in your previous system |
|---|---|
| Minimum required columns | Member Email · Payment Date · Amount |
| Optional columns | Currency · Description · Stripe Payment ID |
| Behavior | No charges are made during or after import. Records are archived as historical payments. A member must exist in MapleGather before their historical payment can import — rows without a matching member fail with “Member not found.” |
| Currency | USD only at M1. Rows in other currencies are skipped and appear in the error report. |
| Stripe IDs | If a row includes a Stripe Payment ID, live billing takes precedence. A historical payment record is still created for archival. |
Historical membership tenure (historical_memberships)
Section titled “Historical membership tenure (historical_memberships)”| What it covers | Past membership periods, “Member since” dates, and renewal history |
|---|---|
| Minimum required columns | Member Email · Level · Start Date |
| Optional columns | End Date · Status |
| Behavior | Imported periods anchor the “Member since” display for each member. The most recent active period is treated as the current membership. A future End Date is imported as an active membership rather than historical. |
| Overlapping periods | If two rows create overlapping membership periods, MapleGather shows a warning in the preview. You can allow the overlap or merge the periods. |
Historical event registrations (historical_events)
Section titled “Historical event registrations (historical_events)”| What it covers | Past event attendance records |
|---|---|
| Minimum required columns | Member Email · Event Name · Event Date |
| Optional columns | Amount Paid · Registration Date |
| Behavior | Historical events import in archived status and don’t appear on active event calendars. If a row includes a paid amount but no corresponding payment record, a zero-amount invoice is created for reporting purposes. |
| Multi-session events | If your data contains multiple sessions of the same event (same name, different dates), MapleGather offers to treat them as separate events with a shared tag (the M1 default) or as a multi-session event structure (available in a future update). |
How historical records affect reporting
Section titled “How historical records affect reporting”Historical records are excluded from new-revenue reports by default. Your financial dashboards show only activity in MapleGather. Historical records are visible in an individual member’s profile under their payment and membership history, and in reports when you include the historical filter.