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.

The Integration Hub in Innealla

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
See our integrations →

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.

⇄

SIS to Moodle

Student information systems to Moodle and other VLEs.

◔

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.

01

Fixed scope

An acceptance test for every integration, agreed before the build starts.

02

Documented

Monitored and supportable by someone other than the person who built it.

03

Least privilege

Logged, with no shared passwords.

04

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
Read the case study →

Proof

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

software developer

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
Request a review

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
Talk to us
strategic consulting

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
Discuss a project

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
See our integrations
AI & Intelligent automation

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
Read the case study

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.

Frequently Asked Questions