Probably the key thing that I would recommend to anybody when they're looking or considering this is you can only really do so much prep before it, and you can only know how much pain it's going to be until once you start. You can do small text bikes, and you can do estimation session after estimation session and trying to work out how heavy each one of those assets is gonna be, but it's not really known until you get into the mix of it. Yeah. For sure. I'd say we probably spent, what, half a week looking at various bits of data that I could pull from from Looker in terms of utilization, in terms of complexity of each of the different dashboards that we wanted to try to rebuild. Yeah. I think we were probably fairly accurate with, like, how difficult those would be. We we point based them, didn't we? Yeah. I think we did a good job there. I think what I think our learning that we both said at the end of it is that we some of it because you had an existing semantic layer was migrating a semantic layer, and then there was after that building. And I think we ended up going back and forth between building and then editing the semantic layer a bit, whereas maybe we both said we would have, like, spent way more time completely nailing down, obviously, given more than four weeks, nailing down the semantic layer. Because once the semantic layer was in, building became incredibly easy. Yeah. So I think that is, like, one thing that we both said in the retro. And I think another thing that you've mentioned is, like, you were obviously incredibly analytical, but you had people that had all the business context, which I also think is a really key, like, success criteria of any migration, which is, like, professional services obviously can help do the migration. They can fully own the migration, but having someone with business context is, yeah, invaluable. Yeah. I think it's vital. You can only do so much from a technical perspective unless you understand what the data is actually related to.