An NPSP customer wants to move to Nonprofit Cloud. How would you scope that engagement?

As a re-implementation with a data migration, not as an upgrade, and I would say so in the first meeting.

1. The constituent model is the crux. NPSP uses Contacts with household Accounts; Nonprofit Cloud typically uses Person Accounts, which NPSP does not support. That is not a toggle, it is a data transformation.
2. The fundraising model changes too. Donations move from Opportunities and payment schedules to Gift Transactions, Gift Commitments and Gift Commitment Schedules, with designations replacing whatever allocation approach was in use.
3. So the scope has four real workstreams: data mapping and migration, integration rework for anything pointed at the old objects, report and dashboard rebuild, and retraining. Teams routinely underestimate the last two.
4. I would run a discovery phase first to establish how much custom development and how many integrations exist, because that — not the record count — usually determines the size of the project.
5. And I would be straight about whether it is worth it. If the customer's NPSP org is working and nothing is blocked, the honest recommendation may be to wait and plan properly rather than migrate because a newer model exists.