Your first sync
How SchemaForce builds your baseline snapshot and keeps your schema current.
When you connect an org, SchemaForce crawls your org's metadata and stores a first snapshot as your baseline. The initial crawl runs in the background — you can watch its progress during onboarding.
What the first snapshot captures
The baseline captures the structure of your org, not its data:
Standard and custom objects, with their labels and API names.
Every field, its type, and its configuration.
Lookups and master-detail links between objects.
Record types defined on each object.
The rules that gate writes in your org.
Layouts and the picklist value sets they use.
Building history
From that baseline, change history accumulates automatically.
History can't be backfilled
SchemaForce can only track changes that happen after you connect — history can't be reconstructed retroactively. The sooner you connect an org, the more history you'll build.
Staying current
SchemaForce keeps your schema current in three ways:
Daily incremental sync
A scheduled sync re-reads only what changed since the last run — fast and low-overhead.
Periodic full reconciliation
A full re-crawl runs on a slower cadence to catch anything an incremental sync might miss.
Sync now
Trigger a sync manually any time from the org's page — useful right after a big deployment.
Always read-only
Everything here is metadata-only, and syncing never writes to your org. The only write SchemaForce ever makes is the opt-in Push to Salesforce action for field descriptions you explicitly confirm.