Alrighty. Make a five minutes pass the half hour. Let's kick things off. So first of all, I'd like to welcome everyone to today's webinar on tab Tableau Clyde. If this is your first time coming across Interworks, welcome. If you don't know who we are, we're a a data and analytics consultancy with, we've been operating for over twenty five years, and we deal with things, all things on the data and analytics spectrum whether it be data engineering, data architecture, data strategy, data governance, or analytics, enablement, all things on the spectrum. For those of you that have come across us before, you may be familiar with this particular series, we, run these webinars about once a month on topics that we see are are are are talked about most talked about in the market, and today's topic is moving to Tableau Cloud. So I recommend you visit the Interworks blog. We'll find more info about the technologies that we support and some great reading on migrating to Tableau Cloud as well. We are known for our blog, so be sure to check it out if you get a chance. Go ahead go ahead and follow the interworks, inter interworks LinkedIn edge as well, where you'll see plenty of, updates on all things, all the latest things that we're coming up with. A few reminders and housekeeping for today's session, we will be recording this session. It will be on our website in a few days, and we'll send you an email if you've registered, to let you know when it's available to access. One quick favor that we do ask is to please use the Q and A function in Zoom today. To help us keep track of any questions. So there is a chat function in there, but please use the Q and A function. If you have any questions, and we'll endeavor to answer as many questions as we can at the end of the session. Keep an eye on the question queues, and we will kick things kicked off. Next slide, John. Thank you. So today, my name is Bill Clark. I'm the regional lead, an APAC West for interworks. So looking after WA essay in Southeast Asia. So for me, it is one thirty in the afternoon, just after. And we have John Saunders, who is usually based in Perth in Western Australia, but is joining us today from, the wonderful island of Sicily and Italy, I believe. So, welcome, John. Thank you. Thanks, Bill. It's I'm a platform's architect, with Intworks and and happy to take you through, tablet cloud today. So let's have a quick look at the agenda. So we're very excited to have you joining us to take the first step towards migrating to Tableau into a has dedicated a lot of thought towards ensuring our clients are well informed and prepared for the complexities of migrating from Tableau server to Tableau Cloud. So do a simple introduction to Tableau cloud and reiterate some of the many reasons you might be considering migration. Next we'll cover a set of factors that should be well understood before migrating. Excuse me. Would then talk about the effort that is reducing friction, to pave way for a smooth migration. And we'll offer some strategies for planning your migration. We'll then get into a few logistics surrounding the hands on effort And finally, we'll talk about maximizing, your new tablet cloud environment and ways you can use a time once consumed by administrative overhead to shape, your, your analytics culture within your organization. So to begin, we'd like to take a poll and and really understand where are you at with your Tableau cloud right now. I'm seeing lots of interactions already. Thank you for that. We'll give folks another Thirty seconds or so to pop in their answers. Thus far, we're seeing a roundabout just over twenty percent, currently on Tableau Clyde. Around about thirty two percent still on Tableau server, but want to migrate to Tableau Clyde. Give a few more seconds. There's a lot of folks on here, John, unsure if we're ready to migrate the top blue cloud. So perfect audience, or for today's session. Absolutely. Well, thanks for your your feedback day. So I think we can end the poll and and we'll move on. Thanks, Bill. So that into works, we're passionate about finding relatable ways to navigate complex transitions. That's why we found this moving house analogy to be a perfect fit for com capturing the essence of migrating from Tableau server to tablet cloud. Just as moving from a house in the Burbs to an apartment complex in the city brings about a shift in environment, dynamics, and daily routines. Transitioning your Tableau deployment from an on premise server to a cloud based infrastructure involves similar considerations. In this webinar, we'll dive into the parallels between these two experiences, exploring how the analogy illuminates key insights strategies, and best practices for a successful migration journey. My next side button doesn't wanna play today. So consider our analogy and the reasons why you may consider migrating from Tableiservo, your house in the Burbs. Is your team grappling with the juggling act between vital projects and maintaining an on premise tableau server. As your Tableau community flourishes, the call for instant insights and seamless collaboration intensifies. Are you are the surging demands of your expanding user base becoming a challenge? We know that changes are constant in the business world. Be it a shift in direction, leadership, or grappling with understaffing. Adaptability is Lynch bin. Are you driven by these lifestyle changes? Perhaps you're wrestling with the sprawl of growing content. Struggling to secure swift access to a single source of the truth. Now let's step into the bustling city complex that is a Tableau cloud and uncover why this migration holds. I promise. Firstly, you gain access to the most recent version of Tableau. Complete with cutting edge features, some of these innovations, actually may not be, supported in Tableau server as yet. Furthermore, upgrades and updates become a seamless part of your experience. With tablet cloud, these enhancements are applied regularly and automatically ensuring you're always at the forefront of performance, functionality, and security. Real yourself from the shackles of administration tasks as you migrate to the SaaS solution, administrative overhead becomes a thing of the past. Revel in the freedom to channel your energy into tasks that truly add value to your organization's journey. At its core, Tableau cloud is a software as a service or SaaS offering. This cloud based form provides a dynamic and accessible environment for your data, exploration, and visualization needs. So what are the key benefits of tablet cloud? With Tableau, you're always equipped with the most recent version of Tableau complete with the latest features and enhancements. You gain access to the new tools that might not yet be available in the traditional Tableos service setups. Keeping you ahead of the analytics curve. Tableicloud automates the process of upgrades and updates. Ensure ensuring that you're seamlessly provided with the most current functionalities and performance improvements. Migrating to tablet cloud liberates you from the over, operational overhead, allowing you to focus on tasks that can contribute to, directly to business growth and insights generation. Tableicloud scalable nature ensures that you can effortlessly accommodate the expansion of your user base and data requirements. The cloud boat based approach ensures that insights are at your fingertips, whether you're in the office at home or on the go or fortunate enough to be working from Sicily. Tableic Cloud encourages real time collaboration and data sharing, enabling teams to work seamlessly together and making form decisions faster. Tableau Cloud almost eliminates the need for on premise hardware and complex set service setups. We'll dive into that later. This translates to lower infrastructure costs and simplified IT management. So we'd really love to know what your primary drivers are for migrating to tablet cloud. And you'll see another poll, popping up on your screen, hopefully. Yep. We're getting some inputs. Yeah. So thus far, the number one reason reduced administrative overhead of running Tableau server. I guess that's not unusual when it comes to obviously looking for a managed service. That's exactly why we're looking for one try to reduce that admin burden. So that would absolutely make sense as the number one reason. Interesting call out here is obviously cost and licensing considerations is really very, a very low percentage of people are interested in that. I think, you know, moving forward, that might be something that changes depending on how licensing and arc, and and the architecture costs themselves, the infrastructure costs. Sorry. Evolve, but, yeah, by far and away, the number one reason for everyone is to reduce that administrative overhead. I think we'd all love some time back in our day. Cool. Back to you, John. Right. Thanks, Bill. So shifting from tablet server to tablet cloud, means moving from a customized on network infrastructure to a shared ecosystem. In this realm, a standardized offering empowers all sites equally. The idea of having access to a maintained swimming pool, an in house gym, and someone else cleaning the gutters, sounds pretty nice. Right? But we've also have a chuckle, at the inner city apartment stories. The oversized four by four squeezing through the the low garage doors, the king-size bed incompatible with those snug bedrooms, and that beloved recliner disrupting the feng shui of the new open plan living. Just as city living brings its limitations and considerations, so does tablet cloud. So we'll take a closer look at these aspects and and view them from a lens of a cloud migration. Our aim here is to provide you with an unfiltered perspective, ensuring your decision is well informed and transparent. First, we'll dive into the administrative considerations when it comes to tablet cloud. Tablet cloud is always up to date with the latest version and features. You might not have a say in it, but as administrators, It's our role to ensure our user community are in the loop and ready for upgrades that come on Tableau's timeline. Regarding backups in Tableau server, we have the capability to create PS backfires. Which could be used to restore accidentally deleted essential content. However, this approach has changed with Tableau cloud. Any deleted data or workbooks is now permanently removed. Tableau cloud does not support individual site restores. The platform retains backups for a thirty day period, primarily intended for restoring the higher environment in the event of a significant system wide issue rather than recovering specific workbooks or content. You will no longer have access to your individual URL as you now exist as a site within Tableau's environment. This will result in a format such as AWS region dot online dot Tableau dot com slash your site name. When accessing your site. This one might be a bit obvious, but the TSM access is no longer available in in tablet cloud. Meaning that any custom scripts you previously used to manage Tableau's back end will no longer be applicable. However, tableau now handles these tasks autonomously. Your responsibility will be to understand and comply with the configuration restrictions that have been established. Access to the repository on Tableau cloud is not as unrestricted as it is on Tableau server. While direct access to the postgresql database is not possible, you do retain access to the administrative views and insights. We'll provide a link in the chat, for more information, but I I thought I'd quickly show you some examples of the inbuilt dashboards that are available in your admin insights data. So here we have, a sample of the overview of your Tableau cloud environment. We have, the user roles and license consumption. Groups, and their group memberships. Log in activity over time. Traffic to your views and data sources at a project level. The publishing trends of your workbooks and and dashboard a data sources, sorry, over time. Detail view of your stale content or unused content. And your space usage to track against your site capacity, which we'll dive in a little later. And if these template, views and and workbooks aren't catering to your specific requirements. Here are the data sources that are curated and published for you in your admin, insights that you can build your own workbooks from. When dealing with data sources, there are specific considerations. Firstly, when we refer to on premise, we are referring to any physical or virtual infrastructure that resides in your office data room, data center, or even your virtual private cloud VPC. Tableic cloud works best with cloud based data sources, such as Snowflake, and supports a wide range of data sources such as Google BigQuery, Amazon Redshift, Amazon RDS, Microsoft SQL through to your traditional MS SQL server. If you intend to retain on prem data sources, it's essential to establish a software package called Tableau Bridge. To facilitate data connection and data extract refresh. Once installed and configured, Tableau Bridge serves as a secure and reliable intermediary between on premise data sources and cloud based Tableau environments. Enabling regular data refreshes and ensuring that the analytics and insights presented in your Tableau cloud are based on the most current data. For any on premise data, careful planning is necessary. All data sources that are connected to on premise data must be published data source and cannot be embedded into your workbook. We'll dive into that more detail a little later as well. Notably, COBRA authentication is not supported for published connections within tablet cloud. Another layer that warrants careful consideration is authentication. Tableau cloud is compatible with system for cross domain identity management scheme, allowing you to automate the strange of identity information. You can provision your users autonomously. Multi factor authentication or MFA, is mandatory in the tablet cloud. You can use the inbuilt tablet cloud MFA or integrate with your IDP, such as okta or MS as your AD, with Samuel and and single sign on and NFA. Please ensure that all end users are informed and prepared before migration, especially if MFA is not already implemented in current Tableau service setup. At present, Tableau connected apps are designed to optimize the embedding of tableau views and metrics in external applications. They are u also used to authorize access to Tableau REST API. Here are some, a couple of significant, capacity considerations. On premise, file store capacity, in your Tableos server environment, is confined by the available disk space in the location of your file store process. This encompasses published data sources such as extracts flows, revisions, and more. As Tableau cloud imposes a hundred gigabyte light limit first sight. For some users, this may pose an immediate obstacle, unless the advanced management license is acquired, which elevates that limit from a hundred gigabytes to one terabyte. Moreover, there's a cat of fifteen gigabytes on the size of individual workbooks, data sources, or flows. I personally feel that if you had a workbook of size fifteen gig, we probably need to do some work in in optimizing that to start with. But that's the limit in the tablet cloud. There exists certain usage capacity constraints as well. Each purchased creator license provides eight hours of background at processing time. Simultaneous extract refreshes are capped at ten jobs, but this exceeds to twenty five. With the acquisition of advanced management license. All jobs are subject to a maximum run time of two hours. If you employ flow jobs, it's essential to have a data management license and obtain additional resource blocks if you intend to execute more than one flow concurrently. I do see that someone's raised their hand. We've got another poll I'll take that opportunity to dive into the Q and A, and see if we can answer your question whilst we're, Got the poll running. And, yeah, we'd love to know which considerations that we discuss would most resonate with your organization. Just give a give a second for it to get some of these results coming through. Obviously, a number of considerations, Joan, that you pointed out there. It looks like, the other source readiness and administrative limitations are the front runners. Thus far. Still got a few more people putting their votes in. It's great to get this sort of feedback. We have an question, from Ravi, the question is, is Tableau bridge required when using AWS Redshift I think I'll answer the question more broadly and say that if your database is, publicly accessible from the internet, then you you don't have to use Tableau bridge. But if it's hidden or or behind your corporate network, then, Tableau bridge would be required. Hopefully, that does answer your question there, Robbie. Perfect. Thank Sorry, John. All results are all in, administrative limitations and data source readiness tends to be the things that resonate most, with with folks. Based on your experience, John, obviously, as a platforms architect, is that something you come across regularly? My apologies, Bill. I was reading the the chat just as soon as you're speaking. So data source readiness and administrative limitations are the two, two most popular responses in terms of considerations. Is that in line with the conversations that you would have on a day to day as a data, as a as an architect? Yeah. A hundred percent down. Thanks, Bill. And and sorry for tuning you out earlier before. Right. So With the expertise in these areas at Intuitworks, we feel that we are great at assisting when addressing each of these considerations. Moreover, we are well equipped to offer solutions for instances where your organization may not align to this criteria. Now let's delve into the concept of reducing friction as you prepare for your migration. Having personally experienced numerous relocations, I've embraced Mary condos Fox Joy decluttering approach. Through this, I've come to understand the value of simplicity, time efficiency, cost effectiveness, and stress reduction by only carrying along those belongings that truly hold significance. Given the expanding and proficient user community, managing content sprawl and content governance poses a challenge for most organizations. Let's take a brief look at some elements you might contemplate streamlining before making the shift to Tableau cloud. Schedules. Schedules extend across the entire Tableau server, encompassing all sites within your current setup. At times, they can seemingly multiply exponentially. This juncture presents an excellent opportunity to evaluate what is generally utilized and necessary pinpointing areas where we can minimize or amalgamate tasks. Managing workbooks can swiftly become a challenging, particularly when Sandbox projects a host to redundant test workbooks, each cramped with revisions. It's crucial to pinpoint and define outdated unnecessary workbooks and eliminate them from your server. Since migration can involve substantial manual effort undertaking a comprehensive cleanup during the stage proves advantageous. In the event that you possess multiple sites, and aim to consolidate into a single Tableau cloud site. This presents an ideal opportunity to internally streamline operations. Consider rearranging or transferring content into a solitary site and reevaluating your permissions framework. While maintaining segregation through project level permissions, you can set the stage for internal success. Naturally, Table Cloud thrives with cloud hosting data sources and has innate compatibility with many of them. However, if you have on premise data sources you wish to retain, careful consideration is needed. These sources either need to be migrated to a cloud based data service, such as Snowflake, or you'll need to implement and maintain Tableau bridge. Workbooks embedding on premise data cannot be directly published to tablet. How publish these data sources separately, and subsequently can reconnect your workbooks to the published data sources? This circumstance may turn out to be advantageous as it could lead to a reduced overall data footprint. You might discover the potential to utilize a single published data source for multiple workbooks. A shift from the password duplicate data resided on your tableau server. Whether you're planning to migrate to Tableau cloud or not add into works, we believe that you should consider reducing the friction as your the benefits in your existing tablet server environment. And we have a stale content management offering that will archive your pre loved and unused workbooks data sources and much more automatically. With your sights set on the promise of what a simplified life would look like in Tableau Cloud, it's time to begin planning. If you are physically moving from one home to another, there'd never be a scenario in which you decide today that moving is right for you. And wake up tomorrow expecting to load your moving truck and hit the road. There's just too much to plan in between. In the same way, Intworks recommends a very thorough approach to planning your cloud migration. Let's walk through the four areas that we suggest you dedicate time, to planning. First, let's talk about governance. We've discussed, that a typical tablet cloud deployment supports only one site. Perhaps your current tablet serve environments utilizes different sites to distinguish sandbox content from production content. This calls for thought surrounding how you'll keep that sandbox content distinct. One of our favorite approaches involves using projects to separate business units, finance, marketing, sales, for example, And within each of these projects, a sandbox, Q and A, and production project appear as sub projects, with permissions applied respectively. You'll want to be sure that project structure, as well as who is responsible for the promotion of content within those projects are well defined. Depending on when you last updated your Tableau server, a migration to cloud could also open up semi exciting governance features for you, such as collections, which allow you to organize items into an easy to access list according to what's meaningful to you regardless of the project that that content lives in. And through And though, sorry, certified data sources have been available for some time on tablet server. This is also possible in tablet cloud. Taking advantage of certified data sources in Tableau cloud will instill confidence in your router. What about change management? This often overlooked yet highly important aspect of migration asked you to think about what that mid migration experience should look like. As previously mentioned, your new tablet cloud site will processor fresh and distinct URL, accompanied by its own content repository, file store, and identity store. During the migration process, you will inevitably find yourself with two complete and populated Tableau environments. How you manage the content that's been migrated significantly impacts all of your Tableau users. Consider your creators for a moment. If they aren't informed that one of their dashboards now resides in the cloud, They might unknowingly continue refining the version on Tableau server, potentially causing a remigration of that content. On the flip side, envision a team that caught in the midst of a high pressure week. Logging into Tableos server only to discover that their content has been shifted tablet plan. The absence of a well defined change for management process could easily lead to a frustrated user community. At into works, we've developed various strategies to address this complexity, adaptable to your specific needs. These approaches rain range from gradual cutover strategies employing visual cues like banners added to promoted workbooks. To supporting comprehensive environment cut over the plans. For those utilizing embedded analytics, where dashboard views are integrated into another portal like curator. And interx the interx curator is a a non code analytics. Portal for Tableau, Power BI, and Sportsport. The change management process becomes more streamlined. In this scenario, curator or your web portal will guide users to the designated platform for each workbook, whether it's Tableau server or Tableau This setup facilitates a smoother transition and management of the change process. Equally crucial to change management is tending to the data sources that underpin a migration workbook before directing users to the tablet cloud supply to access that workbook. Ensuring that refresh schedules are properly configured to maintain data freshness in these workbooks on Tableau Cloud is paramount. This aspect is pivotal in ensuring that the transition to tablet cloud is as positive for your users as you certain as you certainly wouldn't want the initial experience to be supported by outdated content in their workbooks. Less technical in nature, but just as important is how you communicate to your users about the migration to tablet cloud. Let's think about custom views and subscriptions, which will need to be rebuilt by your end users following the migration. It's possible that some time has passed since your users created subscriptions. Help them move forward with confidence by distributing how to, for custom view and subscription creation, videos can also be an effective way to knowledge share about these tasks such as things. Consider centralizing these resources in an internal knowledge base so that your users know where to go to find what they need. Intworks curator also boasts great flexibility for centralizing resources and hosting tutorials to guide your users through these steps. Enablement is key to getting ahead of any confusion or frustrations for your users. A moment ago, we talked about what it might look like to interrupt interrupt a team's workflow by migrating their content in the middle of the week. Unannounced. It's important to strategize order of content migration with business needs in mind and communicate that strategy to your end users. Think things like, here is how you access this. Here is how your access to this content will look different. Here is where you can find the latest version. On this date, please look for your content in this new location on tablet cloud through hyperlinks provided Finally, it's important to also get users excited about the new functionality that'll gain through migrating. Find channels throughout your organization to begin plugging new features and building excitement around what's possible in Tableau. Encourage your developers to download and begin playing with the latest version of Tableau desktop in an anticipation of a server that will support these cool new features. Not sure where to start with empowering your users to get the most out of Tableoted. Interworks has a strong enablement practice that specializes in making sure that your organization is getting the most out of Tableau, and we'd love to help you think through these things. Tableau Bridge is a big area requiring thoughtful planning if your organization has a dependency on on premise data. That is data on a private network since it won't be accessible by Tableau Cloud. Tableau Bridge is like a client software that runs on a machine inside your network to keep data sources that connect to your private network data fresh on tablet cloud. Without Tableau bridge, Tableau cloud cannot reach your private network or virtual cloud data. Intworks has a built, sorry, Intworks has built an hour long workshop called Tableau Bridge Foundation in which we dive into installation, scheduling, and security among other things in greater detail. For today's purposes, here's a glance at the content we covered there. First, in order for Tableau Bridge to keep your on premise data fresh, those data sources cannot be embedded into your workbooks. To be clear, this has nothing to do with live versus extract data, but rather whether that data source is published to your Tableos server, or if those connections have been built directly within your workbook, AKA, embedded. At the moment, Bridge cannot keep embedded on premise data fresh. As such in migration planning, you'll want to account for the time it takes to publish those embedded connections. Next, you'll need to identify a virtual machine, on which you plan to install and configure tablet bridge. Bridge is only available on Windows. And only one bridge client can be installed on a given virtual machine. The reason we recommend a virtual machine over a developer's local laptop, for example, it is that a server managed by your IT services will be subject to availability and uptime agreements. And it's less prone to being shut down and taken home for the weekend or on holiday to Sicily. When possible, we recommend installing a bridge client on at least two virtual machines so that you can take advantage of pooling. Pauling is possible when you have at least two bridge clients running on a separate virtual machine, and distributed start of freshness task to available clients within the pool. If one of your clients is unavailable for any reason, those freshness tasks will be sent to the other client so that your data stays fresh. Once bridge is installed and any polling configured, we recommend testing the connection to each on premise data connection hosted on your cloud site by refreshing an extract or if a live source, making a change to the underlying data to confirm the updates are reflected tablet cloud. So giving myself a little break now, we'll take another poll. To understand which area of planning feels most pertinent to your organization. Alrighty. We're getting some results coming through. So change management being the big one. No surprise there. I think in terms of the the answers that we've got here, I don't know about you guys, but I would probably couple change management with the communication plan. I think good change management comes, with communication very much built into that. So again, it's no surprise that change management governance, authentication or scripting are all coming out pretty strong. Just as I said, that Tableau bridge starts to gain a little bit of momentum. Yeah. I would say, so it's certainly for me on the sales side of things. Change management, is probably the most important thing when you're making such a shift from, from Tableau server to Tableau Clyde, I would say, you know, the important bit is to get ahead of it, start to plan it well in advance. Think about the things that you need to get done and, and and think a lot of the considerations that we that John has talked to today, and ultimately, change management, if it's done well, will improve the smoothness of the transition and reduce the opportunities for things to go wrong. Thanks, Pam. So planning is a beefy part of any cloud migration. I know we've just covered a lot, and yet time didn't really allow for us to get into everything. On this webinar. We consider migration planning to be just as important as the care with which we treat the migration itself. So much that so that we offer migration services, consisting of building your master plan to support your migration. Should have to anticipate and devise a solution for every blocker on your own. Interworks migration master planning will help you in this effort and allow you to move forward with migration competently. So let's take a few minutes, to discuss logistics around the actual migration itself. We'll delve into content migration with a focus of effort needed to migrating workbooks. While we'll later explore automated migration methods, it's essential to outline the manual process to provide clarity. Additionally, emphasizing the importance of a data source considerations before migration is vital. Initially, We suggest identifying all published data sources crucial for reporting on your tablet server and publishing them to your Tableau cloud site. This ensures that they're readily available as you begin moving the pendant workbooks to the cloud. For each data source within a workbook, a structured approach can be followed. If the data source is published, simply update the data source connection in your workbook by editing the server details to point to tablet cloud. If the data is embedded, your approach varies based on whether it's cloud based, or resides on a private network. Remember that Tableau Bridge is required for private network data sources. The rule is that these data sources must be published. If your workbook utilizes an embedded on premise data source, publish that data source to the cloud first, replace the embedded source within your workbook with the version published to tablet cloud. If you're embedded, the source is cloud hosted, no action is needed. This is why we recommend rearchitecting your data platform to a cloud platform, such as Snowflake. However, we do understand that some businesses need the on premise hosting. We then repeat this process for each source within each workbook. And subsequently publish the workbook to tablet cloud. Ensure that any refresh extracts needed, for the data sources are scheduled. So migration, with that view, can seem daunting, especially in sizeable environments. The content migration tool provides, is a tool, provided by Tableau. Is invaluable in the scenarios where your site project site, project, and content structure remains unchanged as it can migrate workbooks, published data sources, projects, and user group permissions. However, note that manual recreation is necessary for elements such as subscriptions, custom views, data driven alerts, and favorites. So the process we walk through today closely aligns with Interworks careful treatment of migrations. Intworks, Tableau cloud migration services encompass the following components. An online prerequisite questionnaire. We strongly recommend the complimentary, prerequisite evaluation for anyone contemplating a transition to tablet cloud. This assessment furnished furnishes our migration consulting team with essential insights to your current state. As a follow-up, we'll offer a thirty minute advisory session to discuss the evaluation outcomes. Building upon the initial questionnaire, we take our discovery process several steps further. Our team delves deep into your environment examining examining the intricate details of your setup and data architecture. Our goal here is to provide you with a comprehensive roadmap to facilitate a successful transition. Regarding implementation services, when you're prepared to make the move to Tableau cloud. I presume you'd appreciate some assistance along the way. Our implementation services and guide you throughout the deployment process ensuring a seamless and efficient transition. Certain services may already be familiar to you. For example, our analytics practice are in depth sorry, adept at optimizing workbooks, while our data practice specializes in aiding data platform migrations. Additionally, our enablement practice is well equipped to support your content governance needs. This approach minimizes any unnecessary disruption to your workflows, ensuring a smoother migration experience. Managing cloud and support services. Imagine maintaining the continuous smooth operation of your tablet cloud instance with minimal effort. Keepwatch is our support services offering end to end management of Tableau bridge clients, coupled with long term guidance for health of your analytics infrastructure. A dedicated team of engineers through the Keepwatch program ensures the sustained performance and reliability of your setup. Well, that's all from me today. And so I'm gonna hand back to Bill, to to wrap it up for us. Thank you, John. Great presentation, if I may say so. Just a few things just while while we wrap things up. I will give you guys a second just to pop some any questions you have in the Q and A. But just I wanted to run through a couple of things here. So, obviously, in terms of different services that we offer. We we do offer management services for Tableau Bridge. So that is the component that would, sit on us, sit outside of the Tableau Clyde and be pushing your on prem data sources up into Tableau Clyde. And that is something that we offer called keep watch. If you're interested, please reach out to us for more information. Another consideration that you might need to think about when it comes to migrating to cloud is dashboard optimization. Obviously, it gives you a really good opportunity to clean house to think about things that maybe aren't performing as you would like them to. And to think about, okay, maybe you should invest time and effort into optimizing so that when we start using Tableau Clyde, we know that everything's had a bit of a, a clean slate, and we've cleaned things up and they're performing as they should. Along those lines, we've got user center dashboard development, and that's really about putting the user at the center of the analytics that you're producing So we want to give the end user a great experience. We wanna make sure that those things are answering the right questions that the business have, their performant. They're in line with visual best practices, etcetera. So that's another service that might be worth investing in as you move things to this shiny new tableau Clyde. And finally, Tableau Clyde, because it sits outside of your VPC as such, it it opens up the upper opportunity for a lot of organizations to look at things like embedded analytics. That means that, you know, you can purchase content for people outside of your organization, or maybe Maybe it's the salespeople on the road or whatever without having to sign in, to to VPNs or anything. And we specialize and I've done for a number of years in embedded analytics services. And that's where our cur curator product came about from. There are a number of different considerations and things that we can offer help with and support with and we're more than happy to chat to any of you, after this webinar. With that in mind, I'm just looking at the Q and A. It doesn't appear that there's any further questions. You might be off the hook, John. So I would just like to take a moment to say thank you very much to all of you for coming today. You will receive a notification about this cording being available, hopefully, in the next few days. If you do want to learn anything more about it, there are, like I said before, there is a a wealth of information on our blog. Please go ahead and look at that. And there are a number of links that were shared today. We'll keep the keep the webinar open for a minute or two afterwards if you want to grab some of those links from the chat. But it's been a pleasure having you here. We look forward to seeing you at the next one. And once again, thank you John for a great presentation. Thank you everyone.