Guides and Tools
Mirror or Migrate: Decide Before You Move
Activating trusted enterprise intelligence without a forklift migration. An interactive walkthrough of Trusted Data Mirroring, built for the conversation you are about to have.
Watch the Briefing
How do you move the estate, and what does the business need to use right now? Those two questions decide whether you mirror or migrate.
Data Migration asks how to move the estate. Data Mirroring asks what the business needs to use right now.
The traditional answer to enterprise AI has been a large data migration. Copy the data into a new platform, validate it, rebuild permissions, reconcile duplicates, and only then begin analytics and AI. That sequence delays value and often transfers existing data problems into a more expensive environment. Redundant, obsolete, trivial, sensitive, and poorly owned information does not become trustworthy simply because it has been moved.
Zantaz Trusted Data Mirroring changes the sequence. Smart Stack 3.0 discovers and refines information in place, creates governed Trusted Data Collections, and publishes the resulting intelligence into the customer's Microsoft Fabric Lakehouse as open Delta tables. For supported sources such as SharePoint, OneLake shortcuts provide governed access to the original files without creating a second bulk copy. Understand first, activate what matters, and move only when a business requirement demands it.
Compare the Two Strategies
Flip the switch to see how each decision factor changes.
Primary Objective
Activate curated intelligence while the source remains authoritative.
Relocate data into a new system.
Activate curated intelligence while the source remains authoritative.
What Is Moved
Curated tables and approved content, with pointers or shortcuts to original files.
Selected files, content, and supporting metadata.
Curated tables and approved content, with pointers or shortcuts to original files.
Time to Value
Begins incrementally with the first approved collection.
Often follows planning, transfer, validation, and cutover.
Begins incrementally with the first approved collection.
Source Impact
Existing workflows can continue during activation.
May require freezes, cutover, or decommissioning.
Existing workflows can continue during activation.
Primary Cost Drivers
Refinement, publishing, and processing of approved high-value data.
Engineering, transfer, staging, duplicate storage, testing, and remediation.
Refinement, publishing, and processing of approved high-value data.
Governance Sequence
Applied upstream before downstream use.
Frequently reconstructed after ingestion.
Applied upstream before downstream use.
Best Fit
AI, analytics, discovery, governance, and faster activation without bulk relocation.
System retirement, consolidation, application replacement, or required relocation.
AI, analytics, discovery, governance, and faster activation without bulk relocation.
Migration is a relocation strategy. Trusted Data Mirroring is an activation strategy.
Where Value Appears on the Timeline
The same estate, two sequences. Only one of them delivers usable intelligence early.
Forklift Migration
Value waits for the program to finish.
Trusted Data Mirroring
Value begins with the first approved collection.
Size the Difference
Move the inputs to see what an activation-first sequence avoids. These are directional estimates, not a quote.
493TB
Duplicate raw storage not created in the destination.
240.3M
Estimated ROT files excluded from downstream processing.
33.8TB
High-value information activated in Fabric first.
6
Migration workstreams removed from the critical path.
Assumptions: average file size of 1.2 MB, roughly five percent of the estate per activated collection, and selective staging of a fifth of the refined content. Actual results depend on source platforms, retention rules, existing contracts, Fabric capacity, and the scope approved for activation.
Eight Business Benefits of Data Mirroring
Open each one to see what it changes for the enterprise.
Traditional migrations can spend months in discovery, planning, transfer design, remediation, validation, cutover preparation, and reconciliation before the business receives useful insight. Data Mirroring lets a team start with a defined collection such as a department, audit scope, legal matter, legacy share, or AI use case and publish it directly into Fabric. Depending on scope, readiness, and approvals, useful datasets can become available in weeks instead of being tied to the completion of a broad migration program.
Choose the Least Disruptive Action That Satisfies the Requirement
Mirroring is the default for activation. Physical movement stays available when the use case genuinely requires it.
What Moves
Manifests, curated metadata, business-ready tables, and source references.
What Stays
The authoritative files remain in their existing system of record.
Best For
Analytics, discovery, dashboards, and AI grounding.
Is It a Mirror or a Migration?
Select every statement that is true for the scope you have in mind.
Recommendation
Mirror first, then decide what needs to move.
Nothing in this scope requires relocation. Publish the Trusted Data Collection into the customer's Fabric Lakehouse, let the business use it immediately, and keep the original system authoritative.
Who Benefits Across the Enterprise
CIO and Infrastructure
A faster path to modernization without committing every use case to a large relocation program.
CDO and Data Teams
Curated, documented, analytics-ready collections rather than raw file sprawl.
CISO and Privacy
Earlier visibility into sensitive information, ownership, and access context.
Legal and Compliance
Traceable, matter-specific or policy-specific collections for review and defensible action.
AI and Analytics
High-signal datasets that are easier to understand, query, and govern.
Business Leaders
Insight sooner, with less cost and disruption than a broad migration program.
A Practical Enterprise Adoption Path
Prove value without making an enterprise-wide migration the price of admission.
- 01Select the ScopeAn audit, department, legal matter, migration candidate, or Copilot use case.
- 02Scan and Refine in PlaceDiscover the estate without relocating it first.
- 03Create the CollectionA Trusted Data Collection with defined ownership, policies, and business purpose.
- 04Mirror into FabricPublish the collection into the customer's own Lakehouse.
- 05Measure the OutcomeTime saved, data excluded, storage avoided, risks identified, decisions enabled.
- 06Expand on Proven ValueAdd collections based on demonstrated business demand.
Move only when movement is required. Mirror when the objective is intelligence.
One clarification matters. Microsoft also provides mirroring services that replicate operational databases into OneLake. These are complementary concepts, not identical ones. Zantaz focuses on activating refined, governed unstructured information without requiring a wholesale file migration. The enterprise gains speed without abandoning control, modernization without unnecessary duplication, and AI readiness without first moving every file it owns.