Data Mapping Overview

This section provides detailed documentation of how data flows between WeGive and Blackbaud Raiser’s Edge NXT. Understanding these mappings is essential for successful integration configuration and ongoing maintenance.

Integration Architecture

The WeGive Blackbaud integration provides bidirectional synchronization between:

WeGive Platform: Modern donation and donor engagement platform
Blackbaud Raiser’s Edge NXT: Comprehensive fundraising and donor management CRM

Synchronization Model

Authentication

OAuth2 with PKCE (Proof Key for Code Exchange)
Automatic token refresh for uninterrupted service
Environment-specific authentication (development/production)

API Integration

Blackbaud Sky API REST endpoints
Rate limiting and automatic retry logic
Comprehensive error handling and recovery

Data Flow

Real-time synchronization for critical updates
Scheduled batch processing for bulk operations
Bidirectional sync with conflict resolution

Core Object Relationships

Primary Objects

WeGive Object	Blackbaud Object	Sync Direction	Purpose
Donor	Constituent	Bidirectional	Individual and organization donor records
Donation	Gift	Bidirectional	Transaction and payment records
Fund	Fund	Bidirectional	Designation and fund management
Campaign	Campaign	Bidirectional	Fundraising campaign tracking
Recurring Donation	Recurring Gift	Bidirectional	Subscription and recurring payment management

Supporting Objects

WeGive Object	Blackbaud Object	Sync Direction	Purpose
Address	Address	Bidirectional	Contact address information
Phone	Phone	Bidirectional	Phone number records
Email	Email Address	Bidirectional	Email contact information
Organization	Company	Pull Only	Corporate and business records
Family	Household	Pull Only	Family relationship structures

Data Synchronization Patterns

Object Creation Flow

New Donor Registration (WeGive → Blackbaud)

WeGive donor record created
Real-time sync triggered
Blackbaud constituent created
Correlation ID established
Address/contact information synced

Gift Processing (WeGive → Blackbaud)

Donation processed in WeGive
Gift record created in Blackbaud
Constituent relationship established
Fund designation applied
Payment method recorded

Update Synchronization

Bidirectional Updates

Changes in either system trigger sync
Last-modified timestamp determines precedence
Conflict resolution based on business rules
Complete audit trail maintained

Relationship Management

Constituent Relationships

Household structures preserved from Blackbaud
Individual constituent records maintained
Corporate affiliations and roles tracked
Family relationships respected

Field Mapping Strategy

Standard Field Mappings

Direct Mappings

Fields with identical purposes map directly
Data type conversions handled automatically
Validation rules applied consistently

Transformed Mappings

Complex business logic applied during sync
Multiple source fields combined into single target
Calculated fields generated during transfer

Custom Field Support

User-configurable field mappings
Custom field creation in target system
Data type preservation and validation

Data Quality Controls

Duplicate Prevention

Email address and name matching
Correlation ID tracking
Merge logic for duplicate detection

Data Validation

Required field validation
Format and length checks
Business rule compliance

Error Handling

Validation error reporting
Automatic retry for temporary failures
Manual resolution queue for conflicts

Integration Capabilities

Pull Operations (Blackbaud → WeGive)

Available Objects:

Constituents (individuals, organizations, households)
Companies and corporate structures
Gifts and payment records
Campaigns and fundraising appeals
Funds and designation categories
Recurring gifts and pledge schedules
Communication lists and segments

Pull Frequency:

Real-time webhooks (where available)
Scheduled batch imports
Manual sync triggers

Push Operations (WeGive → Blackbaud)

Available Objects:

Donor records and profiles
Transaction and gift records
Campaign and appeal data
Fund and designation information
Recurring donation schedules

Push Frequency:

Real-time for critical updates
Immediate for new donations
Batch processing for bulk updates

Detailed Object Mappings

Constituent Mapping

Complete field mappings for donor and constituent records, including:

Personal information and demographics
Contact details and preferences
Custom fields and attributes
Relationship and household data

Gift Mapping

Comprehensive transaction and payment mappings, including:

Gift amounts and designations
Payment method and processing details
Campaign and appeal attribution
Soft credits and tribute information

Fund Mapping

Fund and designation management mappings, including:

Fund categories and hierarchies
Active/inactive status management
Description and purpose information

Campaign Mapping

Campaign and appeal tracking mappings, including:

Campaign goals and metrics
Date ranges and status tracking
Attribution and reporting structures

Recurring Gift Mapping

Recurring donation and subscription mappings, including:

Schedule and frequency information
Payment method and amount details
Start/end dates and status tracking

Communication List Mapping

Segment and list management mappings, including:

List membership and criteria
Communication preferences
Opt-in/opt-out status tracking

Data Flow Examples

New Donor Scenario

Step 1: Donor Registration in WeGive

WeGive Donor Created:
- Name: John Smith
- Email: [email protected]
- Phone: (555) 123-4567
- Address: 123 Main St, City, State 12345

Step 2: Sync to Blackbaud

Blackbaud Constituent Created:
- Individual constituent type
- Primary email and phone
- Preferred address
- Correlation ID stored

Step 3: First Donation

WeGive Donation → Blackbaud Gift:
- Amount: $100
- Payment Method: Credit Card
- Fund: General Operating
- Campaign: Annual Appeal 2024

Existing Donor Update

Scenario: Address Change in Blackbaud

Address updated in Raiser’s Edge NXT
Webhook or scheduled sync detects change
WeGive donor record updated
Change log created for audit

Best Practices

Configuration Recommendations

Start with Pull-Only: Begin by importing existing Blackbaud data
Enable Push Gradually: Add WeGive → Blackbaud sync after validation
Monitor Data Quality: Regular audits of sync accuracy
Test Thoroughly: Use sandbox environment for configuration testing

Data Management

Clean Source Data: Ensure data quality before integration
Establish Conventions: Consistent naming and formatting
Regular Audits: Periodic data quality reviews
Backup Strategy: Maintain data backups before major changes

Performance Optimization

Batch Processing: Use scheduled sync for large datasets
Rate Limiting: Respect API limits and throttling
Error Recovery: Implement robust retry mechanisms
Monitoring: Track sync performance and success rates

Troubleshooting Common Issues

Sync Failures

Authentication Errors

Verify OAuth2 credentials
Check token expiration and refresh
Confirm environment settings

Data Validation Errors

Review required field mappings
Check data format compatibility
Validate business rule compliance

Rate Limiting Issues

Adjust sync timing and frequency
Implement proper backoff strategies
Monitor API usage patterns

Data Quality Issues

Duplicate Records

Review duplicate detection settings
Check correlation ID tracking
Validate merge logic

Missing Data

Verify field mapping configuration
Check data availability in source system
Review sync scope and filters

Performance Problems

Slow Sync Operations

Optimize batch sizes
Review API response times
Check network connectivity

High Error Rates

Analyze error patterns
Review data validation rules
Check system resource availability

API Reference

Blackbaud Sky API Endpoints

Authentication

OAuth2 Authorization: https://oauth2.sky.blackbaud.com/authorization
Token Exchange: https://oauth2.sky.blackbaud.com/token

Core Data Endpoints

Constituents: https://api.sky.blackbaud.com/constituent/v1/
Gifts: https://api.sky.blackbaud.com/gift/v1/
Fundraising: https://api.sky.blackbaud.com/fundraising/v1/

Rate Limits

Standard: 5000 requests per hour
Burst: Short-term higher limits available
Headers: Rate limit status in response headers

WeGive Integration Endpoints

Configuration

Integration settings and status
Field mapping configuration
Sync control and monitoring

Monitoring

Sync logs and audit trails
Error reporting and resolution
Performance metrics and analytics

Support Resources

Documentation

Support Contacts

WeGive Support: [email protected]
Blackbaud Developer Support: Developer Community
Emergency Support: Available 24/7 for critical issues

Training Resources

Integration setup webinars
Best practices documentation
Video tutorials and guides
Partner training programs

Overview

Data Mapping

​Data Mapping Overview

​Integration Architecture

​Synchronization Model

​Core Object Relationships

​Primary Objects

​Supporting Objects

​Data Synchronization Patterns

​Object Creation Flow

​Update Synchronization

​Relationship Management

​Field Mapping Strategy

​Standard Field Mappings

​Data Quality Controls

​Integration Capabilities

​Pull Operations (Blackbaud → WeGive)

​Push Operations (WeGive → Blackbaud)

​Detailed Object Mappings

​Constituent Mapping

​Gift Mapping

​Fund Mapping

​Campaign Mapping

​Recurring Gift Mapping

​Communication List Mapping

​Data Flow Examples

​New Donor Scenario

​Existing Donor Update

​Best Practices

​Configuration Recommendations

​Data Management

​Performance Optimization

​Troubleshooting Common Issues

​Sync Failures

​Data Quality Issues

​Performance Problems

​API Reference

​Blackbaud Sky API Endpoints

​WeGive Integration Endpoints

​Support Resources

​Documentation

​Support Contacts

​Training Resources