Testing your integration
Testing your integration before going live is a critical step in your MoveData setup. A thorough test in a Salesforce sandbox helps you catch configuration issues, verify data mapping, and build confidence before production.
Before you begin#
- You need MoveData installed in a Salesforce sandbox.
- Your integration should be connected and active in the sandbox.
- You need access to your fundraising platform to generate test data.
Warning
Do not skip sandbox testing. Issues found in production affect real data and can be harder to resolve.
Use a sandbox#
Test in a Salesforce sandbox rather than production. A sandbox gives you a safe environment to verify that data flows correctly. If something goes wrong, no live records are affected.
If you do not have a sandbox, speak to your Salesforce administrator about creating one.
Test checklist#
Work through the following steps to verify your integration is working correctly.
1. Send a test donation or transaction#
Create a test donation (or other supported transaction) in your fundraising platform.
- Webhook integrations (e.g., Raisely, Grassrootz) — the donation triggers a notification automatically within minutes.
- Polling integrations (e.g., JustGiving) — the donation is picked up on the next polling cycle, which may be up to 24 hours depending on your schedule. Check the integration article in this knowledge base for details on your platform's polling schedule.
- File-based integrations (e.g., Benevity) — export the data and upload the file to MoveData.
2. Check that a notification appears#
Open the MoveData app in Salesforce and navigate to the Notifications tab. A notification for your test transaction should appear based on the timing described in step 1.
3. Verify the notification status is Success#
The notification status should show Success. If it shows Failed, open the notification to review the error.
4. Review the execution log#
Open the notification and click the Execution tab. The execution log shows every step MoveData performed, including record creation, matching, and field mapping. Review the log to confirm the expected records were created or updated.
5. Verify Salesforce records#
Navigate to the records MoveData created in Salesforce. Depending on your integration and extension, check the following:
- Contact (NPSP) or Person Account (Nonprofit Cloud) — was the supporter record created or matched correctly?
- Opportunity (NPSP) or Gift Transaction (Nonprofit Cloud) — does the donation amount, date, and campaign match the source data?
- Campaign — was the correct campaign created or linked?
6. Test duplicate detection#
Test that MoveData correctly matches incoming data to existing Salesforce records. For detailed steps on how to do this, see Testing your configuration in the Duplicate rules article.
7. Test edge cases#
Where your platform supports them, test the following scenarios:
- Anonymous donation — a donation with no supporter details.
- Recurring donation — a subscription or regular giving setup.
- Refund — a reversal of an earlier donation (if supported by your platform).
What a successful test looks like#
Your test is successful when:
- Notifications arrive with a Success status.
- The correct Salesforce records are created with accurate field values.
- Duplicate detection works — sending the same data twice does not create duplicate records.
- Edge cases are handled gracefully (skipped or processed as expected).
What a failed test looks like#
If your test notification shows a Failed status, this is not unusual during initial setup. Open the notification and review the execution log for error details.
Common causes include missing field mappings, permission issues, or validation rule conflicts.
Success
See Reading and understanding error messages for step-by-step guidance on diagnosing errors.
Moving to production#
Once all tests pass in your sandbox:
- Install MoveData in your production Salesforce org.
- Repeat the integration connection steps in production.
- Send a small batch of real data to confirm everything works.
- Monitor the Notifications tab closely during the first few days.
See What to expect after going live for guidance on normal production behaviour.