Mainframe Tape to Cloud Migration with VirtualZ™

Executive Summary

Enterprises migrating tape data to the cloud have two distinct paths, depending on how that data will be used after migration.

VirtualZ supports both approaches, allowing organizations to modernize tape storage without forcing a one-size-fits-all architecture.

  • PropelZ™ is ideal when tape data is being replicated and transformed for analytics, AI, reporting, or downstream applications.
  • FlowZ™ is ideal when tape data must remain file-based and continue to be accessed by z/OS applications, even after moving to cloud storage.

Both solutions are out-of-the-box, zIIP-eligible, and cloud-agnostic.

Modernizing Tape Storage for 2026

Physical tape and virtual tape libraries remain reliable — but they are no longer economical or flexible enough for modern enterprise needs. Organizations are migrating tape data to the cloud to:

  • Reduce storage and maintenance costs
  • Improve access to historical data
  • Eliminate hardware refresh cycles
  • Support modernization, analytics, and compliance initiatives

VirtualZ enables this transition without custom code, without application rewrites, and without operational disruption.

FlowZ vs. PropelZ for Tape Migration

How to Choose the Right Approach

Both FlowZ and PropelZ can be used for tape-to-cloud migration. The right choice depends on two key questions.

Key Question Choose PropelZ™ Choose FlowZ™
How will the data be stored in the cloud? Database tables Files / object storage
Will z/OS applications access the data after migratioin? No Yes
Primary use case Analytics, AI, reporting Archive, backup, active tape
Replication only? Yes No
Application changes required No No
Cloud & on-prem support Yes Yes
zIIP eligible Yes Yes

In summary, use PropelZ when:

  • Tape data is being copied off the mainframe
  • The destination is a database
  • Data will be consumed by analytics, AI, or cloud applications
  • z/OS applications will not continue accessing the data

And use FlowZ when:

  • Tape data must remain file-based
  • z/OS applications must continue reading or writing tape data
  • Cloud storage should behave like an extension of existing tape infrastructure

Key Capabilities (Both Solutions)

  • Automated Tape Data Discovery: Automatically identify and catalog datasets across physical tape and VTL environments.
  • High-Volume Migration: Optimized batch processing minimizes network impact and operational risk.
  • Cloud & On-Prem Support: Supports AWS, Google Cloud, Azure, IBM Cloud, and low-cost on-prem object storage.
  • Data Integrity & Validation: End-to-end verification ensures migrated data is complete and accessible.
  • Cost Optimization: Reduce or eliminate the expense of physical tape libraries and VTL platforms.
  • zIIP Eligibility: Migration workloads can run on zIIP engines, reducing general-purpose CPU usage.

Benefits of Tape to Cloud Migration with VirtualZ

  • Lower Storage Costs: Replace fixed, capital-intensive tape infrastructure with scalable cloud storage.
  • Improved Access to Historical Data: Make tape data usable by modern platforms without complex ETL pipelines.
  • Elastic Capacity: Scale storage up or down based on actual needs.
  • Resilience & Security: Leverage cloud encryption, replication, and durability features.
  • Operational Simplicity: Install, configure, and run — without rewriting applications or changing workflows.

Conclusion

VirtualZ enables organizations to modernize tape storage on their own terms.

  • PropelZ™ is best when tape data is being replicated and transformed for downstream use.
  • FlowZ™ is best when tape data must remain actively accessible to z/OS applications after migration.

Both approaches eliminate legacy tape inefficiencies while preserving performance, governance, and control.

Next Steps

Learn More

Latest Blog Posts

PropelZ™ 2.0 Is Here

PropelZ™ 2.0 Is Here

Built from the Real World, Ready for What’s Next Enterprise data teams don’t need another tool with theoretical capabilities. They need solutions shaped by real workloads, real constraints, and real feedback — from the environments they operate in every day. That’s...

VSAM to PostgreSQL: 460K Records in 25 Seconds

VSAM to PostgreSQL: 460K Records in 25 Seconds

460,000 VSAM Records. 25 Seconds. Into PostgreSQL. With PropelZ™. A global outsourcer recently shared a powerful proof point from a large retail customer: “[A large retailer] just loaded 460K VSAM records into a PostgreSQL database on Google Cloud in 25 seconds.”...