Home / Innealla SIS / SIS migration / SITS
SIS migrationSITS to Innealla
Tribal SITS:Vision runs modular programmes, occurrences and assessments for universities across the UK and Ireland. If that depth now costs you specialist staff you cannot hire, Innealla is the lighter cloud SIS: fixed-price SITS migration, parallel run, and Moodle wired without StuTalk as a single point of failure.
Live in under two monthsWritten rollback planIntegrations on day one
Other routes Banner · Quercus · Colleague · Spreadsheets · TSM or Thesis · All SIS migration
One student record from application to transcript, a fixed-price migration that imports your SITS data, and a supplier you can actually talk to. Your current system stays the source of truth until cutover, and we prove the numbers before anyone switches off the old login.
What Innealla does →
Tribal SITS:Vision runs modular programmes, occurrences and assessments for universities across the UK and Ireland. The depth is real; so is the cost of staying on that depth when your college is smaller than the product assumes.
A SITS renewal or re-implementation quote that no longer matches the size of your registry team.
Occurrences, diets and assessment patterns that only a handful of staff can configure safely.
Statutory and exam-board extracts that still need a specialist rather than a saved view.
StuTalk and custom interfaces that are hard to change when Moodle or CRM moves on.
It is not the right move for every SITS estate, and we will say so at discovery.
Colleges that want a system built for how they work, rather than adapted to it, with Moodle and CRM connected from day one.
It is not the right move for everyone, and we will say so at discovery. Complex multi-campus estates take longer than the usual two months, and discovery sets that date before you commit.
If your data cannot move cleanly, the grading shows it table by table, with a clear list of what will migrate cleanly and what needs a decision.
Talk to us →Most SITS moves we run are live in under two months, including a parallel run. We use the APIs and exports your Tribal estate already supports; your exam boards set the calendar.
We take a full SITS export, grade every table from A to G, and give you a fixed price for the migration and a go-live date.
Students, programmes, modules, enrolments, results and fees mapped and cleansed in days.
Innealla and your current system side by side, with reconciliation reports your registry and finance teams can check.
Timed to your academic calendar, usually between intakes, with a rollback plan agreed in writing.
Your current system stays the source of truth until cutover. We prove the numbers before anyone switches off the old login, and if something does not match, the written rollback plan says exactly what happens next.
Start with discovery →Programmes, occurrences, assessments and results are graded table by table at discovery so exam boards know what will land cleanly in Innealla.
Historic enrolments, results and awards come across, so transcripts can be produced from Innealla for past students.
Where the old system holds documents, we migrate them to the student’s record or keep a read-only archive, whichever you prefer.
Our Moodle plugin, the Salesforce managed app or Zoho connector, and GL and payment exports to your finance system are rebuilt on the Integration Hub as part of the fixed price. Anything bespoke is scoped at discovery.
Innealla is a hosted subscription banded by student numbers. At discovery we put those figures beside your Tribal licence and support costs, so the comparison is on paper.
This page is the SITS route. The others below use the same discovery and parallel-run shape, with the specifics for that system. How every SIS migration works →
For colleges approaching a Banner renewal. Your Banner data imported and reconciled, with Banner and Innealla side by side during the parallel run.
Banner to Innealla →For colleges approaching a Unit4 Student Management renewal. Your TSM data imported and reconciled, live in under two months.
TSM or Thesis to Innealla →For colleges approaching a Quercus renewal. A fixed-price migration that imports your Quercus data, live in under two months.
Quercus to Innealla →For colleges approaching a Colleague renewal. Your Colleague data imported and reconciled, with integrations rebuilt on day one.
Colleague to Innealla →Excel, Access and a shared drive. Your spreadsheets are the migration source, taken as they are.
Spreadsheets to SIS →On a hosted subscription banded by student numbers with your rate held for 24 months.
Discovery starts with a full extract of your SITS programmes, occurrences and assessments. It tells you how clean that data is and fixes the price before you commit to anything.
Innealla is built with AI running through it, not bolted on. Staff ask it questions and tell it to do things in plain English, and it works against the live student record within the permissions that person already has.
Innealla owns the student record and the Integration Hub connects it to everything else a college runs. Enrolments, courses and CRM applications are reconnected as part of cutover, not as a later project. We build connectors for a living, so if one is missing we add it.
Our plugin provisions courses, cohorts and enrolments from the curriculum and keeps grades and announcements in step
A managed app we built, so applications and cases flow into the student record without re-keying
The same, for colleges on Zoho CRM
GL journal export to your accounts system, payment providers, sponsor billing
Plus email and SMS
In the core; an existing Celcat export imports for cutover
What to expect through discovery, data grading, parallel run and cutover, and who this kind of migration suits.
Read the article →Dublin Business School, whose Moodle estate we build, integrate and operate.
Read the case study →Yes. Students, applicants, programmes, modules, enrolments, results, awards and fee history all map into Innealla, and the discovery grades each table before anything moves.
Most colleges are live in under two months from the start of discovery, including a parallel run. The migration itself is AI-assisted and measured in days; the calendar is set by your intakes and your sign-off.
Yes. Historic enrolments, results and awards come across so transcripts for past students can be produced from Innealla. Documents are migrated to the student’s record or kept in a read-only archive, whichever you prefer.
Yes. Innealla is built for colleges in Ireland and the UK: awarding-body and partner-university programme structures, progression and classification rules configured without code, and finance that handles instalment plans, sponsors and holds. Hosting is in AWS Ireland under a data processing agreement; talk to us about data residency requirements at discovery.
They are rebuilt on the Integration Hub as part of the fixed price: our Moodle plugin, the Salesforce managed app or Zoho connector, and GL and payment exports to your finance system. Anything bespoke is scoped at discovery.
A fixed-price Innealla Discovery. You get a graded assessment of your data, a migration price and a go-live window before anything is committed.
Book an Innealla Discovery: your data graded from A to G, a fixed migration price and a go-live date, before anything is committed.
SITS-scale structure without SITS-scale staffing.
Occurrences, assessments and fees in one lighter system.
SITS:Vision is the UK (and Irish) university workhorse: modular programmes, occurrences, assessment diets, StuTalk and a specialist market around it. That depth is why big HEIs keep it. It is also why a smaller college ends up waiting on a scarce SITS analyst for every curriculum change.
We map the SITS academic spine, programmes, modules, occurrences, enrolments, assessments and fee records, into Innealla. StuTalk or database extracts are graded in discovery before price is fixed.
After cutover, staff ask Innealla about students, occurrences and fees in plain English. You are not training another generation on SITS forms. How we run AI on college systems.
Yes when SITS is more system than the college needs, or when specialist SITS capacity is the constraint. No when you need a full research-university SITS estate with a dedicated records team. Discovery says which.
Enrolments and grades should move to Moodle without waiting on the one person who knows the SITS jobs. That is what the Integration Hub is for.
See integrations