Raiser’s Edge NXT Database View retirement: how to prepare for Web View

Blackbaud has announced that support for Raiser’s Edge NXT Database View and Database View-dependent functionality will end on September 15, 2027. Blackbaud is moving users toward its browser-based Unified View and continues to release Web View functionality.

For nonprofits, this is not a data migration. The underlying challenge is moving the processes, integrations and staff responsibilities that still depend on Database View.

What the Database View retirement means

The impact will vary by role. Fundraisers and major gift officers may already complete most of their work in Web View. Database managers and advancement operations teams are more likely to depend on Database View for:

• Imports, duplicate review and global changes
• Queries, exports and reporting
• Gift entry and batches
• Campaign, fund and appeal management
• Segmentation
• Acknowledgements, receipts and mail processes
• Consent management
• Data maintenance and reconciliation
• Plugins and connected applications
• Specialized administrative workflows

Because the roadmap changes as features are released, use Blackbaud’s current Unified View Transition Guide and Feature Map when evaluating functionality.

Start with workflows, not a feature list

Rather than evaluating features in isolation, document the complete Database View workflows your organization relies on, including the process owner, related queries and files, business rules, required outputs, connected applications and any Web View gaps.

Test complete workflows and outputs with real examples. This will show which processes can move now, which need more preparation and where additional support may be required.

For a broader approach to ownership, communication, testing and staff adoption, use our Web View transition plan.

Prepare for the transition

Organizations should focus on three priorities:

1. Assign an owner. Appoint a Web View Transition Leader to coordinate workflow reviews, testing, documentation, training and communication with leadership. Provide dedicated time and support from database, fundraising and reporting teams.
2. Test critical workflows. Use Web View for real processes while Database View remains available. Test imports, queries, gift processing, reporting, acknowledgements, segmentation and reconciliation. Document gaps, permission issues and workarounds.
3. Review plugins and integrations. Identify workflows that depend on Database View plugins, especially ImportOmatic and SegmentOmatic. Document what each tool does and evaluate whether Web View or a partner solution can support those requirements. Their current plugin versions will not continue in their existing form after Database View-dependent functionality ends.

If you use ImportOmatic

Review:

• Active import profiles
• Source platforms and file formats
• Matching and duplicate rules
• Field transformations
• Fund, campaign and appeal coding
• Consent updates
• Exception handling
• Gift batch requirements
• Import schedules
• Manual review after processing

Blackbaud’s native Web View Import may meet some requirements. More complex data flows may still require a partner solution.

If you use SegmentOmatic

Review:

• Active segmentation models
• RFM and other scoring rules
• Queries and suppressions
• Segment priorities
• Package and appeal assignments
• Channel rules
• Export fields
• Processes performed in spreadsheets
• Data written back to Raiser’s Edge NXT
• Final validation steps

Do not focus only on recreating a SegmentOmatic output file. Preserve the rules and organizational knowledge behind the segmentation process.

Omatic has also published a Raiser’s Edge Database View Sunset FAQ. Customers should confirm Omatic’s current roadmap and support terms directly with the vendor.

Modern options for data integration and segmentation

The Database View retirement is a useful point to evaluate whether existing processes still meet the organization’s needs.

Charity Automator Data Flow

Charity Automator Data Flow helps automate data movement between fundraising platforms and the CRM, giving teams clearer visibility into how information moves through their systems.

Depending on the configured integration, it can support:

• Data import from various sources and connected platforms

• Constituent matching
• Coding rules
• Data validation
• Scheduled processing
• Exception management
• Reconciliation information
• Visibility into processing status and data issues

Post-launch support matters because fundraising work is time-sensitive. SimpliPhi’s approach is proactive rather than reactive: helping teams identify issues early, understand their data more clearly and keep critical processes moving when timing is tight.

For organizations reviewing ImportOmatic, the correct comparison is based on required workflows, rules, source systems and support needs. Charity Automator Data Flow should not be treated as a simple one-to-one product replacement without an assessment.

AmpliPhi.app

AmpliPhi.app provides a structured environment for donor segmentation connected to Raiser’s Edge NXT.

It allows teams to:

• Connect your CRM and build segments in minutes
• Define and organize each audience using simple inclusions/exclusions
• Validate audiences directly in the application: adjust your criteria if needed, and recalculate your segments on the fly
• Choose the right channel for each segment and push assignments directly to your CRM

For organizations reviewing SegmentOmatic, AmpliPhi.app offers a modern approach to managing segmentation outside a Database View plugin.

How SimpliPhi can help

SimpliPhi helps organizations prepare their people, processes and connected systems for Web View.

Our team can help:

• Audit Database View workflows
• Identify affected plugins and integrations
• Prioritize processes for testing
• Document current and future procedures
• Coordinate transition activities
• Support the Web View Transition Leader
• Review ImportOmatic and SegmentOmatic dependencies
• Evaluate modern integration and segmentation options

Blackbaud provides the Unified View platform, roadmap and product resources. SimpliPhi helps organizations apply those changes to their own operations.

Raiser’s Edge NXT Web View readiness checklist

Before building your transition plan, confirm that:

• A Web View Transition Leader has been appointed.
• The project has executive support and allocated staff time.
• Critical Database View workflows are documented.
• Plugins and connected applications are included in the inventory.
• ImportOmatic and SegmentOmatic processes have been reviewed.
• Workflows are being tested with real organizational data.
• Issues and differences are documented.
• Process owners are involved in testing.
• Training is planned by role.
• Revised procedures are documented.
• Critical processes have contingency plans.
• The team follows Blackbaud’s current Feature Map and release updates.

If your organization needs help reviewing Database View workflows, integrations or segmentation processes, contact SimpliPhi.

Frequently asked questions

When will Raiser’s Edge NXT Database View be retired?

Blackbaud has communicated that support for Database View and related Database View-dependent functionality will end on September 15, 2027. Check Blackbaud’s official resources for future updates.

Is Raiser’s Edge NXT being discontinued?

No. Blackbaud is retiring Database View and moving Raiser’s Edge NXT toward a unified browser-based experience.

Will Web View replace ImportOmatic?

Not necessarily. Blackbaud says native Web View Import will cover essential importing, while advanced requirements may still need partner solutions. ImportOmatic users should compare their current profiles and business rules with available modern options.

Will ImportOmatic and SegmentOmatic continue working?

Their existing versions operate as Database View plugins. SimpliPhi’s technical assessment is that they cannot continue in their current form after Database View-dependent functionality ends. Confirm product-specific plans directly with Omatic.

Can donor segmentation be completed in Web View?

Web View functionality continues to develop, but organizations should not assume it replaces every advanced segmentation process currently managed through plugins, Database View queries or spreadsheets. Document the complete segmentation workflow before choosing a future solution.

When should organizations begin preparing?

Start now by documenting Database View dependencies and testing available Web View functionality. Early testing gives the team more time to update workflows, train users and resolve gaps.

Which workflows should nonprofits review before Database View is retired?

Review every process that uses Database View, a plugin or a connected application. Common examples include imports, gift batches, queries, exports, acknowledgements, segmentation, reconciliation and administrative data maintenance.

What should ImportOmatic and SegmentOmatic users do now?

Document the profiles, rules, source files, outputs and manual review steps supported by each plugin. Then compare those requirements with Blackbaud’s available Web View functionality and modern partner solutions. Confirm each vendor’s current roadmap directly before making a product decision.