Data imports
MoveData only processes information from the time your integration is connected. It does not automatically go back in time to find data from before your integration was set up. If you need historical data imported into Salesforce, you need to arrange a data import.
Data imports let you bring that historical data into Salesforce through MoveData, ensuring your records follow the same mapping and duplicate-matching rules as live transactions.
When you need a data import#
You may want a data import if you:
- Connected a fundraising platform after it had been collecting donations for months or years.
- Switched from a manual data entry process to MoveData and need to backfill records.
- Added a new platform that already has historical transaction data.
Note
Whether to run a sandbox dry run before production is your call. A sandbox import lets you review the data before it lands in production, but it doubles the cost of the import. See Choosing sandbox vs production below for guidance.
Self-service imports for file-based platforms#
Some platforms use file uploads rather than live API connections. If your platform supports file-based uploads, you can import historical data yourself by uploading historical files through your existing integration.
To run a self-service import:
- Download your historical data files from the fundraising platform.
- Open the MoveData app in Salesforce.
- Go to your integration and click Upload File.
- Select the file and upload it.
- Monitor the resulting notifications for any errors.
Success
Start with a small date range to verify that records are mapped correctly before uploading your full history.
Professional import service#
For platforms that use API connections (such as Raisely, JustGiving, or Funraisin), historical data is not available through file upload. MoveData offers a professional import service where the MoveData team retrieves and processes that data for you.
What to expect#
Once you've requested an import, the flow is:
- Submit your request — email support with your Salesforce org ID, the integration IDs you want backdated, the date to backdate to, and whether you'd like a sandbox dry run first.
- MoveData runs the import —
- Production only: MoveData pulls the historical data and imports it directly into your production org.
- Sandbox first: MoveData imports into your Salesforce sandbox for you to review. Once you confirm the records look right, MoveData runs the same import against production.
- Invoicing — MoveData raises an invoice for the work.
Choosing sandbox vs production#
Both paths are supported. Pick whichever fits the import you're requesting.
Production only is usually fine when:
- Your integration is already running cleanly against the same platform.
- The data you're backdating is recent and you're confident in its quality.
- You want to keep the cost down.
Sandbox first makes sense when:
- The import covers a long history and you're not sure how the older data will land.
- You want to review the records — mapping, duplicates, campaign attribution — before committing them to production.
- You'd rather spend the extra hours than risk a clean-up later.
A sandbox dry run doubles the cost of the import — it's the same work performed twice (once in sandbox, once in production). See Pricing below.
Pricing#
MoveData charges 4 hours per platform per environment. Whether you choose production-only or sandbox-first determines how many environments are billed:
| Path | Hours per platform |
|---|---|
| Production only | 4 |
| Sandbox + production | 8 |
Multiply by the number of platforms in scope — so importing two platforms straight into production is 8 hours total, while a sandbox-first import for the same two platforms is 16 hours total. For the applicable hourly rate, see the MoveData Professional Services page.
Important considerations#
- Sandbox environment (when used) — if you opt for the sandbox path, you'll need to provide a sandbox that matches your production configuration. If testing passes in sandbox but issues arise in production because of environmental differences, you're responsible for remediation.
- Existing records — MoveData does not automatically map imported data to existing Salesforce records. If you have records in Salesforce that need to be matched during the import, you are responsible for preparing that mapping.
- Data quality — imports proceed on an as-is basis. MoveData processes whatever data the source platform provides and does not verify or correct data quality issues originating from the source.
- Large volumes — MoveData reserves the right to decline imports with very large data volumes (hundreds of thousands of records), as the tool may not be suitable for such projects. Contact your account manager to discuss your specific requirements.
How to request an import#
Email support@movedata.io with:
- Your Salesforce org ID.
- The integration IDs you want backdated.
- The date you want data backdated to.
- (Optional) Whether you'd like a sandbox dry run before the production import.
MoveData confirms scope and runs the import. An invoice is raised once the work is complete.