The foundation Connect clock is ticking⏰advice for NPSP customers

If your charity or not-for-profit still relies on Salesforce’s foundationConnect for grant management and you’re on the Nonprofit Success Pack (NPSP), this is a message you can’t ignore: foundationConnect will be deactivated on 31 January 2026 (and subscriptions are no longer renewable)  Salesforce. In short, the foundationConnect clock is well and truly ticking to make a reliable plan and start moving.

Below we summarise the facts and walk through the options.


The facts

foundationConnect will be deactivated on 31 January 2026. Salesforce

Subscription have not been renewable for foundationConnect since 31 January 2025 — this is to ensure customers can’t prolong the product beyond that renewal window.

Grantmaking is Salesforce’s newer, first-party solution for grant management; it is delivered as part of Salesforce’s Nonprofit Cloud (NPC). In short: if you want to utilise Salesforce’s Grantmaking you’ll need to migrate over to NPC. Salesforce

Salesforce and partners alike have published migration guidance and tools to help move organisations from the NPSP managed package to NPC but planning and data transformation are heavy lifts.


Weigh up your options

1. Migrate to NPC and adopt Salesforce Grantmaking

Pros: First-party product (longer roadmap), deep platform capabilities, access to native features (OmniStudio, Business Rules Engine, Experience Cloud) and future Salesforce investments. Good if you want to align solely to the vendor roadmap. Salesforce

Cons: Requires migration from NPSP → NPC (data model and processes change). That takes planning, testing and resources. Expect more time and cost than a simple add-on.

Viable if: You want to standardise on Salesforce’s product roadmap, reduce third-party dependency, and can commit to a platform migration immediately.

2. Keep NPSP and build a native grant management solution in line with how you work

Pros: Fastest route to continuity. You can design grant objects/processes that match your workflows exactly. Native builds (custom objects, Flow, Lightning pages, Experience Cloud portal or judicious use of the Guest User profile) run inside your org — lower ongoing license complexity. A well-scoped native solution can be delivered affordably and quickly.

Cons: Requires someone (internal or partner) who knows Salesforce configuration or simple development.

Viable if: Migration to NPC isn’t feasible in your timeframe or budget. You need continuity, control and a cost-sensible path. (This is the safe option the rest of the sector is using while they plan larger migrations.)

 

3. Move to a third-party grant management app (AppExchange or standalone)

Pros: Off-the-shelf grant features, portal functionality, quicker than a full NPC migration.

Cons: May require integration work to sync contacts, payments and outcomes with your NPSP data; introduces ISV lock-in; will incur ongoing subscription costs. For some organisations, total cost or missing features make this less attractive.


Make the right decision

If you have leadership appetite and budget to standardise on Salesforce and want long-term roadmap certainty → Migrate to NPC and adopt Grantmaking.

If you need continuity, low cost and quick delivery before Jan 31, 2026 → Build a native solution on your existing org (NPSP). It’s pragmatic and more cost effective than a rushed NPC migration.

If you want an out-of-the-box product and are willing to integrate → Consider third-party grant management solutions (evaluate integration and total cost of ownership).


Final thoughts

This is a firm deadline from Salesforce: foundationConnect will be deactivated on 31 January 2026. Treat this as a project with fixed-end date: if you plan to move to NPC Grantmaking, start the migration now. If moving to NPC isn’t an option this year, a well-scoped native solution on your existing NPSP org will enable you to manage grants in line with your business processes and business rules, and—contrary to what you may fear—doesn’t need to break the bank.