Salesforce to Salesforce migration.

Why the Salesforce → Salesforce migration goes wrong

Salesforce-to-Salesforce sounds easy until you actually do one. Salesforce-to-Salesforce native broke at 100 records per transaction for a reason. Six places it quietly breaks:

• Cross-org identity resolution. Two orgs from an M&A integration both have a Contact named "John Smith" with the same email. One has him as primary at AccountA, the other as a relationship contact at AccountB. Which survives? The decision has to be deterministic, replayable, and aware of household structure.
• Polymorphic lookups + record types. Task.WhatId, Event.WhoId, Note.ParentId, polymorphic lookups break if either side's record types don't align. Record-type ID mapping is the silent killer of org merges.
• Managed package data. NPSP, FSC, Health Cloud, Pardot, CPQ, managed-package objects have prefixed namespaces, package-licensed fields, and post-install scripts. The package version on the target org has to match (or be migrated forward coherently) or post-install triggers corrupt the load.
• OWD + sharing rules + ownership. Owner mapping across orgs is rarely 1:1. Role hierarchies and sharing rules don't always re-derive. Records can land orphaned (owned by integration user, invisible to the original owner's team) without warning.
• Apex triggers + flows. The target org has its own triggers and Flows. A bulk load fires them at scale. Pre-load, suppress them. Post-load, replay them deterministically. The "data is in but the rollups are wrong" complaint traces here most of the time.
• Field history + audit trail. Field history isn't natively portable cross-org. Most tools simply drop it. Compliance auditors notice. Pathfinder carries field history forward as a typed custom object the audit chain can verify.

Deliverables

• Workspace archive at completion. Your data, packaged. Source-org Bulk API extracts, transform mappings, identity resolution decisions, every dry-run trace, every gate decision.
• Signed audit chain. Every cross-org record movement chained via SHA-256, sealed every 256 leaves with Ed25519. Your auditor verifies the chain on her own laptop. Protocol published →
• NPSP-aware mapping (where applicable). Households, Relationships, Affiliations, RD2 recurring plans, GAU Allocations, preserved across the move.
• Replay manifest. Every migration is replayable. The compliance-review conversation that used to take six weeks runs in forty minutes.