Home / Innealla SIS / SIS migration / TSM or Thesis
SIS migrationUnit4 Student Management to Innealla
Still on Unit4 Student Management (also called TSM or Thesis)? Innealla is a cloud SIS for Irish and UK colleges: one student record from application to transcript, a fixed-price migration of your data, and engineers who answer the phone. Also see Unit4.
Live in under two monthsWritten rollback planIntegrations on day one
Other routes Unit4 · Banner · SITS · Quercus · Colleague · Spreadsheets · All SIS migration
One student record from application to transcript, a fixed-price migration that imports your TSM 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 →
We have integrated with TSM for years through its APIs, so we know what it holds and how colleges use it. The reasons a college starts looking elsewhere are usually practical rather than dramatic.
A platform transition or end-of-life on the horizon, with a re-implementation cost that invites the question of whether to re-implement at all.
Fee, instalment, sponsor and QQI or Ofqual processes handled in spreadsheets beside the system.
Reporting that needs an export and a developer rather than a question asked in plain English.
Moodle, CRM, timetabling and finance each holding their own copy of the student, with staff re-keying between them.
A support model built for large institutions, when you need a named engineer who knows your set-up.
Wanting AI that works on the live student record without student data leaving the platform.
It is not the right move for everyone, 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 colleges are live in under two months, including a parallel run. The migration itself takes days; your intakes and your sign-off set the calendar.
We take a full 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 →Everything a registry relies on has a home in Innealla, and discovery tells you exactly how clean yours is before it moves.
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 the figures beside your current licence, hosting and support costs, so the comparison is on paper, not in a sales pitch.
Each route has its own page, 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 SITS renewal. Your SITS data imported and reconciled into a system built for Irish colleges.
SITS 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.
Because we already read TSM data through its APIs for integration work, the extraction side of a migration is well trodden. The discovery tells you how clean your 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. We have worked with the TSM APIs for integration projects for years, so extraction is a known process. 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.
Your Unit4 / TSM data, imported and reconciled,
in a student information system built for colleges
Same system whether your team says Unit4, TSM or Thesis. The usual trigger is practical: renewal cost, spreadsheet workarounds, or integrations that never quite settled.
Searching for TSM or Thesis? Same move: TSM or Thesis to Innealla.
We have read Unit4 / TSM data through its APIs on integration work for years, so extraction is familiar. Discovery grades every table and locks the price before you commit.
Staff query students and fees in Innealla after cutover. How we run AI on college systems.
It usually is when the college has a few hundred to several thousand students, runs programmes under QQI, Ofqual or a partner university, and wants a system shaped around how it actually works. We will say so if it is not.
We have read TSM through its APIs for years on integration work. After cutover, Moodle and CRM sit on the Integration Hub instead of one-off TSM jobs.
See integrations