Req. Number
Req 2.85: The Supplier shall ensure that all configurations,...
📋 Requirement Details
Req 2.85: The Supplier shall ensure that all configurations, templates, policies, and device lists can be exported for potential migration to another MDM solution.
⚙️ Technical Demonstration
IMTLazarus completely satisfies this requirement by providing built-in, unrestrictive data extraction capabilities across the entire multi-tenant dashboard environment. The platform is designed with a core philosophy of data portability, ensuring that DepEd retains absolute ownership of its operational configurations and can extract all system components in open, structured formats without friction or proprietary roadblocks:
- Universal Format Export Engine: All core operational configurations—including device lists, hardware inventories, system policies, timetable templates, and restriction profiles—can be extracted on demand. The system avoids encrypted or proprietary data structures, outputting all files into universally readable formats such as CSV, JSON, or XML that are standard for ingestion into alternative enterprise management systems.
- Granular and Bulk Data Extraction: Administrators possess the flexibility to export assets at any tier of the organizational hierarchy. Central ICT administrators can trigger a comprehensive, nationwide bulk export of the entire fleet database, while division or school-level managers can isolate and export specific sub-tenant device lists and local policy templates independently.
- Identity and Mapping Preservation: When exporting device metadata and inventory lists, the platform maintains standard identifiers (such as hardware serial numbers, IMEI numbers, MAC addresses, and assigned organizational unit paths). This structured approach ensures that the relational mapping between devices and their respective DepEd organizational tiers remains completely intact for seamless translation to another MDM solution.
Data Portability and Migration Extraction Schema
The platform maps its system components to standard, open-format outputs to support external system migration:
| MDM Component | Extraction Format Options | Included Operational Metadata | Migration Utility |
| Device Inventories | CSV / JSON | Serial Numbers, IMEI, MAC Addresses, OS Versions, Hardware Specs, and Active Tags. | Allows immediate bulk enrollment and asset matching in a new platform. |
| Organizational Blueprints | JSON / XML | Multi-Tenant Hierarchy Mappings, Sub-Tenant Boundaries, and Role-Based Permissions. | Preserves the administrative structure and directory alignment without rebuilding. |
| Filtering & Security Policies | JSON | Web Category Configurations, URL Allow/Blocklists, Keyword Triggers, and App Blacklists. | Serves as a clear, plain-text policy reference for translating rule behaviors into alternative engines. |
| Timetables & Templates | JSON / CSV | Instructional Scheduling Parameters, Access Window Flags, and Temporal Policy Triggers. | Retains the specific time-based filtering schedules designed for DepEd classrooms. |