SIS to Moodle
Student information systems to Moodle and other VLEs.
Home / Solutions / Connected campus
Connected campusIntegration
Connect the systems you already have.
Student records, Moodle, CRM, timetabling, finance and service desk working as one. We build the integrations between them and look after them.
Not tied to a vendorDocumented and monitoredInnealla or your SIS
The problem
A typical college runs systems from different suppliers and different decades.
Student recordsMoodleCRMTimetablingFinanceService desk
Staff re-key data between them, and students have to know which system holds what.
Who it is for
Platforms we work with.
We are not tied to a vendor. These are the ones we have connected most often.
- Innealla, our own student record system, and other SIS platforms
- Moodle and Iomad
- Salesforce and Moodle, Zoho and HubSpot
- Celcat timetabling
- Microsoft 365 and Google Workspace
- Sitefinity and WordPress
- Payment providers and finance systems
What we connect
One college, many systems, one set of integrations.
The student record sits at the centre, whether that is Innealla or the SIS you already have.
Attendance
Attendance to timetables and student records.
CRM
CRM to admissions, payments and enrolment.
Service desks
Service desks to student data.
Microsoft 365 and Google
Microsoft 365 and Google Workspace to everything else.
Portals and AI
Intranets and portals to AI assistants.
How we work
Integrations fail when only one person understands them.
Ours are built so that is never the case.
Fixed scope
An acceptance test for every integration, agreed before the build starts.
Documented
Monitored and supportable by someone other than the person who built it.
Least privilege
Logged, with no shared passwords.
Embedded where needed
Integration engineers with your SIS or CRM programme for 6 to 24 months.
⇄
Built on the Integration HubA connector built for one college becomes available to every other college on the hub.
Start here
Start with an Integration Review.
Two weeks, fixed price. You get a map of what you have and a plan you can act on, with us or without us.
2 weeksFixed priceReport for IT
Book an Integration Review →What you get
- Every system and interface mapped
- What breaks, what is manual, what is undocumented
- Fixes ranked by value and effort
- A short report for IT and the senior team
Case study
Built for Dublin Business School.
Moodle, attendance, payments and Salesforce working across one estate.
- Multi-tenant Moodle estate
- RFID attendance tied to timetables and records
- Student service desk on Salesforce, connected to student data
- Automated release pipeline for every system we maintain
Proof
A partner for the work, not another supplier.
Dublin Business School, from Moodle and attendance to payments and Salesforce.
“Inneall are very solutions driven. They find better ways of doing things. I can throw an idea at them and they’ll find a way to do it.”
EO
Read the DBS case study →Edward OrmondeHead of IT, Dublin Business School
CASE STUDY
A technology partnership at the heart of DBS’s digital ambition
Read more →
AI AT INNEALL
Lugh: the AI agent that answers our service desk first
Read more →
AI AT INNEALL
The Ops Agent: how our servers are checked every morning before anyone logs in
Read more →Do you have preferred platforms you always recommend?
We know Moodle, Salesforce, Zoho, Sitefinity and Celcat well because they have proven themselves in colleges. We are not tied to any vendor. We start from what you need and what you already have, and we will tell you plainly if an existing platform is the right answer.
Can you help with the redesign of internal workflows?
Yes. Before we configure or build anything we sit with the people who do the work and map how it actually happens, not how the process document says it happens. We find the duplication and the friction, then design the workflow the technology will support. Better systems on broken processes do not give better outcomes.
Will off-the-shelf software meet all our needs?
Sometimes, rarely entirely. Established platforms are proven, maintainable and cost effective, but colleges have processes, compliance requirements and integrations that generic software does not cover out of the box. We use the platform where it fits and build the missing pieces where it does not, then connect everything so it works as one system.
How long does a typical project take?
A focused integration or workflow automation can be live in weeks. A full programme across recruitment, student records, learning and reporting usually runs six to twelve months. Every project is broken into short phases so you see working software early and can change direction while it is still cheap to do so.
Where is our data held and how is it protected?
Systems we host run in AWS in Ireland, with backups, monitoring and access controls in place, and we can also run inside your own AWS or Azure account. We sign a data processing agreement with every client. We are working towards ISO/IEC 27001 certification and can share our security practices on request.
Next step
Connect the systems you already have.
Two weeks, a fixed price, and a map of every integration you need, ranked by value and effort.
Integrators for specialised education and CRM platforms
- Moodle
- Salesforce
- Zoho
- HubSpot
- Sitefinity
- Celcat
- Microsoft 365
- AWS
One college, many systems,
one set of integrations
Start with an Integration Review
Two weeks, fixed price. You get a map of what you have and a plan you can act on, with us or without us.
- Every system and interface mapped
- What breaks, what is manual, what is undocumented
- Fixes ranked by value and effort
- A short report for IT and the senior team
What we connect
A typical college runs systems from different suppliers and different decades. Staff re-key data between them, and students have to know which system holds what. The student record sits at the centre, whether that is Innealla or the SIS you already have.
- Student information systems to Moodle and other VLEs
- Attendance to timetables and student records
- CRM to admissions, payments and enrolment
- Service desks to student data
- Microsoft 365 and Google Workspace to everything else
- Intranets and portals to AI assistants
How we work
Integrations fail when only one person understands them. Ours are built so that is never the case.
- Fixed scope and an acceptance test for every integration
- Documented, monitored and supportable by someone other than the person who built it
- Least privilege, logged, no shared passwords
- Integration engineers embedded with your SIS or CRM programme for 6 to 24 months where needed
Platforms we work with
We are not tied to a vendor. These are the ones we have connected most often.
- Innealla, our own student record system, and other SIS platforms — see SIS migration
- Moodle and Iomad
- Salesforce and Moodle, Zoho and HubSpot
- Celcat timetabling
- Microsoft 365 and Google Workspace
- Sitefinity and WordPress
- Payment providers and finance systems
Built for Dublin Business School
Moodle, attendance, payments and Salesforce working across one estate.
- Multi-tenant Moodle estate
- RFID attendance tied to timetables and records
- Student service desk on Salesforce, connected to student data
- Automated release pipeline for every system we maintain
How we do things
Partnership, transparency, user-centred design and long-term quality guide every project. Each one runs through the same six stages, so you always know where it stands and who is accountable.
DISCOVER
Audit and workshops
Scope of work
Integration mapping
Risk and dependency analysis
Finalised project plan
Scope of work
Integration mapping
Risk and dependency analysis
Finalised project plan
DESIGN
User experience
Concept proposals
Stakeholder reviews
Design development
Final specifications
Approval to progress
Concept proposals
Stakeholder reviews
Design development
Final specifications
Approval to progress
BUILD
Software development
System integration
Customisations
Content and data migration
Front end interface
System integration
Customisations
Content and data migration
Front end interface
TEST
Functional and user acceptance testing
Browser/app performance testing
Accessibility
System and security
Browser/app performance testing
Accessibility
System and security
DEPLOY
Training
Final configuration and domain go-live
Hypercare in the first weeks
Bug-fix support
Handover to support
Final configuration and domain go-live
Hypercare in the first weeks
Bug-fix support
Handover to support
SUPPORT
Tailored service level agreements
Responsive support
Planned maintenance
Quality control
Performance tuning
Responsive support
Planned maintenance
Quality control
Performance tuning
Discover how we think,
deliver and make an impact
View more
We love API environments
and the challenge of integration
We’ve integrated systems others refused to touch!
“Inneall’s impact on our ability to deliver reliable, scalable technology has been absolutely enormous. What sets them apart is their deep knowledge of our business, they understand our systems, our teams, and our priorities. That means we’re not dealing with a technology supplier; we’re working with a partner who genuinely cares about getting it right.”
Edward Ormonde
Head of IT, Dublin Business School
Frequently Asked Questions
Do you have preferred platforms you always recommend?
We know Moodle, Salesforce, Zoho, Sitefinity and Celcat well because they have proven themselves in colleges. We are not tied to any vendor. We start from what you need and what you already have, and we will tell you plainly if an existing platform is the right answer.
Can you help with the redesign of internal workflows?
Yes. Before we configure or build anything we sit with the people who do the work and map how it actually happens, not how the process document says it happens. We find the duplication and the friction, then design the workflow the technology will support. Better systems on broken processes do not give better outcomes.
Will off the shelf software meet all our needs?
Sometimes, rarely entirely. Established platforms are proven, maintainable and cost effective, but colleges have processes, compliance requirements and integrations that generic software does not cover out of the box. We use the platform where it fits and build the missing pieces where it does not, then connect everything so it works as one system.
How long does a typical project take?
A focused integration or workflow automation can be live in weeks. A full programme across recruitment, student records, learning and reporting usually runs six to twelve months. Every project is broken into short phases so you see working software early and can change direction while it is still cheap to do so.
Where is our data held and how is it protected?
Systems we host run in AWS in Ireland, with backups, monitoring and access controls in place, and we can also run inside your own AWS or Azure account. We sign a data processing agreement with every client. We are working towards ISO/IEC 27001 certification and can share our security practices on request.