Consolidate Multi-Org Salesforce into unified Salesforce today

Roll-Up Summary fields are formula-based aggregations that depend on parent-child relationships to recalculate. During the migration, our transformation layer preserves the parent-child lookups and the Roll-Up Summary field definitions, but the calculations don’t trigger until Salesforce’s native recalculation engine processes the data—this typically happens within 24 hours after the final data load completes. We recommend scheduling migration completion during a low-activity window and validating Roll-Up Summary totals the following business day. If you need immediate recalculation, Salesforce can manually trigger this via a support case, but we’ll provide you with a validation report showing expected vs. actual values to confirm the calculations are correct.

Attachment migration is our highest-latency operation—2TB across 5 orgs typically takes 4-6 weeks when accounting for extraction, deduplication, and incremental loading. We use a phased approach: weeks 1-2 involve extracting metadata and smaller attachments (under 100MB) from all orgs, weeks 3-4 handle large file transfers in parallel across org batches to avoid destination org API throttling, and weeks 5-6 cover reconciliation and re-attachment validation. Your production orgs remain fully operational throughout—we work against a staging copy of your data first, and only sync delta changes (new/modified attachments) during the final cutover window, which is typically 2-4 hours per org. We’ll establish a clear go/no-go checkpoint after week 2 so you can decide whether to proceed or optimize file volumes before the full migration.

SuprSwitch’s deduplication engine uses a multi-pass matching algorithm that detects duplicates within each source org and across all source orgs simultaneously using weighted scoring on Account name, billing address, phone, website, and custom identifier fields you specify. You configure deduplication rules upfront—strict (exact match only) or fuzzy (allows typos and minor variations)—and we generate a pre-migration report showing identified duplicates and our recommended merge strategy. During the actual migration, duplicate Accounts are consolidated into a single record in the destination org, child records (Contacts, Opportunities, Cases) are reassigned to the merged parent, and we maintain a comprehensive duplicate lineage report for audit purposes. If you disagree with a proposed merge, you can mark specific duplicates as ‘keep separate’ and we’ll migrate them as distinct records—there’s no one-size-fits-all rule here, and we prioritize your business logic over automation.

Territory Management in Multi-Org setups creates complexity because each org maintains independent territory hierarchies, account assignments, and rule sets—the destination Salesforce org can’t natively ‘import’ these as-is without conflicts. SuprSwitch maps each source org’s territory hierarchy into a unique prefix structure in the destination org (e.g., ‘NA_West_Org1’, ‘NA_West_Org2’) and uses Account custom fields to track original territory ownership by source org. This preserves assignment rules and prevents territory orphaning, but it doesn’t automatically deduplicate overlapping territories—you’ll need to manually consolidate territories post-migration if desired. We recommend planning your target territory structure before cutover and using our pre-migration assessment to identify overlaps; we can also optionally freeze new territory assignments during the migration window to prevent data loss from concurrent changes in source orgs.