<aside>
🛠️
We're upgrading Hubfleet's maintenance management system. New customers are already on the new system. Existing customers will be migrated with no data loss and minimal disruption.
</aside>
At a glance
- New customers use the new system immediately
- Existing customers will be migrated in phases
- New and old systems will run in parallel during migration
- No data or access will be lost
Migration steps
- Outreach and scheduling
- We will contact your team to confirm timing and next steps for migrating your maintenance data.
- Enable the new system (parallel run)
- We will turn on the new maintenance system for your account while keeping the old system active.
- You will not lose any data or access to existing records during this period.
- Configure the new system together
- We'll guide you to set up configuration so the new experience matches your operations.
- Configure parts and task custom fields:
- Create your reusable building blocks:
- Set up service programs and assign to assets:
- How service programs work in the new system
- Service programs no longer cascade as in the legacy system.
- Create separate programs for each service type (for example, "A Service" and "B Service").
- Combine and schedule these conveniently through the new Work Orders feature.
- Mapping review meeting
- Once configuration is complete, we will book a session to confirm how your legacy data maps to the new structure.
- Automated migration
- After mapping is confirmed, we will migrate historical data into the new system automatically.
- Validation meeting
- We will meet again to verify that records, schedules, and configurations have moved across successfully.
- Deactivate the old system
- After you confirm everything looks good, we will switch off the legacy maintenance module for your account.
What stays the same vs. what changes
- What stays the same
- All your historical data remains available. Nothing is deleted during migration.
- Your team retains access throughout the parallel run period.