Having just used this for the first time, there are a number of things that I think are important to know -

1. Before you use this you must delete any existing sandbox. This is a huge leap of faith for those of us with very customized instances. Luckily for me, I have multiple instances and was able to work with a newer one with less overhead than our main instance. If I had used this with that one I would have been extremely unhappy.

2. Although a number of items were created, they were not usable as is and required significant review to get correct: Not all views were created, triggers were not in the correct order, customer lists were not created, etc.

3. Custom ticket fields do not have the same field numbers and any reference to those fields will be incorrect. So references within emails to to a custom field must be reviewed and revised; also triggers, automations, and anything else.

4. All agent login emails are changed. That's not a problem except that the passwords are also changed, so an agent can't log in with the changed email to reset their password or their email. An administrator must manually change either the password or the email for each agent that will be using the sandbox. If you have a lot of agents and light agents this can be a huge time waste.

5. The sandbox doesn't include even a stripped-down version of the Guide, so there's no way to test/train using a new request form.

Given these restrictions, it's not as easy as we are lead to believe to create a new test or training environment. Using my starter instance it took many days to confirm that everything was the same as production. For the primary instance, which has over 150 triggers, macros, and views, over 30 custom fields and 10 forms with conditions, I'm not sure that this is usable as is. If I need to review every item I'd rather maintain the existing sandbox and review anything that's changed. In my opinion, this needs more work to be usable for anyone maintaining a more complicated system.