Fonteva Upgrade Readiness Report

Prepared for [Association name redacted] · Current: Fonteva 21Winter → Target: Fonteva Platform 16 · 5-day assessment

56/ 100

Upgrade readiness: Elevated risk

The platform is operational and business-critical, but four domains score Red for the FP 16 upgrade. Two critical blockers must be resolved before migration — a deprecated package reference and custom overrides of core Fonteva services. Clear the items below and this becomes a controlled, staged upgrade.

Remediate before upgrading

Readiness by domain

Eight domains scored for FP 16. Four are upgrade blockers.

Membership architectureCore membership is highly customized with manual intervention and complex org structures — the biggest upgrade risk. Low readiness

Technical debt & configuration complexityDuplicated fields, legacy patterns, and undocumented customizations increase platform fragility. Low readiness

Identity & data integrityDuplicate identities and inconsistent contact data complicate membership processing and authentication. Low readiness

Governance & documentationLimited architectural documentation and inconsistent governance make safe platform changes difficult. Low readiness

Security, automation, portal & integrationsFour domains at medium readiness — workable, but each needs validation before cutover. Medium

Key upgrade findings

The specific components that FP 16 impacts, ranked by risk.

Deprecated CurrencyApi package referenceLegacy references embedded in permission metadata, deprecated in FP 16. Can block package removal or throw deployment validation errors. Critical

Custom overrides of core Fonteva servicesCustom extensions of core service layers create a regression surface requiring targeted upgrade testing. Critical

Unsupported DonorApi & CPBase componentsAutomation relies on DonorApi (unsupported after FP 16); community uses CPBase Visualforce components entering sunset support. High

Guest user over-exposureGuest profiles have read access to 227 objects and edit to 218 — far above standard. Remediate before upgrade. High

Payments package alignment unconfirmedThe installed Fonteva payments framework must meet FP 16 prerequisites before upgrade. High

Permission-set based access modelIdentity relies primarily on permission sets, aligning with FP 16 requirements — just needs final validation. Ready

Environment at a glance

The scale behind the risk — complexity score 12 vs. a benchmark of 13 (average).

~174K lines of code across 9,261 filesLarge customization footprint (462 custom objects, 246 triggers) increases regression-testing effort. Watch

7,623 components on obsolete API versions (v < 55)Plus 288 deprecated. 61 managed packages, 21 out of date and 37 not security-reviewed. Watch

11,305 well-architected issues (74.8% technical debt)65+ high-severity and 6,704 medium-severity issues to triage across the codebase. Watch

Recommended roadmap

A five-week path to the Fonteva Platform 16 upgrade.

Week 1 Upgrade preparation

Refresh sandbox, confirm the FP 16 prerequisites, and lock scope around the critical blockers.

Week 2 Environment remediation

Resolve the CurrencyApi reference, address custom service overrides, and tighten guest-user access.

Week 3 Sandbox upgrade execution

Apply FP 16 in a full sandbox and validate DonorApi, CPBase community, and payments dependencies.

Week 4 Regression testing & validation

Run end-to-end tests across membership, events, commerce, and the community portal.

Week 5 Production readiness & cutover

Execute in production with a defined rollback plan and post-upgrade validation.

Actionable next steps

What to do first, in order.

Resolve the deprecated CurrencyApi package reference — it can block the deployment outright.
Inventory and plan validation for the custom Fonteva service overrides (your biggest regression surface).
Remediate guest-user permissions (227 read / 218 edit objects) before cutover.
Confirm the Fonteva payments package meets FP 16 prerequisites.
Schedule a full sandbox refresh and confirm the production window & rollback plan with stakeholders.

This is a sample. Get one for your instance.

A full Checkpoint assessment scores your exact environment across every package, integration, customization, and data risk — delivered in 5 days, and credited back in full when you upgrade with Radical One.

Start my assessment →

Sample only. All findings, names, and figures are illustrative and anonymized; they do not represent a real association's environment.