#iSyncSF – Salesforce-to-Salesforce Data Sync & Migration
Complete documentation for the iSyncSF managed package — the fastest way to copy, migrate, and sync data between Salesforce orgs.
Application Overview
iSyncSF is a Salesforce-to-Salesforce data synchronization application installed as a managed package. It allows...
1. Setup & Initial Configuration
Purpose: One-time and ongoing configuration of the application itself - OAuth credentials, performance tuning,...
2. Org Connection
Purpose: Establishes a secure, authenticated link between the source Salesforce org and one or more target...
3. Template Management
Purpose: Templates are the central configuration unit of iSyncSF. A template defines WHAT data to sync and HOW the...
4. Template Lines
Purpose: Template lines define the specific Salesforce objects to include in the sync and how to query them. While...
5. Object Settings (Advance Tab)
Purpose: Object Settings provide granular, per-object sync configuration. While template lines define WHICH objects...
6. Preview / Scan Tab
Purpose: The Preview/Scan feature lets users see exactly how many records will be included in the sync BEFORE...
7. Execute Tab
Purpose: The Execute tab is where data actually moves from source to target. It orchestrates the entire sync...
8. Sync History Tab
Purpose: The History tab provides a complete audit trail of all past sync executions for a template. It allows users...
9. Rollback
Purpose: Rollback provides a safety net - if a sync produces undesired results (wrong data, too many records, data...
10. Application Logs
Purpose: Application logs provide real-time visibility into what the sync engine is doing during execution. They...
11. Org Compare
Purpose: Org Compare is a pre-sync validation tool that ensures the target org s schema matches the source org. If...
12. Automation Control
Purpose: Automation Control manages the target org s automations (triggers, validation rules, flows, workflow rules)...
13. Data Masking
Purpose: Data masking protects sensitive information (PII, financial data, confidential fields) when syncing data to...
14. Field Mapping & Expressions (Detailed)
Purpose: The field mapping and expression system is the intelligence layer of the sync engine. It determines: (1)...
15. Sync Behavior Options
Purpose: These options control fundamental sync behaviors at the template level - how the engine handles ongoing...
16. Scheduled Background Jobs
Purpose: Scheduled jobs handle automated maintenance and operational tasks that keep the application healthy without...
17. Callback Extensibility System
Purpose: The callback system allows developers to extend the sync behavior with custom logic at specific points in...
18. REST API / External Integration
Purpose: The REST/SOAP API endpoints serve two roles: (1) The DataSyncReceiver endpoint runs on the target org and...
19. Security & Permissions
Purpose: The security layer controls who can do what within iSyncSF. Custom permissions provide feature-level access...
20. Data Model (Key Objects)
Purpose: These custom objects store all configuration, execution state, and audit data for the application....
21. Typical User Workflow
This document covers all functionality of the iSyncSF (SF2SF Data Sync) application as of Spring 2026. It is...
FAQ
Common questions about iSyncSF sync errors, Salesforce exceptions, sandbox seeding, and troubleshooting
Troubleshooting
Diagnose and fix common sync failures including scan issues, validation errors, OAuth problems, and performance
File & Attachment Migration
Sync Salesforce files, attachments, and ContentVersion records between orgs with size-aware transfer
System Configuration Reference
Complete reference for system properties, custom metadata settings, and performance tuning options
Cleanup & Maintenance
Manage storage with scheduled log cleanup, audit log retention policies, and record deletion tools
Sandbox Seeding Use Case
Step-by-step guide to safely copying production data to a sandbox with PII masking and rollback
Org-to-Org Migration Use Case
Migrate data between Salesforce orgs for consolidation, platform changes, or org splits