Data transfer activity is rarely identical from one month to the next.
One month, your organization may move several large research datasets. The next month may involve fewer transfers while teams wait for sequencing results, imaging files, study approvals, vendor deliveries, or partner submissions.
Many subscription services follow a use-it-or-lose-it model. Any capacity left at the end of the billing period disappears, even though the customer has already paid for it.
MLADU takes a more flexible approach.
With an eligible MLADU monthly subscription, unused allotted transfer bytes can roll forward for future use. This helps your organization preserve more of its subscription value, manage irregular data transfer requirements, and prepare for larger transfers without wasting unused monthly capacity.
Monthly data transfer rollover allows unused transfer capacity from your MLADU subscription to remain available after the month ends.
For example, suppose your monthly subscription includes 1 TB of data transfer capacity and your organization uses only 700 GB during the month. The remaining 300 GB can roll forward, subject to MLADU’s rollover policies and accumulation limits.
Instead of losing that unused capacity, your organization can apply it toward future data transfers.
This makes MLADU a better fit for organizations whose data movement changes according to research schedules, project milestones, partner activity, operational requirements, or seasonal demand.
Organizations should not have to lose the value of unused transfer capacity simply because their data was not ready before the end of the month.
MLADU rollover helps preserve eligible unused transfer bytes so they can support future work.
Research and enterprise data movement is often unpredictable.
A genomics program may receive a large sequencing delivery one month and very little data the next. A consortium may collect information quarterly. A biotechnology company may receive major deliveries when a study phase or vendor milestone is completed.
Rollover gives organizations more flexibility to accommodate these natural changes.
Unused monthly transfer capacity can help your organization prepare for a future transfer that exceeds its regular monthly allowance.
This can be especially valuable when planning for:
Rollover can make it easier to align data transfer spending with actual operational demand.
Instead of losing unused capacity during slower months and purchasing additional capacity during busier months, organizations can retain eligible unused transfer bytes for later use.
This can reduce waste and help teams plan their transfer budgets with greater confidence.
A use-it-or-lose-it allowance can encourage teams to move data before it is operationally, scientifically, or administratively ready.
MLADU rollover reduces that pressure. Your organization can focus on moving the right data at the right time rather than rushing to consume an expiring monthly allowance.
Every eligible MLADU monthly subscription includes an allotted amount of transfer capacity.
When your organization does not use the full monthly allotment, the eligible unused balance rolls into the next month automatically.
Your organization can accumulate rollover capacity up to the applicable maximum.
The maximum rollover balance is calculated using the monthly subscription allotments from the previous four months. This approach accommodates organizations that maintain the same plan as well as customers whose subscription capacity changes over time.
Suppose your organization has received 1 TB of monthly transfer capacity for each of the previous four months.
Your maximum accumulated rollover capacity would be:
1 TB × 4 months = 4 TB
Your actual rollover balance would depend on how much of the monthly capacity remained unused during those months.
The 4 TB figure represents the maximum rollover capacity, not an automatic additional allotment.
Suppose your organization received:
The total subscription capacity provided during those four months would be:
500 GB + 500 GB + 1 TB + 1 TB = 3 TB
Your maximum rollover capacity would therefore be 3 TB.
Your actual available rollover balance would be based on the eligible unused capacity remaining from those subscription periods.
This method allows the rollover limit to reflect changes in your monthly subscription.
Consider a research organization with a 1 TB monthly plan:
| Month | Monthly capacity | Capacity used | Unused capacity |
|---|---|---|---|
| January | 1 TB | 600 GB | 400 GB |
| February | 1 TB | 800 GB | 200 GB |
| March | 1 TB | 500 GB | 500 GB |
| April | 1 TB | 900 GB | 100 GB |
Across these four months, the organization has 1.2 TB of eligible unused capacity.
Subject to MLADU's rollover rules and any other usage during that period, the organization could retain that capacity for a future transfer instead of losing it at the end of each month.
Monthly rollover can be especially valuable for organizations that move large amounts of data on uneven schedules, including:
These organizations may have months of intensive transfer activity followed by quieter periods. MLADU rollover helps the subscription adapt to those operational cycles.
Consortium participants may submit data at quarterly milestones rather than every month. Rollover allows unused capacity from quieter periods to support higher-volume submission periods.
A research team may need to wait for a sequencing facility, imaging center, laboratory, or external vendor to complete a dataset. Accumulated capacity can help support the transfer when the data becomes available.
An organization preparing for a future migration can preserve unused transfer capacity during the planning period and use it when migration work begins.
Some organizations experience predictable peaks tied to study schedules, annual programs, client deadlines, fiscal periods, or operational events. Rollover provides greater flexibility across these cycles.
An urgent project, new collaboration, or unplanned partner delivery may require more capacity than originally anticipated. An accumulated rollover balance can provide additional flexibility without requiring the organization to start from zero.
Unused rollover capacity cannot be transferred, sold, or reassigned to another MLADU customer account.
Unused transfer capacity cannot be converted into a cash payment, refund, or account credit.
Organizations can accumulate eligible unused capacity only up to the applicable rollover maximum. The maximum is based on the subscription allotments provided during the previous four months.
Rollover capacity supplements the flexibility of an eligible MLADU monthly subscription. It does not replace the subscription's other pricing, usage, overage, cancellation, or service terms.
Customers should review their subscription agreement and current MLADU pricing documentation for complete details.
MLADU was designed for organizations that move large, important, and complex datasets.
Those organizations should not be forced into a rigid pricing model that assumes transfer activity will be perfectly consistent every month.
Monthly rollover gives customers more time to use eligible transfer capacity they have already purchased. It supports better planning, reduces unnecessary waste, and allows the subscription to align more closely with real data transfer schedules.
It is one more way MLADU helps organizations make large-scale data movement simpler, more predictable, and more cost-effective.
Use the MLADU Pricing Calculator to estimate the transfer capacity that may be appropriate for your organization.
For help evaluating irregular, seasonal, quarterly, or large-scale transfer needs, schedule a conversation with the MLADU team.
Topics
ON THIS PAGE
ASK A QUESTION
Can't find what you're looking for? Our team is here to help.
Try MLADU Free
Experience the power of AI powered data transfers.
No credit card required