Key concepts and glossary
This glossary brings together the most important terms you will encounter when working with MoveData and Salesforce. Use it as a reference whenever you come across an unfamiliar term.
MoveData terms#
Authorised user — the Salesforce user account that MoveData uses to create and update records. All records created by MoveData appear as though this user made the changes. A dedicated user is recommended.
Commerce extension — a MoveData managed package that provides business logic for processing commerce transactions such as ticket sales, merchandise, and event registrations. Uses the commerce pipeline.
Commerce pipeline — a MoveData processor designed to handle commerce transaction data, including products, orders, and order items.
Commerce schema — the standardised data structure MoveData uses to process commerce transactions consistently across different platforms.
Donation — a financial contribution made by a supporter through a fundraising platform that MoveData synchronises to Salesforce.
Donation pipeline — a MoveData processor designed to handle donation and fundraising data. It processes notifications through account, contact, campaign, recurring donation, and donation phases.
Donation schema — the standardised data structure MoveData uses to process donation transactions consistently across different fundraising platforms.
Event — a fundraising campaign or activity on a platform where multiple fundraisers or donors can participate to support a nonprofit organisation.
Execution log — a detailed record of every step MoveData takes when processing a notification. The log displays four columns: Time, Group, Message, and Detail. A Variable Inspector is also available to view the data values at each processing step.
Extension — a MoveData managed package that provides specialised business logic for a specific Salesforce data model. Extensions contain pre-built Flows and metadata configurations.
Fieldset — a grouping of Salesforce fields that MoveData loads when matching existing records. Fieldsets ensure that all fields referenced in processing flows are available during execution.
Gift commitment — the Nonprofit Cloud equivalent of a recurring donation record. Represents an ongoing commitment by a supporter to give at regular intervals.
Gift transaction — the Nonprofit Cloud equivalent of an opportunity record. Represents a single donation or financial transaction in a Nonprofit Cloud organisation.
Integration — a configured connection between MoveData and a specific fundraising platform. Each integration defines how data is captured and which platform credentials are used.
MoveData application — the native Salesforce Lightning application where you manage integrations, view notifications, configure settings, and monitor processing.
Notification — a standardised data package that flows through the MoveData lifecycle. Each notification represents a single event or transaction captured from a fundraising platform. It contains all the information needed to create or update Salesforce records.
Notification status — the current state of a notification. Possible statuses are Success (processed without errors), Failed (an error prevented processing), Skipped (intentionally not processed), and Processing/Queued (awaiting or currently being processed).
NPC extension — a MoveData managed package that provides integration functionality for the Salesforce Nonprofit Cloud data model. Uses both the donation and commerce pipelines.
NPSP extension — a MoveData managed package that provides integration functionality for the Salesforce Nonprofit Success Pack data model. Uses the donation pipeline.
Permission set — a Salesforce configuration that grants users specific access rights needed to work with MoveData, its extensions, and their associated objects and fields.
Pipeline — a structured processor that executes a notification through a predetermined sequence of phases. Each phase handles a specific domain such as contacts, campaigns, or donations.
Pipeline metadata — the configuration data that defines how a pipeline operates. This includes which flows to run, which fieldsets to load, and other processing settings. Stored in the movedata__MoveData_Pipeline__mdt custom metadata type.
Platform — an external fundraising system that integrates with MoveData to synchronise transaction data into Salesforce. Examples include Raisely, JustGiving, and Benevity.
Platform key — a constructed identifier that uniquely links a record from a specific platform to its corresponding record in Salesforce. For example, raisely:abc123 links a Raisely contact to a Salesforce contact.
Protect name — a checkbox field on account, contact, and campaign records that, when enabled, prevents MoveData from overwriting the record's name during synchronisation.
Reprocess — the action of reprocessing a previously failed or skipped notification. Click the Reprocess button on a notification to try again after resolving an error or changing a configuration.
Schema — a standardised data structure that defines how MoveData processes a particular type of transaction. The two core schemas are donation and commerce.
Schema mapping — a custom metadata configuration that links a schema type to its processing pipeline. Stored in the movedata__Movedata_Schema_Map__mdt custom metadata type.
Soft credit — attribution of a donation to someone other than the primary donor. Used to recognise fundraisers, matching gift organisations, or other contributors who helped facilitate the gift.
Setup wizard — the guided configuration process that runs when you first open MoveData after installation. It handles authorisation, extension installation, and initial settings.
Salesforce terms#
Account — a Salesforce object that represents an organisation, household, or individual (when using person accounts). In NPSP, contacts are grouped under household accounts.
Campaign — a Salesforce object used to track fundraising initiatives, appeals, events, and peer-to-peer activities. MoveData creates and links campaigns based on data from fundraising platforms.
Change set — a Salesforce deployment tool used to move configuration and customisation between environments (such as from sandbox to production). MoveData's onboarding team uses change sets to deploy approved configurations.
Contact — a Salesforce object that represents an individual person, such as a donor, volunteer, or beneficiary.
Custom metadata type — a Salesforce configuration mechanism used to store settings that can be deployed across environments. MoveData uses custom metadata types for pipeline and schema configuration.
Duplicate rule — a Salesforce configuration that defines how the system identifies potential duplicate records. MoveData uses duplicate rules during processing to match incoming data with existing records.
Field — a single piece of information stored on a Salesforce record, such as a name, email address, or donation amount.
Flow (formerly Lightning Flow) — a Salesforce visual automation tool that allows you to build business logic without writing code. MoveData uses Flows for data mapping, duplicate checking, and custom processing rules.
Matching rule — a Salesforce configuration that specifies the criteria used to compare records during duplicate detection. Matching rules work alongside duplicate rules.
Nonprofit Cloud (NPC) — Salesforce's current nonprofit solution, built on person accounts. It combines contact and account information into a single record per individual.
Nonprofit Success Pack (NPSP) — Salesforce's original nonprofit solution, built on the standard platform with customisations for nonprofit use cases. NPSP uses a household account model.
Object — a type of data in Salesforce, similar to a database table. Standard objects include Contact, Account, Opportunity, and Campaign. Custom objects can be created for organisation-specific needs.
Opportunity — a Salesforce object used to track donations, grants, and other fundraising transactions in NPSP environments.
Permission set — a collection of settings and permissions that extend a user's access without changing their profile. See also the MoveData-specific permission set definition above.
Person account — a Salesforce record type that combines contact and account information into a single record. Used by Nonprofit Cloud for individual constituent management.
Record — a single entry within a Salesforce object. For example, one contact record represents one person.
Sandbox — a copy of your Salesforce production environment used for testing, development, and training. Changes made in a sandbox do not affect your live data.
Integration terms#
API key — a credential used to authenticate MoveData with a fundraising platform's application programming interface. API keys are typically provided by the platform and entered during integration setup.
CSV import — a method of bringing data into MoveData by uploading a comma-separated values file exported from a fundraising platform. Used by platforms like Benevity and Charitable Giving.
Polling — an automated process where MoveData periodically queries a fundraising platform to check for new or updated data. Polling intervals can range from every 10 minutes to every 24 hours.
Webhook — a real-time notification mechanism where a fundraising platform sends data to MoveData when an event occurs. Webhooks provide instant data synchronisation without manual intervention.