One project. Then the old system is read-only.
Foundation and Calendar as one committed project timed to your renewal, with a cut-over date the whole school knows. No year of running two systems.
EthosOne's CompliSpace migration is a single committed project for independent schools moving from CompliSpace (now
Operating under the Ideagen and Policy Logic names). It is timed so the incumbent goes read-only before its next renewal.
What we keep hearing
The renewal invoice is on the business manager's desk, under the enrolment figures. Last year it was signed for one more year because the move looked like a second job on top of the first. The policies sit in one system, the training records in another, and the board pack is still assembled by hand from both.
The renewal date is the only deadline in that pile anyone takes seriously, so that is the one we plan to.
A migration is Foundation and Calendar done properly. The school lands on Stage 1 with the incumbent read-only, and climbs from there at its own pace.
Foundation
Everything the school runs today is inventoried, mapped and loaded once. Staff sign in with the account they already have and every named owner has a role.
You cannot go back when the incumbent is read-only, every owner has signed in and the access matrix is signed.
- This engagement lands here
Calendar
Core and Regulatory Readiness. The strategic plan is on the dashboard with owners, the calendar carries the jurisdiction's dates, and the next submission is assembled with evidence linked per standard.
You cannot go back when an executive meeting is run from the dashboard and the next submission is assembled in EthosOne.
Risk
Risk and Compliance and Personnel. Appetite is set once and approved by the board, the register is real, assurance logs run for a full term, and the first expiry is caught by the system before the date.
You cannot go back when the first Risk and Audit Committee pack is produced from EthosOne and calendar tasks are closed on time.
Board
PolicyAI and Board Engagement. The policy review cycle runs through PolicyAI, the first legislative change is actioned, and the board pack is generated from the record for two consecutive meetings with directors logging in directly.
You cannot go back when two board packs in a row have come from EthosOne and resolutions and actions are tracked in the system.
Group
Group Management over every module. Each entity closes its own calendar, the group board pack is produced from the roll-up, and the group lead reads the portfolio view weekly.
You cannot go back when the group board pack comes from the roll-up and every entity is closing its own calendar.
Twelve weeks back from the renewal date. The cut-over is one date, agreed in week one, and the parallel run has an end written into the plan.
- Week 0
Data map
Every register, calendar, policy set and list in CompliSpace, in spreadsheets and on shared drives, listed with an owner and the module it feeds. The renewal date goes in the plan.
- Week 1
Export and inventory
The CompliSpace policy library, compliance calendar, assurance and task history and risk register out in usable form. The inventory sheet returned by the school.
Gate. Export files received and logged. Inventory returned.
- Week 2
Map and decide what to retire
Policy domains, risk categories and obligation IDs mapped to the EthosOne model. The retirement workshop: stale policies and dead tasks are retired rather than migrated. A migration is a clean-up, not a copy.
Gate. Mapping sheet approved. Retirement list signed.
- Week 3
Load
Module ingests sequenced, deduped and version-stamped. Nothing hand-keyed twice. Every record carries its source file, source date, loaded-by and mapping version.
- Week 4
Cut-over
The reconciliation report: what came across, what was retired, what is missing and who owns the gap. The incumbent goes read-only on the agreed date.
Gate. The school is operating from EthosOne alone. CompliSpace is read-only.
- Weeks 5 to 12
Climb
Calendar live with owners, then Risk, then Board, at the pace the school can absorb, with the same gates every school passes.
- Renewal date
Off
The records the school must keep were exported and linked as evidence before the switch-off. Nothing is lost with the old subscription.
Two decisions, made once, in one room.
- What to retire: the policies nobody has opened, the tasks that no longer happen, retired rather than moved.
- The cut-over date and the parallel-run window, written into the plan so there is no indefinite dual running.
- Who owns each gap the reconciliation report names, with a date beside the name.
The leadership team, a wall of decisions, a facilitator standing.
What replaces what
Every dimension a school weighs, and what each side actually delivers. The same table as the CompliSpace alternative page, so the two agree.
| Feature | CompliSpace | EthosOne |
|---|---|---|
| Focus | One of many industries served | Schools only, founder-led |
| Board reporting | Built from exports and snapshots | Board reporting sharpened and live |
| Risk management | Build-your-own risk forms | A living ISO 31000 register, not a tick-box |
| Excursions | PlanCheckGo absorbed by Assurance in 2026 | Native workflows with embedded risk management |
| SSO & security | SAML supported; setup left to your IT | SSO + MFA, set up for you |
| Support | Tiered, with some channels on premium plans | Included, no tiers to climb |
| Pricing | Modular and not publicly published | Published, predictable, per entity |
| Policies & Procedures | School-managed libraries the school re-works | Interactive version control, approval and a parent portal for sharing |
| Policy Intelligence | Generic, lawyer-drafted templates | PolicyAI: legislative intelligence, verified against the law |
| Professional Development | Learning system | Personnel: certification, compliance training and WWCC |
“It meets all of the real frustrations of business directors in one place.”
Nick MillerDirector of Business, Blackfriars Priory School- Stored in AustraliaAWS Sydney and Melbourne, one database per school
- AI stays in the country tooAmazon Bedrock; never trained on your content
- Published, not describedTrust Centre · ISMS policy · How we handle your data
The six we are asked every time.
Still weighing something up? Thirty minutes with us, on your own registers, answers the rest.
Book your school a demo01Do we have to leave CompliSpace to start?
No. Many schools run both during the project, and the parallel run is part of the plan rather than a compromise. The switch-off is scheduled for the renewal date, and until then nothing in CompliSpace changes.
02Is there an implementation discount for existing CompliSpace customers?
Yes. Ask us when you get in touch and we will set it out in the written scope, alongside the licence, before anything is agreed.
03What about our policy library?
It comes across module by module and is connected to source through AccuFind, so each policy is tied to the obligation and the Act it answers. PolicyAI, in beta, then scores coverage across 25 policy domains so you can see where the library is thin before an assessor does.
04What happens to our history?
Evidence stays where it lives, in your drive or document system, and is linked to the risk, obligation or control it supports. Records held only in CompliSpace are exported before the switch-off and linked as evidence in EthosOne.
05We are on another platform. What is switching like?
Switching is a migration of your registers, policies and compliance calendar into one structure, mapped to the obligations that created them, with your state association content already loaded.
It is one committed project, timed to your renewal. Most schools run the two side by side for a term. Your existing library is imported rather than rewritten, and every document keeps its owner, its version and its review date.
You go live before the old subscription ends, with board reporting already running and nothing rebuilt twice.
06CompliSpace migration before your next renewal, in full: what does it cover?
It runs the Foundation and Calendar stages of the onboarding ladder: the CompliSpace export, the spreadsheet and shared-drive inventory, the taxonomy mapped so nothing lands orphaned, a retirement list rather than a copy, one cut-over date, and a reconciliation report that says what came across, what was retired and what is missing. Assurance is replaced by Risk and Compliance, PolicyConnect by policies and procedures with PolicyAI in beta, and CompliLearn by Personnel.
What are the AI paragraphs you are currently missing from your policies? Watch how we do it.
Free, under ten minutes, and yours to keep whether or not you talk to us.
“It meets all of the real frustrations of business directors in one place.”
“School governance and risk is a complex area without a clear solution.”
Tell us your renewal date, and we would beglad to write the twelve weeks back from it.
Migration service for schools leaving CompliSpace: one committed project, timed to the next renewal, with the old system read-only on a date the whole school knows.