Applicable plans: ❎ The free plan, ✅ The complete plan, ✅ On-demand plan
🕵️♀️ When relocating teams from multiple buildings or areas to a new building location—it’s critical to ensure a smooth transition that minimizes disruption to users. |
ℹ️ Information:
- You can move an area in building A to building B only within the same Entity.
- You can move a building A to a different Entity.
✅ Recommended Method: Seamless Transition Without Disrupting Week Patterns
- Create the New Building
- In the Waldo admin portal, navigate to Desks and parking and create the new building.
- Move Existing Areas to the New Building
- If you're using preferred zones or not, move all the areas from the old building to the new one.
- In the Waldo admin portal, navigate to Desks and parking. Then open the Entities.
- Select the building whose area you want to move and ✏️ edit the name of the area.
- On the building entry name, press, Then change the target building and Save. - This preserves all existing configurations and avoids user-side disruptions.
- If you're using preferred zones or not, move all the areas from the old building to the new one.
- Rename the Old Building (Optional but Recommended)
- Go to the Resources page in the Waldo admin portal.
- Rename the original building to reflect the change (e.g., "Old building") and save.
- Re-assign Seats in the New Building Map
- On the building map page, re-assign all seats to their corresponding new locations and save.
By following this approach:
- Users do not need to manually update their week patterns in the Waldo app.
- All existing and future reservations (even older months) automatically reflect the new building.
- The transition appears seamless from the user’s perspective.
💡 This method has been tested in the Waldo app and shown to correctly carry over all reservation data to the new building.
⚠️ Alternative Method: Start Fresh (Not Recommended for Large Moves)
A second approach is to:
- Create anew building from scratch.
- Manually add new areas and seat maps.
- Assign seats in the new building as needed.
However, this method has a major drawback:
- All users must manually update their week patterns in the Waldo app.
- This can lead to confusion, missed reservations, and a poor user experience.
✅ Is the First Method Safe?
Yes, based on testing and practical usage:
- The preferred method (moving areas and re-assigning seats) is safe and effective.
- It ensures that all booking data remains consistent, and users experience no disruption to their existing patterns or schedules.
Final Tip
Before implementing the move:
- Communicate the change clearly to users.
- Let them know the move will be handled automatically via the Waldo app.
- Provide support contacts in case users experience issues post-move.
Comments
0 comments
Please sign in to leave a comment.