salesforce-data-migration-orchestrator

Plan and execute Salesforce data migrations with staged loads, reconciliation, and cutover controls.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-data-migration-orchestrator-amanpraaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: salesforce-data-migration-orchestrator
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/salesforce-data-migration-orchestrator
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill salesforce-data-migration-orchestrator-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Enterprise Salesforce data migrations fail when mappings are unvalidated, loads are uncontrolled, and reconciliation is skipped, leading to data loss and broken referential integrity. This Skill provides a structured workflow for planning, executing, and verifying high-volume data migrations. ## Core Features & Use Cases - Mapping Validation: Validate source-to-target field mappings and transformation rules before any data moves. - Staged Bulk Loads: Run pilot loads, then execute staged bulk migrations with checkpoints for controlled progress. - Reconciliation & Cutover: Verify record counts, referential integrity, and business totals, then finalize cutover with hypercare checks. - Use Case: When moving millions of Account and Contact records from a legacy CRM into Salesforce, use this Skill to validate mappings, run a pilot load, reconcile counts and relationships, and manage the final cutover. ## Quick Start Use the Salesforce data migration orchestrator to plan and execute a staged migration of legacy CRM records into Salesforce with reconciliation checks.

Frequently Asked Questions about salesforce-data-migration-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate large volumes of data into Salesforce?▼

Migrate large data volumes into Salesforce using a staged approach: validate source-to-target mappings, run a pilot load, execute staged bulk loads with checkpoints, then reconcile record counts and referential integrity before cutover.

How to validate field mappings before a Salesforce data migration?▼

Validate field mappings by reviewing source-to-target mapping definitions and transformation rules against the target Salesforce schema before loading any data. This catches type mismatches, missing required fields, and incorrect transformations early.

What reconciliation checks should I run after a Salesforce data load?▼

Run three core reconciliation checks after a Salesforce data load: record count parity between source and target, referential integrity across related objects, and business total parity such as summed amounts or statuses.

Why do Salesforce data migrations fail during cutover?▼

Migrations fail during cutover when pilot loads are skipped, reconciliation is incomplete, or referential integrity breaks under full data volume. Staged loads with checkpoints and hypercare checks after cutover reduce these failures.

When should I use a pilot load in a Salesforce migration?▼

Use a pilot load before the full staged migration to test mappings and transformation rules on a representative data subset. It surfaces mapping errors and performance issues without risking the complete dataset.