Federate
Keep content in existing repositories and use SCM as the cross-repository control plane.
SCM REPOSITORY
A modern home for content you choose to consolidate.
SCM is designed to support both federated content and a managed repository strategy. Keep existing systems connected, move selected content into SCM Repository, or adopt a hybrid model.
CHOICE, NOT RIP AND REPLACE
Federate, migrate or combine both.
Migrate
Consolidate selected content into SCM Repository as migration capabilities are adopted for your source systems and requirements.
Hybrid
Move the content that benefits from consolidation while continuing to connect repositories that should remain systems of record.
REPOSITORY MODEL
Designed to work with the SCM platform.
The SCM Repository direction brings managed content storage into the same operating model as Universal Search, SuperQL, Super Inspector, Smart Taxonomy, Smart Tasks and Governance. Repository capabilities and migration fidelity depend on the implemented release and source-system requirements; SCM does not assume every legacy feature maps one-for-one.
Content + metadata
Maintain content and structured metadata in a normalized SCM content model.
Versions + provenance
Preserve useful version and source context where supported by the migration path.
Search + inspection
Make repository content available to SCM discovery, query and inspection experiences.
Automation + governance
Apply SCM workflow and governance capabilities to managed content as those controls are configured.
ONE PLATFORM, MULTIPLE STRATEGIES
Keep what works. Move what should change.
SCM gives content programs a path between permanent federation and all-at-once migration.
Plan Your SCM Architecture