There is no universal winner between a unified platform and a set of separate, integrated tools for admissions, CRM and student records. None of the guidance reviewed here, from EDUCAUSE, UCISA, Jisc and the Tambellini Group, tells institutions to buy one or the other. Our reading is that the decision turns on three questions: which data must stay in one governed record, which functions genuinely need specialist depth, and how much integration work the institution can sustain. For institutions where recruitment, admissions, enrolment and student records are closely linked, as in business schools, executive education and specialist institutions, a unified platform such as Full Fabric removes institution-managed synchronisation between those stages. Large universities with a deeply embedded ERP-anchored student system often keep it and connect specialist tools around it. Whichever core is chosen, it still connects to finance, HR, learning and identity systems, so many architectures end up hybrid at the edges.
This guide explains the options, what the evidence says, when each one fits and what each one costs over time, and gives IT teams a practical test for vendor demonstrations.
Transparency note. Full Fabric publishes this article and sells a unified platform for CRM, admissions, payments and student records. We have tried to set out the case for each architecture fairly, including the situations where a unified platform is not the right choice.
The terms are used loosely, so it helps to define them before comparing them. The first two describe how the core of the student lifecycle is built: CRM, admissions, enrolment and student records. The third describes how that core connects to the rest of the institution. The options therefore overlap: a unified lifecycle platform can sit at the centre of a hybrid architecture.
Vendor count is not the same as architecture. A suite of products sold by one vendor can still run on separate databases joined by internal integrations, while a well-governed multi-vendor stack can share identifiers and data definitions. Ask whether the products share a lifecycle data model, not only whether they share a logo.
Two related ideas are often confused with these choices:
The development and maintenance of an in-house system is a complex and time-consuming task. Full Fabric lets you turn your full attention to maximizing growth and performance.
None of the sector bodies whose guidance we reviewed recommends a single architecture for every institution. Each focuses on something different, and we summarise our reading of them at the end of this section.
EDUCAUSE published The Integrated Institution: A Guide to Interoperability for Student Success in September 2026. It treats interoperability as a strategic priority rather than a technology project and describes a four-stage spectrum, from disconnected systems with duplicated or manually transferred data to an "active data ecosystem". It also notes that every non-standard, custom integration adds technical debt, and that standards-based data practices are the foundation for analytics and AI. The guide is about making systems work together, whichever architecture an institution chooses.
The 2026 EDUCAUSE Top 10 adds a warning that applies directly to stacks assembled without a plan. Most technology leaders surveyed said that "quick-fix technology purchases" are common at their institution, putting strain on IT staff and reducing interoperability. One of that year's ten issues is making better technology investment decisions through clear cost, ROI and legacy-system assessments.
The Tambellini Group, a higher education technology advisory firm, set out the trade-off for recruitment and admissions systems in Adopting Recruitment and Admissions Solutions (2021). Stand-alone, best-of-breed products can offer richer functionality, but integrating them into a unified experience and data repository takes additional work. Enterprise-wide solutions give a more consistent user experience and usually need less integration, but their functionality may be less rich. The deciding factors it lists are IT staffing and skills, existing data oversight, IT governance over software buying, and campus culture.
UCISA, the UK's member body for digital professionals in higher education, promotes the Higher Education Reference Model (HERM). UCISA describes HERM as standardised business and data architectures that institutions can use as a starter kit, a reference point and a tool for engaging stakeholders. HERM is curated by CAUDIT with EDUCAUSE, UCISA and EUNIS, and EDUCAUSE reports that more than a thousand institutions use it. UCISA's HERM programme includes work on application rationalisation.
Jisc, the UK's digital, data and technology agency for education, frames the issue through data maturity rather than software. Its data maturity framework treats data as an institutional asset and helps institutions assess how well they manage it.
Our synthesis of this guidance, rather than a joint position of these organisations, is that:
Two data sets give a partial picture of how institutions run these systems. Neither measures the adoption of unified lifecycle platforms or of hybrid CRM and admissions architectures directly.
In the UK, UCISA's Trends in Corporate Information Systems 2013–2023 reported that, in 2023, 33 responding institutions (47%) used more than one core CRM, and twelve (17%) used three. The same report found that 42 respondents (56%) used more than one business intelligence system. Some of this is by design, since a fundraising CRM and a recruitment CRM serve different teams, but it shows how relationship data can spread across systems. Each year's survey has around 70 responding institutions, so treat the figures as indicative.
In North America, ListEdTech's June 2026 analysis, Best of Breed versus Best of Suite, looked at the SIS and ERP vendors of nearly 4,500 institutions in the United States and Canada. It found that 22% use more than one vendor for these core systems, up from 14% in 2019. Size is the main driver: 15% of institutions with fewer than 2,500 students use multiple vendors, compared with 59% of those with more than 30,000. These are vendor counts for SIS and ERP only, in North America. They do not cover CRM or admissions, and they do not show whether systems share a data model, but they suggest that smaller institutions tend to consolidate core systems and the largest tend to assemble them.
The table summarises typical trade-offs for the CRM, admissions and student records core. Individual products and implementations vary, so use it to frame questions for vendors rather than as a verdict.
| Criterion | Unified platform | Best-of-breed (separate tools) | Hybrid |
|---|---|---|---|
| Data model across the lifecycle | Shared person identity and profile, with applications, enrolments and records linked to it | A record in each system, linked by identifiers and integrations | Shared model in the core, with connected systems for selected functions |
| Integration effort | No institution-managed sync between lifecycle stages on the platform; still needed for finance, HR, VLE and identity | Higher; each hand-off between stages is an integration to build, monitor and maintain | Depends on how much sits in the core and how many systems connect to it |
| Functional depth | Broad; depth varies by module and vendor | Can be deeper in a specialist area, depending on the product | Specialist depth where specialist tools are kept |
| Reporting across the funnel | From one lifecycle data set | Through supported integrations, shared analytics, a warehouse or reconciled exports | Native for the core; combined with other sources for the rest |
| Student and applicant experience | Can offer one portal and communication history, depending on the product | Can feel fragmented across logins and portals unless designed carefully | Consistent for the core journey |
| IT skills needed | Configuration, vendor management and governance | Integration engineering, monitoring and data governance across several vendors | Both, at a scale that depends on the design |
| Vendor dependency | High on one vendor's roadmap | Spread across several vendors, with more contracts to manage | Concentrated in the core, spread at the edges |
| Change and upgrades | One upgrade path for the core | Each upgrade needs compatibility checks and testing for affected integrations, and rework where interfaces change | Fewer lifecycle integrations to test |
| Typical fit | Institutions where recruitment, admissions and records are tightly linked | Large institutions with strong integration teams and deeply embedded systems | A common approach at institutions that keep some specialist systems |
The right answer depends on the institution's structure, its existing systems and the capacity of its IT team. These scenarios cover the most common situations.
A hybrid is a common approach, particularly where some systems are too embedded or too specialised to replace. A typical pattern is to keep the stages that share the most data, usually enquiry, application, offer, deposit and enrolment, on one core, and connect that core to finance, HR, the VLE, identity management and, where one exists, an institution-wide fundraising or enterprise CRM.
Licence fees are the most visible cost, but over five years they are often not the only significant one. Both architectures carry costs that do not appear on the first quote.
UK institutions have a specific reason to look at how their student data flows: student data collection is moving to an in-year model. The Office for Students says in-year collection will be introduced across the UK, working with Jisc and the funding and regulatory bodies in Scotland, Wales and Northern Ireland (OfS in-year data collection programme). Obligations will depend on each provider's regulator and type, so check what applies to your institution.
In its June 2026 letter to accountable officers, the OfS set out the timetable as it stood: Jisc was due to publish the in-year data model for 2028-29 returns in July 2026; providers and software suppliers would develop systems during 2026-27; structured testing would begin in autumn 2027; and the first full in-year collection would take place in winter 2028. The letter says the scale of change will vary significantly depending on each provider's current systems and data architecture, and that some providers may need substantial system development or supplier engagement.
More frequent returns favour institutions where applicant, enrolment and student data is consistent and up to date. Whichever architecture you choose, check how quickly and reliably data reaches the system that produces the return.
Slide decks and feature lists do not show how an architecture behaves. Ask each shortlisted vendor, or each combination of vendors, to run the same end-to-end demonstration with synthetic or appropriately anonymised data that reflects your real programmes and volumes:
Then test what happens when something goes wrong:
Watch for re-keyed data, manual exports and steps where a vendor says "the integration handles that" without showing it. Batch updates are not a problem in themselves; judge latency against what each process actually needs.
Then ask these questions:
Full Fabric is a unified platform for higher education. CRM, admissions, enrolment, payments and student records run on a single data model built around one student record, so the same person is followed from enquiry to applicant to student. Our higher education CRM platform and student information system share that record, so there is no institution-managed synchronisation between recruitment, admissions and the student record. It is used mainly by business schools, executive education providers, conservatoires and specialist and international institutions.
It can sit in either of two places in an architecture:
What is documented today, in our Help Centre and API documentation:
Full Fabric is not the right choice in every architecture. A large university that wants to keep an ERP-anchored student system and only needs a recruitment CRM may prefer a CRM-only product. An institution that wants one enterprise CRM for recruitment, fundraising and corporate relations may standardise on Salesforce or Microsoft Dynamics and use Full Fabric for admissions. With Salesforce, the native connector sends data one way into the CRM; with Dynamics, until the native connector is available, the connection would be an API or middleware integration that the institution designs and maintains. Our integrations and ecosystem overview explains the integration options in more detail.
The question is not whether one vendor or many is better in principle. It is which data must stay in one governed record, which functions need specialist depth, and how much integration work the institution can maintain for the next five to ten years.
For institutions where recruitment, admissions and records are closely linked, a unified platform can reduce integration overhead and the risk of records drifting apart between stages. For large institutions with deeply embedded systems and strong integration teams, a well-governed best-of-breed or hybrid stack can work well. Either way, an end-to-end demonstration with realistic data will tell you more than any architecture diagram.
To see how a unified platform handles the journey from enquiry to enrolment, book a demo with Full Fabric.
It depends on how closely those stages are linked and how much integration work the institution can sustain. A unified platform suits institutions where applicants become students quickly and IT capacity is limited. Integrating separate tools suits large institutions with deeply embedded systems and strong integration teams. Many institutions combine the two: a core for the lifecycle, connected to specialist systems around it.
None of the sector guidance reviewed here recommends one architecture for every institution. EDUCAUSE focuses on interoperability, and its 2026 Top 10 reports that most technology leaders see "quick-fix technology purchases" as common, straining IT staff and reducing interoperability. UCISA promotes the HERM reference model and Jisc a data maturity framework. The Tambellini Group sums up the trade-off: specialist tools can be richer but need more integration; enterprise-wide solutions are more consistent but may be less deep.
A hybrid architecture uses a core, either a unified platform or a small set of tightly integrated systems, for the records that must stay consistent, typically enquiry, application, offer, enrolment and the student record. Specialist systems are connected around it for finance, HR, the VLE, identity management or fundraising. A unified lifecycle platform can therefore be the core of a hybrid architecture.
No. A single source of truth means each data object has one authoritative owner. A unified platform makes this easier for lifecycle data because the stages share one data model, but a well-governed best-of-breed stack can also achieve it. What matters is that two systems never claim to own the same field.
The main hidden costs are building and maintaining integrations, resolving duplicate or conflicting records, reconciling data for reports, and managing several vendors, contracts and security reviews. When either connected product changes, integrations need compatibility checks and testing, and rework where interfaces or behaviour change.
Before signing, ask how data is exported, in what format and at what cost; prefer configuration over custom code; and check for documented APIs. For cloud services provided to customers in the EU, the Data Act gives switching rights and, from 12 January 2027, bans switching charges, though this does not eliminate standard service fees, applicable early termination penalties, internal migration effort or independent third-party implementation costs.
Best-of-breed is usually better when the student system is deeply embedded in an ERP suite, when a specialist need is not met by any suite, and when the institution has the integration engineers, middleware and governance to run a multi-vendor stack reliably.
Yes, within documented limits. Full Fabric's native Salesforce and HubSpot connectors send data one way, from Full Fabric to the CRM; a native Microsoft Dynamics connector is listed as coming soon. Other systems, including another student information system or a CRM without a native connector, can be connected through the REST API, which can read and write data, and outbound webhooks. Those API integrations are built and managed by the institution or its agency.