How it Works

How MoveData Functions

MoveData processes information into Salesforce the moment it is issued by your connected platform. The connection is typically established by way of API Key or equivalent linking both systems.

Example: connecting Raisely and Salesforce

Once information is received it is automatically processed into various records representing the information issued and the data model employed in your Salesforce Org (typically Nonprofit Cloud or Nonprofit Success Pack). This is automatically built into your MoveData integration which contains infrastructure, redundancies and efficiencies which are the result of doing Salesforce integrations for hundreds of Nonprofits around the world.

Example: records produced from a peer-to-peer donation in Nonprofit Success Pack

People typically add customisations to their source platforms and to Salesforce, thus an onboarding program is delivered by MoveData to ensure a 100% fit with the way you use Salesforce (see below).

How MoveData works with your Salesforce Org

No two Salesforce instances are the same. As such, all MoveData integrations can be easily extended to incorporate your own business rules. The process we administer for new customers is as follows and typically takes between 2-4 weeks from start to finish. The result is an integration which is 100% compatible with the way you use Salesforce and runs automatically in the background forever more.

1. Access to Sandbox

MoveData receives access to a sandbox environment and connects your integrations. We review the records produced by the integration and identify any additional business rules the integration might need to accommodate.

Examples of these could be:

  • Writing custom information collected in your source platform into Salesforce (for example: if you ask custom questions on your donation forms)
  • Supporting custom fields and/or objects you have set up in Salesforce (for example: if you house marketing consent in a particular way)
  • Implementing other business rules unique to your organisation (for example: if you need donations to flow into a particular campaign based on certain criteria)
  • Other best practices suggested by MoveData and as implemented for hundreds of other Nonprofits who use Salesforce
Example: review performed by MoveData

These findings are journaled to a Google Spreadsheet and a meeting is organised to finalise together. This is performed free of charge to all new MoveData customers on a fair and reasonable basis.

Typical duration: 1 week

2. Documentation

A document is issued to formally define those requirements to be built into your integration.

MoveData provides 8 hours worth of developer support to all new MoveData customers who commit to an annual plan. For most customers this is sufficient to “fine-tune” their integrations to support their desired behaviour. Should effort exceed 8h then a fixed price quotation is issued for the difference.

Typical duration: 1 day

3. Implementation, Testing and Go Live

MoveData builds the additional functionality into your integration and passes internal testing to ensure functionality conforms to the requirements. A handover document is issued so that you can confirm the same and the integration is deployed into Production.

Typical duration: 1-2 weeks