The Fonteva Upgrade Readiness Checklist

Before you touch a single package, run through these 12 checks. They're the same categories our team assesses in a full Checkpoint engagement — use them to spot the risks that most often derail an association's Fonteva upgrade.

1. Environment & versions

Confirm your current Fonteva & Salesforce versionsDocument your exact managed package versions and the target release you're upgrading to.

Check the release gapKnow how many releases behind you are — larger gaps mean more breaking changes to plan for.

Review Fonteva's release notesFlag deprecated features and required migration steps between your version and the latest.

2. Packages & customizations

Inventory all managed & unmanaged packagesList every installed package and confirm each is compatible with the target version.

Audit custom code (Apex, triggers, LWC)Identify customizations that reference Fonteva objects or APIs likely to change.

Review flows, process builders & validation rulesAutomation tied to Fonteva fields is a common source of post-upgrade breakage.

3. Integrations & data

Map every external integrationPayment gateways, email platforms, AMS/CRM syncs — document what talks to Fonteva.

Validate data volume & storageConfirm you're within org limits and that large objects won't stall the migration.

Check for data quality issuesDuplicate or orphaned records can surface as errors mid-upgrade.

4. Testing & rollback

Confirm a full sandbox refreshNever test an upgrade against stale sandbox data.

Define your test scriptsCover member join/renew, events, payments, and reporting end-to-end.

Document a rollback planKnow exactly how you'll revert if something goes wrong on go-live day.

Want this scored against your actual instance?

A Checkpoint assessment turns this checklist into a readiness score, roadmap, and next steps for your environment — delivered in 5 days, and credited back in full if you upgrade with Radical One.