Migrate the CUI You Actually Have, Not the CUI You Think You Have
Enclave builds and tenant migrations are usually scoped from an inventory someone assembled by asking around. That inventory decides how large the destination needs to be, how long the project takes, and what it costs.
Teramis identifies and validates the actual CUI footprint before the move. After findings are confirmed, authorized personnel can remediate or migrate the CUI to a secure, approved location. Teramis can then verify that the source locations have been cleared.
A migration is only complete when the CUI has been moved to an approved location and the source has been verified.
You Can Only Migrate What You Know About
Migration projects are scoped from an assumed data set. When that assumption is wrong, the consequences show up late and cost real money:
- The destination is sized for less data than actually needs to move
- CUI is discovered mid-project, forcing rescoping and schedule changes
- Licensing and infrastructure estimates are built on an incomplete picture
- Data is copied rather than moved, leaving CUI in the original location
- Nobody can confirm the source was cleared after cutover
- The next discovery scan finds CUI still sitting in the environment you thought you left
The migration succeeds on paper while the boundary problem stays exactly where it was.
Establish What Actually Needs to Move
Teramis examines approved data sources to identify where CUI exists across the current environment, including locations the migration plan may not account for.
That gives the project team:
- A file-level view of what is in scope for the move
- Repository and location detail for planning sequence and effort
- Findings in locations the inventory did not include
- A basis for sizing the destination environment
- Evidence to support licensing, infrastructure, and timeline estimates
- A documented baseline to compare against after cutover
Size the destination from findings, not from a survey.
Move Data With a Record of What Happened
Remedius supports movement of identified CUI from file systems, SharePoint, and OneDrive into the destinations your organization authorizes, preserving source folder structure and verifying successful transfer using hash comparison before source files are removed.
File conflicts and unsuccessful transfers are reported rather than passed over, so nothing is assumed to have completed.
Authorized Destination
Movement is directed only to destinations approved by your organization.
Structure Preserved
Source folder structure can be maintained during supported movement workflows.
Transfer Verified
Hash comparison helps verify successful transfer before source removal.
Exceptions Reported
Conflicts and unsuccessful transfers remain visible for review.
What Teramis Does Not Do
- Approve or design the destination environment
- Decide which data must move
- Perform the broader IT migration outside CUI scope
- Provide licensing, infrastructure, or architecture recommendations
- Guarantee a migration outcome or an assessment result
- Make legal or contractual determinations
Projects That Depend on Knowing the Footprint First
Enclave Builds
Scope and size the enclave from the actual CUI footprint rather than an estimate.
Cloud and Tenant Migrations
Move CUI into an approved cloud environment and confirm the source is cleared.
Tenant Consolidation
Identify CUI across multiple tenants or domains before consolidating.
System Retirement and Decommissioning
Confirm what CUI a legacy system holds before it is retired, and verify that nothing was left on it.
Post-Acquisition Integration
Establish the CUI footprint of an acquired environment before merging it.
Explore Supply Chain and M&AYour Organization Sets the Destination and Approves the Move
Your organization defines the authorized destination, approves which data moves, sets the sequence, and makes final CUI handling decisions. Teramis identifies what is in scope, supports the approved movement, verifies transfers, reports conflicts and failures, and documents the result.
Your Organization
- Defines the authorized destination
- Approves which data moves
- Sets migration sequence and timing
- Makes final CUI handling decisions
Teramis
- Identifies what is in scope
- Supports approved CUI movement
- Verifies supported transfers
- Reports conflicts and failures
- Documents the result
What Teramis Does Not Do
- Approve or design the destination environment
- Decide which data must move
- Perform the broader IT migration outside CUI scope
- Provide licensing, infrastructure, or architecture recommendations
- Guarantee a migration outcome or an assessment result
- Make legal or contractual determinations
Know What Needs to Move Before You Size the Destination
Talk with Teramis about your migration timeline, your target environment, and the data sources you need examined first.