account-sync

You can sync segments, flows, jobs, and connections between two Lytics accounts by executing a metadata copy command with source and destination profiles. The process remaps internal IDs and preserves object dependencies.

The safest way to migrate account-level configurations is using a dry-run sync to preview changes before applying them. This creates reproducible promotions by remapping internal IDs and dependencies while keeping the source account intact.

Yes, you can preview metadata changes using the dry-run flag to perform a diff operation. This shows exactly what will be created or updated before any actual modifications are committed to the destination account.

Yes, the sync supports a create-only flag that restricts operations to creating new objects without modifying or overwriting existing metadata. This prevents accidental updates to established flows, jobs, and connections in the target account.

You can trace and audit metadata transfers by enabling trace data appending during the sync operation. This provides a record of synced segments, schema fields, and account settings to support auditing and rollback procedures.

Cross-account sync requires per-account profile files for credential derivation and cannot transfer objects with unresolved external dependencies. It focuses on metadata like flows, jobs, and settings rather than underlying audience data.