# edSI college trial & implementation checklist
Updated: October 17, 2026
Guide and FAQ: https://edsi.app/docs/trial-and-migration
Microsoft setup: https://edsi.app/docs/microsoft-sign-in

## Start and explore
- Just looking? Visit https://demo.edsi.app for published administrator and staff logins with separate four-hour sample sessions. No signup is needed.
- Create a trial at https://edsi.app/signup with college name, contact email, username and password (12–128 characters).
- Save the recovery code shown once. Return at https://edsi.app/login.
- No ChatGPT/Microsoft setup, payment card or automatic billing is required for new trials.
- Explore fictional students, tuition, programs, cohorts, instructors, schedules, labs, placements and supplier bills.
- Use invented data only. Uploads and real staff invitations require verified production setup.
- Try the fictional sample CSV in the migration preview. CSV checks run locally without an AI model or server upload.
- Reset sample data after confirming the college name to discard trial edits.

## Prepare the implementation review
- College: nominate the implementation contact, data owner, academic reviewer, finance reviewer and IT/source owner.
- Scope: identify source systems, record types, cutover date, history, document scope and exclusions.
- Source: provide an anonymized sample export, field dictionary, stable record IDs and relationship definitions.
- Academic: prepare approved programs, cohorts, delivery requirements, schedules and reference documents.
- Finance: prepare fee schedules, payment history, agreed arrangements, opening balances and control totals as of a fixed date.
- Access: prepare the approved administrator/staff/instructor/student roster, student-record links and cohort assignments.
- Microsoft: prepare tenant ID, primary administrator work/school sign-in username, verified domains and a tenant administrator who can grant consent.
- Source access: agree read-only/scoped access first. Install credentials through a secure connection process, never in documents or metadata fields.

## AI-assisted migration approach (planned; not enabled)
1. Discover the source structure and draft configuration questions.
2. Propose source-to-target mappings, program/cohort matches and confidence/rationale.
3. Flag missing data and possible duplicates for college review; do not auto-merge uncertain identities.
4. Approve mapping/configuration versions, then dry-run into separate staging.
5. Reconcile counts, source IDs, relationships, rejection reasons, student balances and payment totals.
6. Obtain named college approval for scope, exceptions, identity access and cutover.
7. Import using an idempotent batch ledger and stable source identifiers; retain pre-import backup and rollback plan.
8. Reconcile again, test representative roles, obtain sign-off and enable separately approved ongoing synchronization.

Before AI processes real records, approve provider/model settings, permitted fields, retention and regional requirements. Imported text is data, not agent instructions. Human review controls financial, identity and approved academic decisions.

## Leave the trial and prepare production
- Choose Start production setup; review the removal warning and type the college name.
- This clears trial students, payments, bills, staff examples, programs, cohorts, settings and trial activity, and creates an empty workspace.
- College name, reserved address and administrator trial login remain. Sample configuration does not carry over. The action cannot be undone.
- Temporary credentials can prepare programs, cohorts and connection metadata in the clean workspace; real student, financial and personnel writes remain blocked.
- Complete college/administrator verification, Microsoft identity linking, role tests, connector/import implementation, reconciliation and college acceptance before live use.
- Confirm commercial terms and support scope separately. Starting setup does not activate billing or production.

## Availability and recovery
AI mapping, live connectors, production Microsoft sign-in and import execution require implementation and testing. The records assistant currently uses rules over permitted records. A subdomain is reserved at signup; activation follows hosting/certificate verification. Use the immediate edsi.app workspace link until then.

A recovery code can replace a forgotten password and revoke old sessions. Email resets are not enabled. If both password and recovery code are lost, automatic recovery is unavailable; create a new sample trial. Contact email alone never grants college ownership or access.