Switching systems, answered.

You can phase it. Most schools start with the modules where the compliance risk is highest — attendance, SAP, records — and bring the rest over on a schedule defined in the blueprint. A staged rollout keeps daily operations running while the new system of record is stood up around them.

Yes. During cutover, Atticus can operate in parallel with your existing systems so nothing breaks on day one. The blueprint defines which system is authoritative for each record and when that authority shifts, so there's never ambiguity about where the truth lives.

Not necessarily. Atticus is the system of record for the events accreditation turns on; many schools keep their LMS for instruction and connect it, while others consolidate over time. The right path depends on your tools and is decided during the blueprint, not assumed.

Yes — boutique schools are exactly who Atticus is built for. Configuration, data migration, most integrations, staff onboarding, and 30 days of support are included, so a small team isn't left to do the heavy lifting alone.

The records that matter for operations and audits: student demographics, enrollment, attendance, academic progress, placement outcomes, documents, and historical records. The blueprint defines the full migration scope before any data moves.

No — it's the norm, and it's better to surface it now than during a site visit. Migration includes auditing and reconciling the data as it comes over: duplicates, inconsistent formats, and missing fields are exactly what the process is designed to catch and clean, rather than carry forward.

Through controlled, encrypted migration — not emailed spreadsheets. Data is encrypted in transit and at rest, access is role-based, and the migration is auditable, so personally identifiable student information is never floating around in loose CSV files.

They come with you. Historical records are migrated, dated, and reconciled so your past is as defensible as everything captured going forward — there's no gap between your old system and your new one.

Most schools go from blueprint to a live system of record in about two to four weeks, depending on the size of the data migration and the number of integrations. The diagnostic and blueprint come first, so the timeline is known before work starts.

The goal is no operational downtime. Because Atticus can run in parallel during cutover and the rollout is staged, your front office, instructors, and students keep working while the transition happens around them.

Less than most owners expect. The Atticus team handles configuration and migration; your staff's main role is confirming policies (SAP rules, attendance, placement criteria), validating migrated data, and attending role-based training before go-live.

Yes. A parallel-run, staged cutover means you don't have to wait for a term break. The blueprint sequences the switch so in-progress cohorts are never left without a system of record.

Pricing is per student, by tier, so it scales with your school rather than charging for seats or modules you don't use. Specific commercial terms are provided after the diagnostic call, once the scope is clear.

Configuration, data migration, most LMS integrations, staff onboarding, and 30 days of support are included with every engagement. Anything beyond that standard scope is identified in the blueprint up front, not billed as a surprise later.

Atticus is built to earn its place, not trap you. Commercial terms are laid out before you commit, and your data remains yours throughout — which matters most for the next question.

Yes. Your records are your property, and you can export them if you end the relationship. Data portability isn't a favor — it's a basic expectation you should demand of any vendor, and a FERPA-aligned one at that.

With role-based training before go-live — compliance, education, and front-office staff each learn the workflows they own, plus documentation and guides they can return to. Adoption is part of the rollout, not an afterthought.

Every engagement includes onboarding support and a launch-day runway, plus ongoing support and updates as standards change. You're not handed a login and left alone.

Most common LMS and third-party integrations are connected during setup. Because not every external tool integrates cleanly, the blueprint identifies which connections are in scope before work begins, so there are no surprises at go-live.

Done right, switching reduces risk rather than adding it. Records are migrated, dated, and reconciled so you're audit-defensible throughout — and a parallel run means you're never without a system of record during the move.

It's possible, but the closer you are to a visit, the more we'd sequence the rollout conservatively. The honest answer depends on your timeline and data — which is exactly what the diagnostic is for. If a visit is imminent, we'll tell you the safe path rather than rush.

Migrated records are reconciled and dated as they come over, and from go-live every event is captured the moment it happens and locked the moment it's captured. The audit trail is continuous across the old system and the new one.

Atticus handles student data under a data-processing agreement, with encryption in transit and at rest, role-based access, and audit logs of access and disclosure. Your data is used to run your school — not for any other purpose. This is general information, not legal advice; confirm specifics against your obligations.