Lot of the customers I talked to, they might have just renewed for a year, but they know migration's big and important to get right. So I guess, yeah, do you have any advice for those people? I do. I think the the first thing is keep keep trying to refine every single time you get a request for a particular asset coming through that needs to be migrated and look at every single part of it, the number of dashboards that we had that we were told we would need the entirety of from Looker that we ended up cutting maybe even fifty percent of that, which actually just wasn't necessarily useful, was significant. And maybe that's just to get ground at the time where we'd had, like I said, sort of six years worth of build up of extra assets. I think that was key, trying not to sort of waste time on things that just are no longer used. Use as much of the kind of the tooling that you can from the tools on the utilization and engagement. And if you can, and use any of the sort of AI tools out there. I was using Cursor an awful lot to script and pull information from the Looker APIs to look at those engagement levels and really try and create a good idea of what is being used on that platform, and then ratify that with your stakeholders, make sure that they agree with you with what you're suggesting is likely to be the key usage things.