Last Updated: January 9, 2026
1. Professional Services Overview
Professional Services delivered by MoveData are done in accordance with the following four (4) stage process:
| Stage | Description | Responsible Party | Key Activities |
| 1. Review | MoveData reviews and analyses the Client’s support request | MoveData | MoveData shall review the support request, assess requirements, identify scope, and determine the approach for implementation |
| 2. Configuration | MoveData configures and develops the required functionality | MoveData | MoveData shall implement necessary business rules, configurations, and customisations within MoveData, Salesforce, and/or applicable Source Platforms |
| 3. Testing | The Client conducts acceptance testing of the delivered functionality | Client | MoveData shall provide the functionality to the Client for testing in the development environment. The Client shall perform acceptance testing in accordance with 5. Requirements: Client |
| 4. Deployment | MoveData deploys approved functionality to the Production environment | MoveData | Upon the Client’s written approval, MoveData shall deploy the functionality to the Client’s Production environment |
2. Financial Information
Financial Information for Professional Services delivered by MoveData is as follows:
| Pre-Paid Support Package Hours | As stated on your MoveData Professional Services invoice. |
| Pre-Paid Support Package Cost | As stated on your MoveData Professional Services invoice. |
| Payment Period | Payment is due within seven (7) days from the invoice date. If payment is not received within the Payment Period, MoveData reserves the right to suspend provision of Services until payment is received. |
| Warranty Period | No warranty period applies to Pre-Paid Support Packages or Services provided. |
| Banking Information | As stated on your MoveData Professional Services invoice. |
| Remittance Advice | Please use accounts@movedata.io for remittance advice. |
Pre-Paid Support Package Cost
The cost for the Pre-Paid Support Package are set out in the table below, denominated in the base currency of the Client’s MoveData account.
| Currency | Hourly Rate | Package Cost (8 hours) |
| AUD | $175+GST | $1,400+GST |
| GBP | £90 | £720 |
| USD | $125 | $1,000 |
| NZD | $200 | $1,600 |
| EUR | €110 | €880 |
3. Legal Information
This Statement of Work is governed by MoveData’s Professional Services Agreement. In addition to the Professional Services Agreement the following conditions apply.
1. Time-Based Charging
1.1.Increments. Time shall be calculated and charged in thirty (30) minute increments.
1.2. Chargeable Activities. All time spent by MoveData personnel in connection with the Client’s requests, requirements, or the Services shall be chargeable, including without limitation: (a) reviewing requests, documentation, or requirements; (b) project management, coordination, and administration; (c) investigation, analysis, and troubleshooting; (d) preparation of documentation, specifications, or reports; (e) attending meetings, calls, or training sessions; (f) communications with the Client or third parties; (g) scoping, estimating, and planning activities; (h) configuration, customisation, and development work; (i) testing, quality assurance, and deployment activities; and (j) any other activities reasonably undertaken in connection with the Services or Client requests.
1.3. Client Acknowledgment. The Client acknowledges that all activities undertaken by MoveData at the Client’s request or for the Client’s benefit constitute chargeable time, regardless of whether such activities result in deliverables or completed work product.
2. Pre-Paid Support Package
2.1. Commencement Date. The Commencement Date is the date on which MoveData receives cleared funds for that Pre-Paid Support Package.
2.2. Validity Period. Each Pre-Paid Support Package shall be valid for a period of twelve (12) months from the Commencement Date. Any unused hours or credit remaining in the Available Balance at the expiration of the Validity Period shall automatically expire and be forfeited by the Client without refund or credit. MoveData shall not be obliged to provide any notice prior to the expiration of unused hours or credit.
2.3. Additional Packages. Where the Client exhausts the Available Balance of a Pre-Paid Support Package, the Client may purchase additional Pre-Paid Support Packages at any time. Each additional Pre-Paid Support Package shall be subject to its own Validity Period calculated from its respective Commencement Date.
2.4. Scope of Pre-Paid Support Packages. Pre-Paid Support Packages are designed and intended to provide: (a) support for the Client’s MoveData integrations; (b) customisation and enhancement of MoveData integrations; and (c) technical assistance directly related to MoveData’s integration services. MoveData expressly reserves the right to determine, in its reasonable discretion, whether requested services fall within the scope of Pre-Paid Support Packages or constitute general Salesforce support. Pre-Paid Support Packages are not intended for, and shall not be used for: (a) general Salesforce administration, configuration, or support unrelated to MoveData integrations; (b) training on core Salesforce functionality unrelated to MoveData; (c) development or support of Salesforce functionality that does not interact with or relate to MoveData integrations; or (d) services that would typically be provided by an internal Salesforce System Administrator or traditional Salesforce consulting partner.
2.5. Non-Refundable. Pre-Paid Support Packages are non-refundable, and no refund or credit shall be provided for: (a) unused hours or credit at the expiration of the Validity Period; (b) partially used Pre-Paid Support Packages; or (c) any other circumstances, except as may be required by law.
4. Requirements: MoveData
As instructed by the Client. MoveData will make timesheets available for all work performed.
5. Requirements: Client
The following is required in addition to the Client obligations under the Professional Services Agreement.
1. Development Environment
1.1. Provision of Development Environment. The Client shall provide MoveData with access to a development environment that accurately mirrors the Production environment in all material respects.
1.2. Client Responsibility for Environmental Discrepancies. Where: (a) functionality developed by MoveData passes acceptance testing in the development environment; (b) the same functionality is deployed to Production; and (c) an error occurs in Production that did not occur in the development environment, then the Client shall be solely responsible for remediating such error, and MoveData shall have no liability for any losses, damages, costs, or expenses (including consequential losses) arising from such environmental discrepancies.
1.3. Environment Stability. The Client warrants that during MoveData’s development activities, the development environment shall: (a) remain accessible without interruption; (b) not expire, be decommissioned, refreshed, or have data restored; and (c) not be subject to substantial configuration or structural modifications, without MoveData’s prior written consent.
1.4. Breach Remedy. Any breach materially impacting MoveData’s ability to develop or test functionality entitles MoveData to time extensions and reasonable additional fees for necessary rework.
2. Acceptance Testing and Production Deployment
2.1. Deployment Schedule. Upon functionality successfully passing acceptance testing in the development environment, the Client and MoveData shall agree on a schedule for deployment to the Client’s Production environment.
2.2. Client Responsibility for Production Errors. Where errors, defects, or data corruption occur in Production following deployment of functionality that passed acceptance testing in the development environment, and such errors arise from: (a) differences in configuration, settings, or parameters between environments; (b) inadequate or insufficient testing conducted by the Client; (c) differences in data, datasets, or data quality between environments; (d) environmental factors, integrations, or dependencies not replicated in development; or (e) any other discrepancies between environments, then MoveData shall have no obligation or liability to remediate, correct, or reprocess any records or data processed in Production.
2.3. Exclusion of Liability. MoveData shall not be liable for any losses, damages, costs, or expenses (including consequential losses) arising from Production errors resulting from environmental discrepancies.
2.4. Client Acknowledgment. The Client acknowledges sole responsibility for ensuring environment parity, conducting appropriate testing, and maintaining adequate backups prior to Production deployment.
3. Client-Controlled Functionality
3.1. Acknowledgment of Client-Controlled Processes. The Client acknowledges that its Salesforce environment may contain functionality not directly controlled by MoveData, including Salesforce Flows, Apex Triggers, Process Builders, Workflow Rules and other custom automations.
3.2. Triggering of Client-Controlled Functionality. The Client acknowledges that Client-Controlled Functionality may be automatically triggered when MoveData creates, updates, or modifies records in the Client’s Salesforce environment.
3.3. Exclusion of Responsibility and Liability. MoveData shall have no responsibility or liability for: (a) the design, configuration, operation, or performance of Client-Controlled Functionality; (b) errors, defects, failures, or data corruption arising from execution of Client-Controlled Functionality; (c) conflicts or adverse interactions between MoveData’s Services and Client-Controlled Functionality; or (d) any losses, damages, costs, or expenses (including consequential losses) arising from Client-Controlled Functionality.
4. Salesforce Governor Limits
4.1. Nature of Governor Limits. The Client acknowledges that: (a) Salesforce imposes governor limits to manage computational resources, API calls, and system utilisation; (b) Governor Limits are established by Salesforce and are outside MoveData’s control; and (c) exceeding Governor Limits may result in processing failures, errors, or service interruptions.
4.2. MoveData’s Compliance. MoveData designs its standard Services to operate within applicable Governor Limits.
4.3. Factors Outside MoveData’s Control. Governor Limits may be exceeded due to: (a) customisations or modifications made by the Client to MoveData’s integration; (b) Client-Controlled Functionality triggered when MoveData creates or updates records; (c) data volume, complexity, or frequency requirements; (d) third-party integrations or processes; or (e) limitations on the Client’s Salesforce subscription level.
4.4. Exclusion of Responsibility and Liability. MoveData shall have no responsibility or liability for: (a) Governor Limit breaches arising from factors described in clause 3; (b) failures or interruptions resulting from Governor Limit exceedances; (c) investigating or remediating Governor Limit issues not caused by MoveData’s standard Services; or (d) any losses, damages, costs, or expenses (including consequential losses) arising from Governor Limit exceedances.
5. Source Platform Uptime
5.1. Nature of Integration Services. The Client acknowledges that: (a) MoveData provides integration services that depend upon third-party platforms from which data is extracted; (b) MoveData relies upon Source Platforms to issue, transmit, and deliver data in accordance with the Source Platform’s specifications; and (c) MoveData does not own, control, or operate any Source Platform.
5.2. Source Platform Issues. The Client acknowledges that Source Platforms may experience: (a) outages, downtime, or service interruptions; (b) performance degradation, latency, or throttling; (c) API changes or modifications; (d) errors or defects in functionality; (e) data quality issues, including incomplete, inaccurate, or delayed data; or (f) authentication or access restrictions.
5.3. Exclusion of Responsibility and Liability. MoveData shall have no responsibility or liability for: (a) failures, delays, errors, or interruptions arising from Source Platform issues; (b) data loss, corruption, or inaccuracy resulting from Source Platform problems; (c) inability to access or process data due to Source Platform unavailability; or (d) any losses, damages, costs, or expenses (including consequential losses) arising from Source Platform issues.
5.4. Client Acknowledgment. The Client acknowledges and accepts the inherent risks of relying upon third-party Source Platforms beyond MoveData’s control.
6. Source Platform Data Integrity
6.1. Data Receipt and Processing Model. The Client acknowledges that: (a) MoveData operates as an integration service receiving, transforming, and transmitting data between Source Platforms and the Client’s Salesforce environment; (b) MoveData has no control over the content, accuracy, completeness, or quality of data issued by Source Platforms; (c) MoveData receives and processes data in the form provided by Source Platforms; and (d) MoveData’s Services process data without independently verifying the underlying accuracy of source data.
6.2. Reliance on Source Data. MoveData applies configured transformations and business logic but does not validate the accuracy or completeness of data provided by Source Platforms.
6.3. Exclusion of Responsibility and Liability. MoveData shall have no responsibility or liability for errors, defects, or data corruption arising from: (a) inaccurate, incomplete, outdated, or corrupted data issued by Source Platforms; (b) data issued in incorrect formats or sequences; (c) data not being issued or transmitted when expected; (d) delays, duplicates, or inconsistencies in source data; or (e) any losses, damages, costs, or expenses (including consequential losses) arising from source data quality issues.
6.4. Client Responsibility. The Client is solely responsible for implementing data validation and quality assurance processes.
7. Source Platform Changes
7.1. Acknowledgment of Platform Evolution. The Client acknowledges that Source Platforms may make changes to APIs, data structures, authentication, business logic, or integration methods at their sole discretion without prior notice or coordination with MoveData.
7.2. MoveData’s Reasonable Endeavours. MoveData shall use reasonable commercial endeavours to: (a) maintain relationships with Source Platform providers where practicable; (b) monitor for announcements regarding planned changes; and (c) implement necessary updates to maintain compatibility where MoveData receives reasonable advance notice.
7.3. Exclusion of Responsibility and Liability. MoveData shall have no responsibility or liability for failures, errors, or service interruptions arising from Source Platform changes where: (a) the Source Platform does not provide MoveData with advance notice; (b) insufficient notice is provided to allow MoveData to develop and deploy updates; (c) the Source Platform implements changes before MoveData completes necessary modifications; or (d) the change requires substantial redevelopment work.
7.4. Remediation Services. Changes requiring substantial redevelopment work may be treated as additional services at MoveData’s professional services rates.
7.5. Service Interruptions. The Client acknowledges that Source Platform changes may result in temporary or prolonged service interruptions requiring reasonable remediation time.
8. Source Platform Supported Functionality
8.1. Limited Scope. The Client acknowledges that: (a) MoveData’s integration is limited to specific objects, fields, and functionality available within Source Platforms; and (b) Supported Functionality may vary between platforms and change over time.
8.2. Client Due Diligence. The Client shall: (a) review MoveData’s documentation to verify Supported Functionality meets requirements prior to executing this Agreement; and (b) not assume functionality is supported unless expressly confirmed in writing or identified in documentation.
8.3. Unsupported Functionality. MoveData may, at its sole discretion, develop unsupported functionality as additional services subject to separate agreement and fees.
8.4. Exclusion of Liability. MoveData shall have no responsibility or liability for: (a) failure to integrate unsupported functionality; (b) data loss or unavailability resulting from unsupported functionality; or (c) any losses, damages, costs, or expenses (including consequential losses) arising from unsupported functionality not being integrated.
8.5. No Implied Warranties. MoveData makes no warranty regarding comprehensiveness of integration or suitability for particular purposes.
9. Environment Configuration and Parity
9.1. Client Configuration Changes. The Client acknowledges that it may be required or may elect to make changes to its Salesforce or other system environments to facilitate MoveData’s Services, including: (a) adding values to picklists or enumerated fields; (b) creating or modifying custom fields, objects, triggers, or automations; (c) adjusting permissions, profiles, or validation rules; or (d) modifying page layouts, record types, or configurations.
9.2. Environment Parity. The Client shall ensure that any Client Configuration Change is replicated consistently and accurately across all environments, including: (a) the development environment provided to MoveData; (b) the Production environment.
9.3. Exclusion of Liability. MoveData shall have no responsibility or liability for: (a) errors or failures arising from the Client’s failure to maintain environment parity; (b) functionality operating correctly in one environment but failing in another due to configuration discrepancies; or (c) any losses, damages, costs, or expenses (including consequential losses) arising from environment disparity.
10. Record Matching and Mapping
10.1. Default Behaviour. The Client acknowledges that MoveData’s default behaviour (with the exception of Contacts and Accounts (NPSP) or Person Accounts and Accounts (NPC) which utilise the Salesforce Duplicate Rules for record matching purposes) is to create new records and does not attempt to match or update existing records unless specifically configured otherwise.
10.2. Optional Record Matching. If the Client requires matching to existing records: (a) MoveData shall provide documentation and guidance regarding Record Matching configuration; but (b) the Client is solely responsible for configuring, implementing, and testing Record Matching logic, including identifying matching criteria, handling multiple matches, and defining update behaviour.
10.3. Client Responsibility. The Client acknowledges that: (a) MoveData has no knowledge of or context regarding the Client’s existing records and data quality; (b) the Client possesses the necessary business knowledge to determine appropriate matching criteria; and (c) Record Matching effectiveness depends upon Client configuration and data quality.
10.4. Exclusion of Liability. MoveData shall have no responsibility or liability for: (a) failure to match existing records due to inadequate configuration or data quality; (b) creation of duplicate records; (c) incorrect matching to wrong records; (d) errors, data corruption, or unintended modifications to matched records; or (e) any losses, damages, costs, or expenses (including consequential losses) arising from Record Matching issues.
11. Historical Data Import
11.1. As-Is Basis. The Client acknowledges that any import of historical data, records, or information is performed on an “as-is” basis.
11.2. No Control Over Historical Practices. The Client acknowledges that: (a) MoveData has no control over, knowledge of, or responsibility for how Historical Data was originally captured, recorded, structured, or maintained; (b) Historical Data may have been captured using different systems, processes, standards, or conventions than currently in use; (c) Historical Data may contain inconsistencies, variations, quality issues, or anomalies resulting from legacy practices; and (d) the Client possesses greater knowledge of its Historical Data and historical business practices than MoveData.
11.3. No Obligation to Accommodate. MoveData has no obligation to modify, adapt, normalise, or develop custom logic to accommodate historical variations, inconsistencies, or legacy formats.
11.4. Client Responsibility. The Client is responsible for cleansing, normalising, or preparing Historical Data prior to import if specific quality standards are required.
11.5. Exclusion of Liability. MoveData shall have no responsibility or liability for: (a) errors, data corruption, or processing issues arising from Historical Data quality or inconsistencies; (b) Historical Data that does not meet expectations; or (c) any losses, damages, costs, or expenses (including consequential losses) arising from Historical Data import issues.
12. Salesforce User License Requirements
12.1. User License Requirement. The Client shall provision and maintain a valid, active Salesforce user license for MoveData’s Salesforce access.
12.2. License Configurations. (a) MoveData recommends a dedicated System Administrator license assigned exclusively for MoveData’s Salesforce access. (b) Alternatively, MoveData’s Salesforce access may use a shared System Administrator license, subject to the Client acknowledging risks including permission conflicts and troubleshooting difficulties. (c) If System Administrator access is unavailable, MoveData’s Salesforce access may use a custom profile license, provided the Client: (i) warrants the custom profile contains all necessary permissions for MoveData to perform the Services; (ii) conducts thorough testing in a non-Production environment to verify fitness for purpose; (iii) promptly adds permissions as reasonably required; and (iv) accepts responsibility for any functionality limitations resulting from insufficient permissions.
12.3. Prohibited License Types. MoveData cannot function with Salesforce API-Only user licenses.
12.4. Exclusion of Liability. MoveData shall have no responsibility or liability for any failures, errors, delays, or losses (including consequential losses) arising from: (a) invalid, improperly configured, or insufficient user licenses or permissions; or (b) use of incompatible license types.
13. Error Notifications and Monitoring
13.1. Error Notification System. The Client acknowledges that: (a) errors may occur from time to time during operation of the Services; and (b) MoveData will send automated email notifications of errors to the email address designated by the Client in MoveData’s settings.
13.2. Client Obligations. The Client shall: (a) designate and maintain a valid, active Notification Email Address at all times; (b) ensure error notification emails are not blocked by spam filters or security measures; (c) actively and regularly monitor the Notification Email Address; (d) promptly review and respond to error notifications; and (e) immediately update the Notification Email Address if it becomes invalid or unmonitored.
13.3. Satisfaction of Notification Obligation. MoveData’s obligation to notify the Client of errors is satisfied by sending email notifications to the Notification Email Address.
13.4. Exclusion of Liability. MoveData shall have no responsibility or liability for any losses, damages, costs, or expenses (including consequential losses) arising from: (a) the Client’s failure to maintain or monitor a valid Notification Email Address; (b) error notifications not being received or reviewed due to Client email configuration issues; or (c) delays in error detection or remediation resulting from inadequate Client monitoring.
14. Acceptance Testing Period
14.1. Testing Period. The Client shall have fourteen (14) days from the delivery date of any functionality developed by MoveData to conduct acceptance testing and notify MoveData in writing of any defects, errors, or non-conformities.
14.2. Deemed Acceptance. If the Client: (a) does not conduct acceptance testing within the Testing Period; or (b) does not provide written notice of rejection specifying defects or non-conformities within the Testing Period, then the delivered functionality shall be deemed accepted by the Client as of the expiration of the Testing Period.
14.3. Effect of Deemed Acceptance. Upon deemed acceptance: (a) the functionality is considered to conform to specifications and to be fit for purpose; (b) the Client waives any right to reject the functionality or claim defects except for latent defects that could not reasonably have been discovered during the Testing Period; and (c) payment obligations (if any) relating to the accepted functionality become due.
14.4. Client Responsibility. The Client acknowledges that it is solely responsible for conducting thorough and timely acceptance testing within the Testing Period.
14.5. Notification Requirements. Any rejection notice must specify in reasonable detail the nature of defects or non-conformities and provide evidence supporting the rejection.