Skip to main content
Migration Concierge is an optional paid service for schools that would rather hand off their legacy-data import than run the self-serve wizard themselves. An administrator submits a request from inside Zion, and Zion staff complete the import on the school’s behalf using an internal tool. The request form and its status live in the app; the import work itself happens off to the side, run by Zion, not by your team.
Requesting Migration Concierge requires an active subscription.

​
When to request it

Use the self-serve importer at Importing Legacy Data if your team is comfortable preparing a CSV and walking through the upload, mapping, dry-run, and commit steps. Request Migration Concierge instead if you would rather not do that work yourself, for example when your legacy data needs more cleanup than your team has time for, or when you want someone else to own the mapping and verification steps.

​
How to request it

1

Open Import

Go to Import from the sidebar (administrator access only) to reach the import page.
2

Find the Migration Concierge card

On the import page, use the Migration Concierge Service card.
3

Submit your request

Provide a contact name and email, your organization’s name, the source system you are migrating from, an approximate student count, and any optional notes about your data.
4

Wait for follow-up

Once submitted, the card shows a status chip confirming your request was received. The Zion team follows up outside the app to coordinate next steps.
A school can have only one active request at a time. If a request is already pending or in progress, a new submission is blocked until it is resolved.

​
What Zion staff do with your request

Migration Concierge requests are handled through an internal tool that is not part of any customer-facing navigation. Zion staff members with the appropriate internal access review submitted requests and open the matching import wizard for your organization. That internal wizard mirrors the same steps as the self-serve importer: upload, map columns, run a dry-run preview, and commit. The difference is who is at the keyboard. Every action a Zion staff member takes while working on your request is scoped to your organization and attributed to that staff member, and a persistent banner is shown throughout confirming which school’s data is being worked on.

Importing Legacy Data

Run the self-serve import wizard yourself: upload, map columns, dry-run, and commit.

Exporting Data

Request an export bundle of your school’s data once it is in Zion.