Vision2 is a comprehensive giving platform for effective stewardship that helps churches connect with their congregation in the same engaging, welcoming way they would in person.
This integration focuses on moving contribution data between Vision2 and MinistryPlatform. This includes both core biographical data, gift/giving data and related items, such as pledges and campaigns. It does not cover other membership or ministry data often associated with donors in a ChMS.
The integration is unique in that it actively maintains a sync between the two systems in both directions. This means that data fidelity is maintained between the two solutions as any change in one will be quickly reflected in the other. In many ways, this allows Vision2 to behave as if it were an extension or ‘module’ of MinistryPlatform, relieving the church from having to deal with data movement and any other associated issues that may arise from having to keep two systems in sync.
There are specific rules and exceptions on when, what, and how the data is pushed and pulled. Below is a graphical representation of the data mapping and a description of key aspects of the integration for various elements.
The ‘Push’ integration moves new data from V2 to MP. This happens virtually instantaneously, since the information is automatically pushed via a direct API call to MP.
The ‘Pull’ or ‘Poller’ integration moves data from MP to V2. V2 periodically checks with the MP instance to see if any new information exists. This checking occurs on a continuous basis, which does mean that the information may not exist in V2 for a short period of time.
Push integration frequency
Duplicates happen. It's nearly impossible to create a usable system that won't allow a dupe to be created under the right conditions, but there are many things in place to minimize them.
Before a new profile is created in V2, there is an attempt to match it to an existing profile. If it can be matched, V2 will not create a new record. Since V2 constantly polls MP for new and updated contact records, there is always up-to-date information to match profiles with.
V2 also honors merges made in MP. When two records are merged in MP, it will also merge those same individual records in V2.
Funds and Designations will only be pulled once from MP at the initial set-up of the integration. Once the integration is established, if a new program or pledge campaign is needed in MP that will be used for tracking donations, it should first be manually created in V2 which in turn will automatically push it to MP.
Giving from recurring gifts will move between systems, but the schedule itself will not. Donations created by a recurring schedule in V2 have the Subscription field in MP populated with the Schedule ID in V2.
Checks / cash envelopes originating from MP or other third party solutions will be pulled into V2, but will not have the associated images. Images from check scans in V2 also don’t push into MP. Check numbers are not pushed to MP for all checks.
Currently, giving to campaigns in V2 will push to MP, but MP pledges are not connected to giving goals in V2. This is an enhancement currently under development.
Conduit gift are gifts on behalf of an individual from an organization or investment vehicle (also referred to as ‘soft credits’). V2 pushes conduit gifts from V2 to MP, however, V2 does not poll them. When V2 polls a donation from MP that has soft credits, V2 creates a gift and payment for the organization that’s on the donation in MP. Organization staff can edit the gift in V2 and change it to be from the individual instead of the organization.
V2 continues to align with MP best practices and expand the list of things that can be synced between the two systems.
An account with Vision2 must be established before the integration can be configured.
There is no charge from Think Ministry for configuring the integration.
Fees from Vision2 will be assessed as per each church's individual contract agreement.
Professional Services has created a nightly routine that can run to create batches and deposits and is available for purchase*. The routine creates a Batch and a Deposit, called "AutoBatch," with the date. If a Donation does not have a Batch that was added today, it will get added to this new Batch and Deposit.
Support is provided by Vision2 at email@example.com.