Commit and monitor an import
After you review the import preview, committing is what writes your members to MapleGather. This guide explains how to confirm the commit and what to do while it runs — including what happens if it’s a large file.
Who can do this: Admins with the import commit permission (imports:write). If the Confirm import button isn’t available to you, ask your Org Owner.
Before you start
Section titled “Before you start”- Review and approve the import preview first. Committing without a fresh preview is blocked — if you changed the file or mapping since the preview, MapleGather will ask you to re-preview before you can proceed. See Review the import preview and relationship graph.
- On the Preview import screen, select Confirm import.
- Read the Commit import dialog: “This will write the imported rows to your member database. You can undo within 48 hours.” Select Commit import to proceed.
- MapleGather moves to the Import progress screen. For smaller files, the import completes quickly and you’re taken to the summary screen automatically.
- While the import runs, the screen shows a moving bar and “Importing {N} rows. This page updates every few seconds.” ({N} is the number of rows in your file). The import writes all of its rows in one step, so there’s no count of rows done so far and no time estimate. You can leave this page and come back — the import continues on the server. In the import history on the Migration page, the row shows Importing · Live beside its status while the import runs, and the list updates itself every few seconds. If the import has no outcome 15 minutes after it started, the screen shows “This import hasn’t finished after 15 minutes” with a Retry import button, and the history row shows Importing · over 15 minutes. See Your large import seems stuck or slow.
- If another import is already running for your org, you’ll see a notice that your import is queued. It will start automatically when the first one finishes. (Not available yet: MapleGather doesn’t queue a second import behind a running one today — the import status has no “queued” value. This is planned with concurrent-import support (Story 14.1.5, M2, not built yet). Kept as written for that release.)
- Cancel import is shown on the progress screen but isn’t available in this release: the screen says “Cancel isn’t available in this release. An import that stops before it finishes saves none of its rows, and this page then offers Retry import.” Let the import finish; if it brought in the wrong data, you can undo it within 48 hours of it completing (see Undo a committed import).
Verify
Section titled “Verify”You’ll know the import is complete when the progress screen takes you to the summary screen, headed Import complete (or Partial import if some rows failed). The summary shows how many members were imported and how many rows failed.
If something goes wrong
Section titled “If something goes wrong”- The import is taking a long time — A large file takes longer, and the screen gives no time estimate. If it hasn’t finished after 15 minutes, the screen says so and offers Retry import. See Your large import seems stuck or slow.
- The page shows “Re-preview required” — The file or mapping changed since you previewed. Go back to the mapping screen and confirm your columns again, then retry.
- The import shows “Import failed” — Nothing from the import was saved, and a failed import can’t be started again or re-mapped: where the next step is to import again, that means uploading the file again as a new import. The message under Import failed names the cause, word for word, and what to do next. Select View import summary to open the import’s summary, which is headed Import failed and repeats the cause under Nothing was imported:
- “The uploaded file couldn’t be read from storage after 3 tries, so nothing was imported. Upload the file again to start a new import.” — MapleGather couldn’t read your uploaded file. Upload it again.
- “The uploaded file is no longer stored, so nothing was imported. Upload the file again to start a new import.” — The uploaded file was removed, or its upload never finished. Upload it again.
- “The file has no data rows, so nothing was imported. Check that it has a header row followed by one row per member, then upload it again.” — The file has headings but no members under them.
- “None of the file’s rows could be imported. The error report lists why each row failed: fix those rows and import the file again.” — Select View import summary, then Download error report to see why each row failed (see Your import has errors or skipped rows).
- “Two columns were mapped to the same field, so nothing was imported. Upload the file again to start a new import, and map each column to a different field.” — Start a new import with the same file, and on the mapping screen map each member field to one column only.
- “Other changes to the same members were being saved at the same time, so nothing was imported. Upload the file again to start a new import.” — Someone or something else was changing the same members. Upload the file again as a new import.
- “A data rule refused one of this import’s changes (for example, a value that must be unique was already in use), so nothing was imported. Check the file for values that repeat or match existing members, then import it again.” — Look for a value that appears twice in your file, or that another member already has.
- “An unexpected error stopped this import while it was saving its rows, so nothing was imported. Upload the file again to start a new import.” — Something went wrong inside MapleGather while saving. Upload the file again.
- “This import was started 3 times and never finished, so it has been stopped and nothing was imported. Upload the file again to start a new import. If the file is very large, splitting it into smaller files lets each import finish sooner.” — See Your large import seems stuck or slow.
- “This import failed before it recorded a reason, and nothing was imported. Upload the file again to start a new import.” — An older import that failed before MapleGather recorded failure reasons.