MBM360 Migration Policy

Effective Date: June 9, 2025
Last Updated: December 31, 2025

This Migration Policy applies exclusively to MBM360, the integrated operating system for mental health associations operated by Mentally Balanced Media OmniCorp (“MBMO”).

This policy governs transitions from MBM Ascend, legacy MBM360 offerings, or prior MBM services into the current MBM360 Integrated OS model.

1. Purpose of Migration

MBM360 is an evolving operating system. From time to time, clients may transition from:

  • MBM Ascend
  • legacy MBM360 plans or services
  • prior MBM-delivered systems or workflows

into the current MBM360 Integrated OS, which may include:

  • Core Platform access
  • Activated Operations Departments
  • Automation, reporting, and infrastructure upgrades

Migration is intended to modernize systems—not to replicate legacy environments exactly.

2. Scope of Migration

Migration may include, where applicable:

  • account restructuring
  • data mapping or selective data transfer
  • workflow reconfiguration
  • automation replacement or consolidation

Not all legacy systems, data structures, or workflows will transfer on a one-to-one basis.

MBM360 reserves the right to redesign, replace, or retire legacy elements in favor of standardized, supported architecture.

3. No Guaranteed Equivalency

Clients acknowledge that:

  • legacy tools, layouts, automations, or processes may not exist in the Integrated OS
  • feature parity is not guaranteed
  • historical data may be selectively migrated or excluded

Migration prioritizes stability, scalability, and long-term maintainability, not preservation of deprecated systems.

4. Client Responsibilities

Successful migration requires timely client participation.

Clients are responsible for:

  • providing accurate and complete data
  • responding to requests for clarification or approval
  • validating migrated outputs
  • backing up any legacy data prior to migration

Failure to engage does not pause migration timelines, billing, or platform activation.

5. Data Integrity & Limitation of Liability

While MBM360 uses commercially reasonable efforts during migration:

  • Data loss, corruption, or formatting changes may occur
  • MBM360 does not guarantee completeness or accuracy of migrated data
  • MBM360 is not liable for loss of historical records, configurations, or metadata

Clients are solely responsible for retaining copies of legacy data.

6. Third-Party Platforms & Dependencies

MBM360 is not responsible for delays, failures, or data issues caused by:

  • third-party platforms or integrations
  • discontinued legacy tools
  • API limitations or vendor outages
  • client-provided systems or credentials

Third-party systems operate outside MBM360’s control.

7. Timing & Availability

Migration timelines vary based on:

  • system complexity
  • data volume
  • third-party dependencies
  • client responsiveness

Timelines are estimates only, not guarantees. Migration does not entitle clients to expedited service unless expressly agreed in writing.

8. Billing During Migration

Migration does not pause:

  • Core Platform billing
  • Operations Department billing
  • contracted service terms

Capacity and resources are reserved upon activation, regardless of migration status.

9. No Outcome or Performance Guarantees

Migration does not guarantee:

  • improved performance
  • increased revenue
  • growth outcomes
  • feature availability

MBM360 provides infrastructure and operational systems—not results.

10. Migration Acceptance

By continuing to use MBM360 after migration:

  • clients accept the migrated environment “as delivered”
  • legacy environments are considered retired
  • MBM360 has no obligation to restore prior systems

Requests to revert or rebuild legacy configurations are treated as new, scoped services.

11. Relationship to Other Agreements

This Migration Policy supplements, and does not replace:

  • MBM360 Terms of Use & Client Agreement
  • Privacy Policy
  • Payments, Billing & Cancellation Policy

In the event of conflict, the Terms of Use & Client Agreement control.

12. Governing Law

This Migration Policy is governed by the laws of the United States and the State of Texas.

International users acknowledge that migration services are delivered under U.S. contractual standards.