WEBINAR @ 13th May, 2 PM (GMT+1)
What's Stopping Progress in Higher Education?
Register now
Salesforce is one of the most capable enterprise CRM ecosystems available to European universities, and for some institutions it is the right choice. For others, the configuration, cost and governance it requires outweigh the benefits, and a purpose-built higher education platform is a better operational fit. This article is a balanced evaluation to help you decide which camp you are in.
European universities are under pressure to modernise recruitment, admissions, student engagement, reporting and lifecycle management. Salesforce is often on the shortlist because it is a powerful, global platform with Education Cloud, workflow automation, analytics, a growing set of AI capabilities and a very large partner network. At the same time, European institutions operate under specific constraints that a generic CRM decision does not always account for: the GDPR, data residency and cross-border transfer governance, public procurement rules, legacy student information systems (SIS) and learning management systems (LMS), fragmented admissions and student records, limited internal development capacity, budget scrutiny, staff adoption, and multilingual, multi-country operations. Sector bodies such as Jisc position this modernisation within a broader agenda for digital transformation in higher education (Jisc, Framework for digital transformation in higher education).
The purpose here is not to argue that Salesforce is good or bad. It is to set out where Salesforce can be a strong fit, where it can create complexity, what European universities should evaluate before committing, what alternatives exist, and how a purpose-built platform such as Full Fabric compares. Throughout, the aim is to be fair to Salesforce, cautious about compliance claims, and specific about the questions that matter.
Salesforce Education Cloud is Salesforce's industry cloud for education, built on the core Salesforce platform and designed to support engagement, recruitment, student success and related education workflows. Salesforce describes it as a unified platform that combines CRM for education with what it calls next-generation SIS capabilities, using platform innovations such as agentic AI and analytics (Salesforce Education Cloud).
According to Salesforce, Education Cloud is organised into modules that map to stages of the learner journey, including Recruitment and Admissions, Academic Operations, Student Success, Student Financials, and Advancement and Alumni Relations (Salesforce Education Cloud guide). Rather than running on the older Education Data Architecture managed package, current Education Cloud uses an education data foundation built natively on the core platform, with education-specific objects such as courses and programme structures. This matters for European buyers because it shapes the data model your teams will work in and the configuration effort involved.
Two points deserve care. First, Salesforce positions Education Cloud as a CRM platform with SIS capabilities that are being built and released over time, describing itself as "embarking on a transformative journey to build a next-generation student information system on Education Cloud" and releasing modular capabilities incrementally (Salesforce, What Is Education Cloud?). Some SIS-adjacent functions, such as course registration and waitlist handling, have been released, while others remain on the roadmap. This means Education Cloud should not be treated as a like-for-like replacement for a mature institutional SIS without verifying which specific capabilities are generally available and appropriate for your record-keeping, compliance and reporting needs.
Second, the terminology is easy to blur. A CRM manages relationships and engagement across prospects, applicants, students and alumni. An SIS is the system of record for enrolment, academic records and compliance reporting. An LMS delivers teaching and learning. An ERP or finance system handles institutional finance, HR and procurement. Education Cloud spans CRM and, increasingly, parts of the SIS domain, but it is not an ERP or an LMS. Keeping these categories distinct is essential when scoping a project and comparing platforms.
The strongest reasons European institutions consider Salesforce are the same reasons large enterprises across sectors do. It is a mature enterprise CRM with a very large ecosystem, deep configurability, strong workflow automation, and extensive reporting and analytics. It can support cross-functional use cases in a single platform, spanning recruitment, admissions, student services, alumni relations and advancement, marketing and support. It has a substantial partner and consultant ecosystem, broad integration capabilities through well-documented APIs, strong brand recognition, and the scale to serve very large, multi-country institutions.
These are real advantages. The important qualifier is that the value depends heavily on implementation quality, governance and institutional readiness. Salesforce is a platform you configure, not a product you switch on. The same flexibility that makes it powerful is what makes outcomes so dependent on how well the programme is scoped, designed and run.
Salesforce is a proven, mature CRM used at enterprise scale worldwide. For universities with large and complex relationship-management needs across many teams, that maturity brings reliability, a deep feature set, and a well-understood administration model. Salesforce itself frames Education Cloud as eliminating the pain of disparate data by bringing constituent information into a unified view (Salesforce for Education).
Few platforms match Salesforce for the availability of skills, apps, consultants and implementation partners. For institutions that want to hire experienced administrators, engage certified partners, or draw on a large community, this ecosystem reduces the risk of being unable to find help. It also means a wide marketplace of add-ons and pre-built solutions, including education-focused offerings from specialist partners.
Because Salesforce is a horizontal platform, it can be shaped to support recruitment, admissions, student services, alumni engagement, advancement, marketing and case management within one environment. Institutions that want to standardise several CRM-style functions on a single vendor often find this appealing, particularly where advancement, alumni or marketing teams are already invested in Salesforce.
Salesforce offers workflow automation, reporting and analytics, and a growing set of AI capabilities marketed under Agentforce for handling constituent queries and supporting staff (Salesforce Education Cloud). Used well, these can reduce manual work and surface insight across the funnel. The caveat, covered in detail below, is that AI value depends on data governance and, in Europe, on careful attention to the regulatory framework for high-impact uses.
Salesforce provides extensive APIs and integration tooling, giving institutions the ability to connect it with an SIS, LMS, finance, identity and business-intelligence systems. For organisations with the engineering capacity to build and maintain these connections, this extensibility is a genuine strength.
For large, multi-country institutions, Salesforce offers scale and a widely recognised operating model. Staff who have used Salesforce elsewhere arrive with transferable skills, and the platform can support operations across many campuses and regions.
This section is deliberately direct, but it is not an argument against Salesforce. It is a summary of the risks European institutions should plan for.
Salesforce is highly configurable, which is both a strength and a risk. A typical higher education implementation involves discovery, solution architecture, data-model design, data migration, integrations, testing, governance, user training and change management. Each of these can be substantial. The flexibility that lets Salesforce fit many use cases also means there is a large design space to get right, and getting it wrong is expensive to unwind.
Running Salesforce well usually requires ongoing access to administrators, and often architects, developers or an implementation partner. Day-to-day changes such as new application stages, revised workflows or new report types may need specialist input. This is not a criticism of the platform, but it is an operating-model choice: institutions should be clear about whether they can staff this internally or will depend on partners, and should avoid making assumptions about exact staffing levels without validating them for their own scope.
The cost of Salesforce extends well beyond licences. Institutions should model add-ons, implementation, partner fees, integrations, training, support, ongoing administration, governance and the cost of future changes. Rather than relying on figures quoted second-hand, pricing and packaging should be evaluated directly with Salesforce and its implementation partners, and total cost of ownership should be assessed over a multi-year horizon rather than at the point of purchase.
As a horizontal platform, Salesforce can be shaped to higher education, but that shaping is design work. Concepts that are native to a purpose-built platform, such as programmes, intakes, cohorts, applicants, offers, deposits, conditional offers, deferrals, student records, executive education and lifelong learning, may need to be modelled and configured. Institutions should verify how closely the education data foundation matches their specific admissions and record structures, and how much configuration is required to close the gap.
If Salesforce is introduced without a clear integration and consolidation plan, it can become another layer on top of an already fragmented estate rather than a simplification of it. Where the SIS, LMS, finance and payment systems remain separate, the institution still has to build and maintain the connections between them. The goal of a single view of the learner is achievable, but only with deliberate integration design.
This is critical for European universities and is covered in a dedicated section below. In short, Salesforce offers EU data residency options and a well-documented compliance posture, but data residency is not the same as data sovereignty, and cross-border transfer questions still require legal and technical review. Data protection officers and legal teams should be involved early.
Many European universities are public bodies subject to procurement rules. A Salesforce programme should be scoped with tender requirements, vendor lock-in, exit strategy, data portability, accessibility, security review and long-term maintainability in mind. These considerations are as important as functionality and should be built into the evaluation, not treated as afterthoughts.
Powerful platforms only deliver value if people use them. Admissions teams in particular need fast, usable workflows during peak cycles. Over-customisation, unclear process design and insufficient training are common reasons adoption falls short. Designing for non-technical users, and fixing process before automating it, materially affects the return on any CRM investment.
European universities process significant volumes of sensitive personal data about applicants and students. This can include identity information, academic history, admissions decisions, communications, support needs, payment references, visa and international-student data, and, in some contexts, special category data. That makes data protection due diligence central to any Salesforce decision. Nothing here is legal advice; treat it as an evaluation checklist to work through with your own data protection officer and legal team.
Salesforce provides a documented set of privacy and residency options. Its Hyperforce EU Operating Zone is designed to store and process EU customer data within the EU, with limited exceptions, and to provide 24/7 support delivered by EU-based personnel for a vetted set of products (Salesforce, Hyperforce EU Operating Zone). Hyperforce itself is Salesforce's public-cloud infrastructure architecture, delivered as code on major cloud providers, which Salesforce says gives customers more choice and control over where data is stored and processed (Salesforce operating zone). Salesforce is also certified under the EU-US Data Privacy Framework, the adequacy mechanism the European Commission adopted in July 2023 following the Schrems II ruling (Salesforce transatlantic data privacy update).
Two things follow from this. First, Salesforce clearly can be used in a GDPR-compliant way, and it publishes the mechanisms to support that. Second, and just as important, data residency is not the same as full data sovereignty. Storing data in the EU addresses where data physically lives, but it does not by itself resolve every question about who could compel access to it, particularly given that Salesforce is a US-headquartered company. This distinction is a recognised part of vendor risk assessment and is one your DPO and legal team should evaluate on the facts of your deployment.
Practical due-diligence areas to work through include: the controller and processor roles for each processing activity; the terms of the Salesforce Data Processing Addendum; where data will reside and which products qualify for EU-only storage and processing; what international transfers occur and which mechanism covers them; whether Standard Contractual Clauses and any supplementary measures are needed; the list of sub-processors and audit rights; encryption, access control and role-based permissions; retention and deletion; breach notification; lawful basis and data minimisation; the handling of data subject rights; and whether a Data Protection Impact Assessment (DPIA) is required.
For the underlying rules, refer to primary sources. The European Commission maintains the Standard Contractual Clauses, adopted on 4 June 2021, for transfers of personal data to countries outside the EEA that lack an adequacy decision (European Commission, Standard Contractual Clauses). The European Data Protection Board's guidance on international transfers and supplementary measures is the reference point for assessing whether SCCs alone are sufficient in a given case. Salesforce's own Data Processing Addendum and privacy documentation set out its contractual and technical commitments. Reading these alongside your institution's own policies is the right basis for a decision.
Salesforce markets AI capabilities for education through Agentforce, including agents intended to answer prospective-student questions and support advising and staff productivity (Salesforce Education Cloud). These can be useful, but AI in a European university setting carries specific obligations that apply regardless of vendor.
The value of any AI depends on the quality and governance of the data behind it. Sector research such as the EDUCAUSE Top 10 has identified the data-empowered institution as a strategic priority, and sound data governance is a prerequisite for using AI well (EDUCAUSE, 2025 EDUCAUSE Top 10: The Data-Empowered Institution). Beyond that, the EU AI Act is directly relevant where AI is used in education or vocational training. Its Annex III classifies as high-risk those AI systems intended to determine access or admission to educational and vocational training institutions, to evaluate learning outcomes, to assess the appropriate level of education a person will receive, and to monitor and detect prohibited behaviour during tests (European Commission AI Act Service Desk, Annex III; Regulation (EU) 2024/1689, EUR-Lex). High-risk systems attract obligations covering risk management, data governance, technical documentation, logging, transparency, human oversight, and accuracy, robustness and cybersecurity, with distinct responsibilities for the provider and the deployer of the system.
The practical implications are significant. Admissions decisions, learning-outcome assessment and progression decisions are precisely the areas where caution is warranted. AI should not make admissions decisions autonomously. Human oversight, transparency to applicants and students, accuracy, auditability and appropriate access controls all matter. It is worth stressing that no vendor's AI is automatically compliant, and that includes both Salesforce's AI and the contextual AI embedded in purpose-built platforms such as Full Fabric. Compliance is a function of how a system is designed, deployed and governed within your institution, not a badge a product carries. Timelines and detailed obligations under the Act continue to be refined, so verify the current position against the official sources rather than relying on summaries.
Salesforce can be a strong choice in a number of clearly identifiable situations. These include large universities with mature IT and CRM teams that can staff administration and governance internally; institutions already invested in Salesforce, where advancement, alumni, marketing or service teams are standardised on the platform; institutions that genuinely want one enterprise CRM spanning multiple non-academic functions; and institutions with the budget and governance capacity to run a major, multi-year CRM programme with the discipline it requires. It also suits institutions willing to invest in architecture, integration and change management, and those whose workflow requirements are so specific that they need customisation beyond what higher education templates provide.
Where these conditions hold, Salesforce's configurability, ecosystem and scale are assets rather than liabilities, and the platform can deliver a great deal.
Equally, there are situations where an institution should evaluate alternatives rather than default to Salesforce. These include cases where admissions teams need a fast implementation with low technical dependency; where the institution wants CRM, admissions, payments and student records connected out of the box rather than assembled; where internal Salesforce expertise is limited; where the budget cannot comfortably absorb implementation and long-term administration; where there is no appetite to manage a complex partner-led build; where lifecycle visibility from enquiry to enrolment matters more than general CRM extensibility; and where business schools or executive education teams need configurable programmes, cohorts, applications, payments and learner records without heavy customisation.
None of this means "avoid Salesforce". It means that in these circumstances the evaluation should genuinely include purpose-built higher education platforms alongside Salesforce, judged against day-to-day operational reality rather than feature lists alone.
A useful way to structure an evaluation is to test each option against the operational requirements that matter most to European universities. A strong alternative should support:
The alternatives below are worth evaluating depending on your requirements. The right shortlist depends on scope, existing systems, internal capacity and whether you need a horizontal enterprise platform or a purpose-built lifecycle platform. None of these should be overstated, and capabilities should be verified directly with each vendor.
1. Full Fabric. Best suited to universities, business schools and executive education providers that want CRM, admissions, payments, student records and reporting connected around one learner record. Strengths lie in higher education fit and lifecycle continuity; the main consideration is that it is a focused higher education platform rather than a general-purpose enterprise CRM or a full ERP. Covered in detail in the next section.
2. Microsoft Dynamics 365 and the Power Platform. Best suited to institutions already invested in Microsoft, wanting a configurable enterprise CRM with strong integration into Microsoft 365 and Azure. Strengths include familiarity and extensibility; the consideration is that, like Salesforce, it is a horizontal platform that requires configuration and often partner involvement to fit higher education. Full Fabric offers a Microsoft Dynamics connector for institutions that keep Dynamics as their CRM of record.
3. Ellucian CRM and SIS ecosystem. Best suited to institutions wanting a higher education-specific vendor spanning SIS and CRM, particularly those already running Ellucian systems. Strengths lie in sector focus and breadth; considerations include the scale and integration effort of adopting a large suite. See Full Fabric versus Ellucian for a focused comparison.
4. Oracle Student and Oracle CX ecosystem. Best suited to large institutions already committed to Oracle for finance or student systems. Strengths include enterprise scale and integration within the Oracle stack; considerations mirror those of any large enterprise programme.
5. Unit4. Best suited, in parts of Europe, to institutions looking at student management alongside ERP and finance. Relevance depends heavily on region and on how student management maps to your admissions and CRM needs.
6. Slate. Best suited to admissions and enrolment management, especially in North America but with European adoption. Strengths lie in admissions depth; considerations include fit with wider lifecycle and student-record needs. See Full Fabric versus Slate.
7. HubSpot. Best suited to marketing and recruitment CRM, particularly for lead generation and nurture. Strengths include ease of use and marketing tooling; the consideration is that it is not a higher education SIS or admissions platform. Full Fabric provides a HubSpot connector where institutions keep HubSpot for marketing.
8. DreamApply. Best suited to international admissions, especially high-volume cross-border recruitment. Strengths lie in international application handling; considerations include breadth across the wider lifecycle. See Full Fabric versus DreamApply.
9. Anthology and other higher education suites. Best suited to institutions wanting broad higher education suites spanning several functions. Relevance and fit vary by product and region and should be verified directly.
10. Local and specialist European platforms. In several European markets there are credible national or specialist platforms built around local admissions and compliance requirements. These are worth including where they reflect the specific regulatory and operational context you work in.
Full Fabric is a purpose-built higher education platform that connects CRM, admissions, enrolment, payments, student records and reporting around one connected learner record. The contrast with Salesforce is straightforward and does not require overstating either side. Salesforce is a broad enterprise CRM platform that can be configured for higher education. Full Fabric is built specifically for the higher education lifecycle, on a single data model designed around it from the outset.
Full Fabric describes its architecture as one platform, one student record and one lifecycle, in which an enquiry becomes an application, then an offer, then an enrolment, then a student record, without re-keying data or migrating between systems at each transition (Full Fabric, higher education CRM platform). The areas where this focus tends to matter most are: admissions and enrolment teams that want purpose-built workflows; business schools, public universities and executive education providers with diverse programme portfolios; institutions that want CRM, applications, payments and student records connected from the start rather than assembled; teams that want to own configuration without building a custom Salesforce architecture; European institutions with clear GDPR, security and data governance requirements; and institutions that need lifecycle reporting from enquiry through enrolment and into the student record.
The relevant capabilities span higher education CRM, admissions CRM, admissions and enrolment software, a student information and management system, built-in payments and commerce, reporting and dashboards, integrations, contextual AI, and security and GDPR support for European institutions. Full Fabric states that its GDPR-ready architecture is hosted on AWS, uses TLS 1.2 or higher encryption, and provides data subject access request handling, consent tracking, data retention controls and role-based access, while noting that compliance ultimately depends on how each institution configures and uses the platform.
It is important to be transparent about scope. Full Fabric is not a replacement for every ERP, finance, HCM, payroll, LMS or enterprise data platform. Many institutions run it alongside existing enterprise systems, and it provides connectors and an API to do so, including a Salesforce connector for institutions that keep Salesforce as their CRM of record while using Full Fabric for the admissions lifecycle. Full Fabric is also not the right fit for every institution; it is best suited to those whose admissions, payments and student records benefit from living in one system and whose teams want to own the platform without managing a large partner-led build. Fit depends on scope, architecture and operating model, and no platform, Full Fabric included, guarantees lower cost, faster implementation, compliance or growth on its own.
This comparison is intended to be fair. Both serve higher education, and the differences are mainly in scope, architecture and operating model rather than in one being universally better.
| Dimension | Salesforce Education Cloud | Full Fabric |
|---|---|---|
| Primary category | Enterprise CRM platform with growing SIS capabilities | Purpose-built higher education lifecycle platform |
| Best suited to | Large institutions with in-house expertise and a multi-year programme | Business schools, mid-size universities and international institutions wanting a unified platform |
| Higher education fit | Configurable to higher education; requires design work | Built around the higher education lifecycle from the outset |
| Admissions workflows | Highly configurable; often partner-assisted | Purpose-built, configured by admissions teams |
| Student lifecycle continuity | Achievable with integration across systems | Continuity by design on one data model |
| Student record / SIS coverage | SIS capabilities being released over time; verify availability | Student records and enrolment included in the core platform |
| Payments | Typically via third-party tools and integrations | Built-in payment collection for fees, deposits and tuition |
| Reporting | Powerful within scope; cross-system reporting needs integration | Lifecycle reporting from a single source |
| Integrations | Extensive APIs and large ecosystem | Modern API and pre-built connectors, including for enterprise CRMs |
| AI | Agentforce agents and analytics; governance is the institution's responsibility | Contextual AI in workflows; governance is the institution's responsibility |
| GDPR and security | EU data residency options; documented DPA and DPF certification | GDPR-ready architecture on AWS; compliance depends on configuration |
| Implementation model | Often certified-partner led | Delivered directly by Full Fabric's implementation team |
| Customisation | Very high; horizontal platform | Configurable within a higher education model |
| Operational ownership | Often depends on admins or partners | Designed for functional-team ownership |
| Best fit summary | Enterprise scale, breadth and deep customisation | Focused lifecycle scope with operational ownership |
The honest reading of this table is that Salesforce offers a broader enterprise CRM ecosystem, higher configurability and a larger partner ecosystem, at the cost of more design and implementation effort, while Full Fabric offers a more focused, purpose-built lifecycle scope with less configuration overhead, at the cost of being a narrower platform than a general enterprise CRM. Neither wins every row, and the right choice depends on your institution.
Use these questions as a decision checklist:
The recurring mistakes are worth naming. Treating Salesforce as an out-of-the-box higher education solution without budgeting for implementation design. Focusing only on licence price and underestimating implementation, partner and integration costs. Underestimating change management. Failing to involve the DPO and legal team early. Assuming that EU data residency resolves every GDPR question. Building too many custom objects and workflows without governance. Ignoring the complexity of SIS, LMS and finance integration. Not planning data migration properly. Leaving ownership between central IT and admissions undefined. Over-automating workflows before fixing the underlying process. Forgetting the needs of non-technical users. And, finally, not comparing Salesforce against purpose-built higher education platforms before deciding.
Salesforce can be a strong option for European universities that have the scale, budget, governance and technical capacity to implement and maintain a highly configurable enterprise CRM ecosystem. Its ecosystem, configurability and analytics are real advantages, and its EU data residency options and documented compliance posture give European institutions credible ground to work from, provided the due diligence is done properly.
For many institutions, though, particularly those focused on admissions, enrolment, payments, student records and lifecycle visibility, a purpose-built higher education platform may be simpler and more directly aligned with day-to-day operations. The decision should turn on what problem you are solving, who will own the platform, and how much configuration and integration your institution is prepared to carry.
For European universities, business schools and specialist providers evaluating Salesforce alternatives, Full Fabric offers a purpose-built higher education platform that connects CRM, admissions, enrolment, payments, student records and reporting around one learner record. Whether that focus is the right fit, or whether the breadth of an enterprise CRM serves you better, is exactly the evaluation this article is meant to help you make.
It can be, depending on the institution. Salesforce is a powerful, configurable enterprise CRM with strong analytics, a large partner ecosystem and EU data residency options. It tends to suit larger institutions with in-house expertise and the budget and governance to run a multi-year programme. Institutions that need fast, low-dependency admissions workflows, or CRM, payments and student records connected out of the box, should also evaluate purpose-built higher education platforms.
Salesforce Education Cloud is Salesforce's industry cloud for education, built on the core Salesforce platform. Salesforce positions it as a unified platform combining CRM for education with next-generation SIS capabilities, using platform automation, analytics and AI, with modules spanning recruitment and admissions, academic operations, student success, student financials, and advancement and alumni relations (Salesforce Education Cloud).
Enterprise CRM maturity, a very large ecosystem and skills market, deep configurability across many use cases, strong automation and analytics, growing AI capabilities, broad integration options, and the scale to support large multi-country institutions. The value depends heavily on implementation quality and governance.
Implementation complexity, dependence on specialist administrators or partners, total cost of ownership beyond licences, the configuration needed to fit higher education concepts, the risk of persistent system fragmentation without a clear integration plan, GDPR and data-transfer due diligence, procurement and governance considerations, and user adoption challenges.
Salesforce can be used in a GDPR-compliant way and publishes the mechanisms to support that, including EU data residency through the Hyperforce EU Operating Zone, a Data Processing Addendum, and certification under the EU-US Data Privacy Framework. Compliance in any given deployment depends on how the institution configures and uses the platform, and should be assessed with your DPO and legal team. This is not legal advice.
It is a Salesforce offering that stores and processes EU customer data within the EU, with limited exceptions, for a vetted set of products, and provides support from EU-based personnel. It is built on Hyperforce, Salesforce's public-cloud infrastructure architecture (Salesforce, Hyperforce EU Operating Zone). It addresses data residency, which is not the same as full data sovereignty; access and transfer questions still require review.
Depending on requirements, alternatives to evaluate include Full Fabric, Microsoft Dynamics 365, the Ellucian ecosystem, Oracle, Unit4, Slate, HubSpot, DreamApply, Anthology, and credible local or specialist European platforms. The right shortlist depends on scope, existing systems and whether you need a horizontal enterprise CRM or a purpose-built lifecycle platform.
Salesforce is a broad enterprise CRM configured for higher education; Full Fabric is a purpose-built higher education platform connecting CRM, admissions, payments, student records and reporting on a single data model. Full Fabric tends to require less configuration for higher education workflows and is designed for functional-team ownership, while Salesforce offers greater breadth, configurability and a larger partner ecosystem. Full Fabric is not a replacement for enterprise ERP, finance, HCM or LMS systems.
It depends on scope and operating model. Institutions wanting one enterprise CRM across many functions, with in-house expertise and budget for a large programme, may favour Salesforce. Institutions focused on admissions, enrolment, payments, student records and lifecycle visibility, wanting lower technical dependency, often find a purpose-built platform a closer fit. Both should be compared against day-to-day operational reality.
Clarify the problem being solved, who will own the platform, internal expertise and partner needs, full five-year cost, required products and integrations, data residency and international transfers, sub-processors and audit rights, DPIA requirements, whether admissions teams can configure workflows without developers, the exit strategy and data portability, and whether a purpose-built platform would be simpler for your scope.
