RENXT to NPSP done local-first. SKY API rate limits, attribute weight encoding, gift split reconciliation, and constituent code hierarchies handled deterministically — not approximately. Signed chain so the auditor verifies it herself.
Raiser's Edge NXT is the most architecturally dense source system in nonprofit fundraising. Twenty years of Blackbaud accretion sits behind the SKY API, and most of it has to land somewhere in NPSP without losing meaning. Six places it quietly breaks:
Same five gates as every CDM migration, with RENXT-specific rules wired in:
audit_log. You can re-run a constituent extract on a single ID three months later and prove what the source said that day.UPPER($Code) doesn't compile; TEXT(Weight) with a zero-truncation bug doesn't save.Your migration runs on your hardware. SKY API credentials sit in the macOS Keychain, gated by the ACL boundary every Mac in the building already uses for Wi-Fi PSKs. Constituent PII never touches our infrastructure. The vendor — including us — isn't in the chain of custody.
Start with a 30-minute discovery call. You describe the move, I ask questions, we determine fit. Project-based engagement — scope determines pricing.