Syntharil copies the metadata you choose from one org to another — code, automation, layouts, profiles and permission sets — production-safe, with incremental re-clones after the first run.
Keeping two orgs’ configuration in sync by hand is slow and error-prone — and the further a sandbox drifts from production, the less your testing means. Metadata clone moves the org’s shape the same way replication moves its data: pick what you want, run it, and re-run incrementally as things change.
Authorize both orgs over OAuth — the same connections your data jobs use.
Choose from 28 supported types, from Apex classes to Flows to Permission Sets.
The first run clones everything selected. Later runs move only what changed since, tracked per type.
Apex classes, triggers, Visualforce pages and components, Lightning Web Components, Aura components, and static resources.
Flows, workflow rules, approval processes, validation rules, and duplicate/matching rules.
Record types, global value sets, custom tabs, apps, page layouts, FlexiPages, and quick actions.
Profiles and Permission Sets — the part of org setup nobody wants to rebuild by hand.
Reports and dashboards, folders included.
Custom labels, custom metadata records, custom settings, and email templates.
Deploys adapt to the target. Into a sandbox, changes apply partially and skip test runs, so iteration stays fast. Into production, every deploy runs all local Apex tests and applies per-group rollback — a failed group rolls back rather than leaving the org half-changed. After the first clone, per-type change tracking makes re-runs incremental, and deletions at the source propagate to the target so the two orgs genuinely converge.
Moving data too? Replication can run an inline metadata phase — see sandbox replication →. Just need to understand the org? MetaSwitch documents it for AI →
Connect both orgs, pick the metadata types to clone, and run. Syntharil retrieves from the source and deploys to the target over the API — no manual packaging.
Yes. Profiles and Permission Sets are supported types, alongside code, automation, layouts, and configuration.
Production deploys run all local Apex tests and use per-group rollback, so a failing group reverts instead of leaving the org half-changed.
No. After the first clone, runs are incremental — each type tracks what changed since its last successful deploy.
Delete propagation removes it from the target on the next run, so the orgs converge instead of accumulating leftovers.
Yes — MetaSwitch exports the org’s data model as Markdown built for AI coding agents, which is often the right tool when the goal is understanding rather than syncing.