Alright. So we will go ahead and get started with our webinar. Thank you everyone for being here today. Thanks so much for you all who responded in the chat in terms where you were calling in from. We've got books not only across the US but across the globe. So super exciting. I'd love to do a quick introduction about Interworks. And if this is your first time being on a Interworks webinar with us, welcome. We are an analytics consultancy. We have a global presence with teams in the U. S. Europe and Australia. Lots of people have heard of us through Tableau. So we are a longtime Tableau partner. Tableau is an amazing suite of products. And we love to help customers and people get the most value out of such a powerful suite of tools. But we can also provide much broader expertise in addition to Tableau. So we help customers problem solve and create meaningful strategies along the entirety of the data spectrum. So that includes analytics, data engineering, architecture, embedded analytics, and even training, and enablement. So I highly recommend that you check out the Interworks blog. You can dive a lot deeper around all the technology that we support and you'll find lots of amazing advice and tips from our entire team, or give us a follow on LinkedIn as well if you'd love to stay in touch with all things data and to continue learning with us. We are really excited to talk to you today all about Tableau Cloud. And more specifically the possibility of migrating to Tableau cloud if you're currently using the Tableau server platform. This topic is something that has come up with so many of our customers across the board. Table Cloud as an offering is evolving really rapidly and as lots of organizations are looking to evolve their technology stack, Tableau Cloud could certainly be a great option. So I'm excited as my expert colleagues, Madeline and Colby, will introduce themselves shortly, and they've got a ton of great information on cloud migrations for us today. Feelbook reminders, we are recording this session. So it will be on our website for future access. If you registered, you'll get an email when the recording available. So don't worry, you'll get that in your in your inbox. You'll notice that we do have a Q and A box So if you have any questions along the webinar, go ahead and drop your questions there. We will do our best to just monitor those questions and address them either as they come up during our presentation or hopefully at the very end. So without further ado, hoping if you could advance the next slide. My name is Debbie Yu. I've been with Interworks for just over seven years now. I started my journey here at Interworks teaching at Tableau desktop courses moved on to consulting around Tableau and data strategy is more broadly. And I now manage several of our consult of teams on the West Coast, and very excited to be here with you all today. Madeline on to you. Thanks, Debbie. My name is Madeline. I'm an analytics consultant here at Interworks, and I'm based in Phoenix. I've been here about a year and a half, and I spend much of my time helping my clients think about effective ways to visualize their data in Tableau. And very recently thinking, lots and lots about Tableau cloud migration, so really excited to be here today talking about this with everyone. Colby, you want to introduce yourself? Yeah. Thanks. I'm Colby Owens. I've been with the North Works for Almost ten years now, which is nice. About eight of those have been around Tableau server. Currently, part of our server care team, and keep watch services team. Work with Tableau server on a daily basis, dealing with anything from authentication, infrastructure, infrastructure issues, completely rebuilding sometimes, so definitely in that in that realm. And I will kick us off as well. So, I just wanna say thanks for everybody joining. Very excited for you to be here, get you into the Tableau Cloud migration journey. We have a lot of thought towards migrating to Tampa Cloud, and we have a lot of internal people that are very used to the situation, a lot of experts, we're well informed and prepared for the complexities of the the migration. So, this is the agenda. We'll start off with table Cloud overview. What is it? Why I consider it? Know your limits. We'll talk about a lot of the limitations you'll face. Reduce friction. We'll come next, that's getting proactive about your migration, cleaning up, prior to migrating, and then I'll hand it off to Madelyn for planning for success. These are your strategies. So, strategies for planning your migration, and then we'll get into some logistics surrounding that hands on migration. And then, at the very end, we'll talk about, let's say you've migrated, so post migration strategies. Alright. Before we get started, I would like to take a quick poll just to see have where you are with your Tableicloud right now. Could be that you've already you're already on Tableicloud or just looking to get there, so just wanna kinda see where you stand. It's looking like kind of an interesting spread. I'm seeing about thirty percent still on server, but wanting to migrate forty percent unsure if they're ready to migrate super fair. A whole variety of responses there. Y'all across the board. Cool, that's good. Think you're in the right spot then. Alright. Let's dive in. So, today, as we talk through migrating from Tableau Server to Tableau Cloud, we're going to kind of frame this around a potential scenario that most of you have probably been in, which is moving, so moving from one home to another, So I want you to kind of think about that that move that you might have done, and the head space you were in when you were considering the move. So let's say you either own or rent your home, and life happens, you get a little busy. Right? Tell you get too busy to upkeep it, do those upgrades you're wanting. It just kind of gets out of hand a little bit, so we've all been there. Or maybe you have a lot of landscaping to do and that takes all your time away and you can't get to the upgrades or updates to your home. That's also potential. Or, maybe you have some kind of lifestyle change. Maybe this was suited to your life then, and now you need something maybe a little bit different. And as you go through it, as you go through life, you usually accumulate stuff. Right? We all have some stuff, and maybe you get too much stuff and you have to store it in a garage or an attic or whatnot, so clutter accumulates, and we wanna think about Potentially moving to a new space. So, before we do that, we want to look at Where do you wanna move? What does it have? What kind of features does it have that is attractive. Right? So let's say you're gonna move to maybe a high rise condo. So, let's think about what drew us to this place. It boasts modern floor plans, promises regular updates, community spaces, you don't have to deal with it. They'd handle all the LAN taping, so you don't have to touch it, which is nice. That also gives you some some freedom. There's your newfound freedom. So all that time, you spent maybe working on your house. So the landscaping, you don't have to deal with anymore. It's taken care of for you. And property management. If something goes wrong in the building or water pipe breaks or something, another thing that they will take care of, and you don't have to think about it anymore. So, we talked about TABCloud and the HiRise idea, but what is it? So, TableCloud is, if you don't know, eighty software as a solution analytics platform fully hosted by Tableau, so they handle the infrastructure. So, they promise up to date software with zero downtime upgrades so that your organization always has access to the newest features, and functionality in a space that Tableau is constantly improving. So you don't have to run any back end administration anymore. They take care of all that. It integrates with other cloud based cloud based platforms and offers fast analytics without needing on premise infrastructure. So, now that we kind of went through this scenario and explained kind of what tablet cloud is, We're going to pop up another poll for you, and see what are your primary drivers for migrating to Table Cloud? What's driving him. So we'll take a minute to answer those. Lots of reducing administrative overhead. That sixty percent. You seen that too cool me? Yeah. Mostly, which makes the most sense. Mhmm. New functionality, coming up. Awesome licensing about twenty five percent that's really understandable there. And wanting to explore all your options. Cool. Nice. Alright. Alright, so, thinking back to this scenario. We're gonna continue on with this. So we've got our house. Maybe you own it or rent it, but you've got a whole house, potentially with a garage, and you're looking to go to something more space conscious, right? So, The condo offers many perks, but you need to be thoughtful about this move, so we want to take some time to think of the considerations through the lens of this cloud migration. So, our goal here is to establish complete transparency around things we want you to know, to fully inform you of a migration decision. There are a lot of aspects to take into consideration, so So, one is we've got a floor plan, and now we've got a new floor plan. It's probably smaller, So perhaps the furniture you had doesn't even fit or work in the new space. So you're gonna have to get rid of some things, maybe rearrange some things. So, let's go through step by step. We're kind of categorizing some of these considerations and limitations, so know your limits here. First off, we're going to talk about administrative considerations. I think this is adheres to the majority of the poll answers, administrative considerations. So, version control that is That is something to take into consideration because they will always update whether you like it or not. So, you do get the updates, you do get newest features. So as far as administrators, you don't have to do the upgrade anymore, but you do have to make sure that all of your end users are aware of when this happens and are aware of the new features that are have a rose, and be used to that. So and then we have backups, so backups considered We used to have the ability to take a TS back, which is to back up your TableOS server, and potentially if someone deleads a project or a workbook or a data source, you could restore that TS back and get your content back. But, That is not the case on Tableau Cloud. If something is accidentally deleted, it's gone. So, they do back up the entire infrastructure in case of like a full meltdown, they keep thirty days' worth of backup so they can completely restore everything, but they're not going to completely restore everything for your workbook. Right? So definitely consider that. REPO data, so repository data. That's not accessible. So, if if you had anyone that's connecting directly to your repository and building those custom admin views, that's not really the case anymore. No direct postgres access. So, you still have the administrative views and and insights. I think we'll throw a link in the chat. For some more documentation on those, if you are interested, but no repo access anymore. TSM scripts, TSM isn't really a back end administration thing, so you don't really have access to that. So, any scripts you've written or utilized, that utilize TSM. That's pretty much gone now. The good part is, you don't have to worry about it. They do all the TSM stuff. And then a new URL, so The custom URL you have, you can totally control your domain and whatnot. Now, it's gonna be some a to b s region online dot tableau dot com and then, like, your site name, for instance. So, that's a lot of administrative considerations. The next step up, we'll talk about data source considerations. So, data source considerations, first comes on prem data. This is one of the biggest ones to take into account, so any on prem data? If you've embedded on prem extract, into your workbooks, they have to be published separately, and then reconnected. You have to reconnect those workbooks to you cannot publish a workbook with those embedded on prem data sources, so that's a big limitation for some people. If you want to retain on prem data sources, you have to set up, and this is a little bit of the infrastructure that you'd have to keep. You have to set up Tableau Bridge to allow connections from TableCloud to your on prem data sources, and allow those to be refreshed, so just be aware of that. TAPI Cloud supports live connections to many different cloud based databases. I think we've got a link for they can quickly go to for Tableau Bridge and those connections, those live connections that Tableau clouds able to hit. So data source considerations, I think the on prem data is a big one for for most people. The next step here is authentication, so authentication considerations, there's Samuel SCIM is an option. In fact, Tableau themselves utilize Okta with SCIM on some of their sites on Tableau Cloud. So, That's definitely utilized. MFA. If you don't have MFA now, you will then, because it's required. As of February first to twenty twenty two, MFA is required, so That's a good thing, but just make sure that if you're in the migration stage, all of your end users know and are used to MFA type stuff. I think we all are now, but just so you know. And then connect to DAP. So today, Tableau connected apps are optimized for embedding Tableau views and metrics in external applications. And they're used to authorize access to the Tableau REST API. So, there's two types, there's direct trust, or o auth two point o trust. And I believe we have a link for more information on that as well. CMFA multi factor authentication That's like logging in and then you have to click maybe on your phone. There's a little app. You have to Click to sign in, more than one factor of auth. Alright, and last one is capacity considerations. This can be a huge blocker almost immediately for A lot of people, a lot of our a lot of our clients, this would be an immediate blocker, and that's the file store and the size. Right? So, the file store, on prem, it just takes up disk space, and if you need more, you just add disk space. So, the file store is where all of your extracts and flows and revision histories live, and they can get quite big. So, if you have a five hundred gigs worth of extracts, that's a blocker for for migrating to Tableau Cloud. There is a one hundred Gig limit to your site, so you're gonna have to clean up some stuff if you're gonna fit thing into. It goes back to the house scenario, you can't move your entire garage, full of stuff into a tiny apartment. Right? There is an option of data management add on. If you purchase data management add on, it is another purchase, but It does provide you a terabyte worth of space on your site, so that's good. There's also an individual content, so workbook data source for flow size, there is a fifteen gig limit, so hopefully nobody has built a fifteen gig workbook. There is that limit on on cloud. As far as concurrency for jobs and whatnot, You can get eight background jobs or eight background hours per create a license you purchase. If you purchase, create a license, you can run a backgrounder for eight hours, so there's that kind of to figure that out for whatever you're running. And then you can only have up to about ten jobs running at a time. Another add on is advanced management if you purchase advanced management, you can increase that ten concurrent jobs running up to twenty five. So there are options for kind of increased use. So that's Quick list. Hopefully, you got all that. It's a quick list of kind of the blockers, the limitations that we ran into, or most most of the blockers for most of the clients that we ran into, so we'll pop up another poll to see kind of which ones which one of those categories fits you. So let's take a minute to answer that one. Alright. I see neck and neck for a capacity and data source. Rightness. Some administration, limitations, some off. So, a bit of both. Hopefully, some of those some of those limitations or at least knowledge of the existence of those we'll help your help you plan plan ahead. And we can help if you need to, so We're used to all these. We're happy to help, reach out to us, and we can walk through kind of the limitations that that you have and see if there's any way we can make it work. I believe we have a link as well. We have blog article that kind of goes pretty in-depth about all these limitations as well, so hopefully that'll be Hopefully, that'll be helpful. Alright, so, that is know your limits. Those are the limitations. Let's talk about reducing friction. Let's talk about kind of removing the unneeded content. Right? So, as far as the house metaphor goes, We have a house, we're moving into a tiny apartment or a condo, we can't bring everything with us. Most of the time people have a garage sale. Right? So, Alright. So, let's talk about cleaning up our environment. So, first thing we should look at are Sketch So, a lot of times, schedules can get kind of out of hand. It's very easy. Hey, I want something to run here. At this time, and you make a schedule for it, so they are server wide, they span all sites in your existing environment, and they can sometimes exponentially multiply. It seems so it's a good time to assess what's actually utilized and needed and where we can reduce or consolidate these tasks. This brings up a good point as well. Schedules are span all of your sites, multiple sites. That's another limitation. I should I should state, but, when you migrate to Tableau cloud, you only get one site. Right? So, if you have a bunch, if you have a hundred sites on your existing Tableos server, we need to try and consolidate those into one site if if possible. So, schedules, see if we can see if we can combine those, shrink them down. The next up we have workbooks, so workbooks can easily get out of hand, I think we all know that. Especially with kind of a sandbox environment, sandbox projects, you end up having test workbook A, test workbook B, and then filling out all of the revision history for each one, so that can get kind of out out of hand. So what we need to do is really go through and and remove anything that's needed, figure out all the stale content, The more you can get get all of the stale content and unused data off the server. Now, the better the migration is gonna be, the easier the migration is gonna be. I do like this part of The migration because even if you don't migrate, doing all of this is going to drastically improve your Tableiserv environment as it stands. So, do it anyway, whether you're migrating or not. And then data sources. So as you can imagine, Tableau Cloud loves cloud based data sources. So and they can natively connect to any. I think we've we've got a link for that. What data sources are natively connected to. We talked about this before, if you have any on prem data sources, you need to retain and you can't move them to a cloud based data source, then you'll have to implement that Tableau bridge. It may be a blessing in disguise, though, so you can find you reduce your overall footprint and utilize that single published data source, instead of embedding everything in your workbooks, you can publish it separately and have that single source of truth, at one published data source, and you can reconnect all your workbooks to that one. So, now that we've overcome any potential limitations, let's say we fixed all that and did much needed house cleaning. I'm going to hand it over to Madeline now to set you up for success. Great. Thanks, Tony. Awesome. That was a lot of great information on those considerations for your migration and love that section about reducing friction so that you're really setting yourself up for this move this migration experience possible. So with that, let's talk about what it looks like to plan for success. If we think back to our analogy of moving homes, there would be no circumstance in which tonight you decide you want to move. And tomorrow morning you wake up in search of the nearest u haul to load your stuff up, with an expectation that you get to your new home and be fully unpacked by tomorrow night. There's just a lot to plan for. And in the same way, inner works recommends a very thorough approach to planning your cloud migration. So let's walk through four areas that we suggest you dedicate some time to planning. First, we'll get into governance. So as Colby mentioned, etipical cloud deployment generally consists of a single site. So if you think about your Tableau server right now and how you're distinguishing your sandbox from your production content, If you're doing that by way of separate sites or possibly even separate servers at the moment, you're going to want to spend some time thinking about how you change that structure to support a single cloud site. Now again, there are options with a data management add on where you could explore other sites, but as we think about again that typical cloud deployment, what are some strategies for organizing our content? In a single site. So Debbie actually has some fantastic ideas surrounding project governance, and I think we're gonna send a link to a webinar that she hosted in the chat. But one of our favorite approaches to organizing your content is to build projects based on business units. So, within your site, you've got multiple projects, think finance, marketing, sales, for example. And within those projects, there exists sub projects for sandbox, QA, and production content. And then you apply permissions to those projects respectively. So you'll want to be thinking about project structure as well as the responsibilities of those project owners and how content promotion looks like as you're progressing a work book from sandbox to a production state, for example. Now, depending on what version of tapas server you're migrating from, you might be excited to explore collections, which are a newer feature to Tableau server and a feature that you will come into by virtue of migrating to upload cloud. Collections allow you to organize your items in an easy to access list according to what's meaningful for your job function. Irrelevant of any projects that that content sits in, you can create a collection to pull in workbooks as it makes sense for your needs. So, you'll definitely wanna check this out if it is new to you. And again, just encourage building excitement around the new features that you'll have available to you in cloud as much as possible to get your users excited too. And then if you're not already take advantage of certified data sources in Tableau server, these are also available to you in Tableau cloud. They fall right in line with your governance strategy and especially in an effort to help your users in building trust around the content that you migrated to Tableau cloud, we recommend utilizing that certified data source feature to instill that confidence. Let's talk about change management now. This is another significant area that warrants some planning. And it's frankly easily overlooked, but really important because it asks us to think about what that mid migration experience looks like for our users. So if you, you know, as we think about the considerations and some of the complex the reality of a typical Tableau server to cloud migration is not that you'll start the day in Tableau server and end in Tableau cloud. How we treat the content that we migrate in between the start and the end of the migration will have an impact on your users. If we think about your dashboard creators for a minute, if they're not made aware that content that they own in Tableau server now exists also in Tableau cloud, I could see a scenario where they are editing the version in Tableos server, they're iterating on that, and now you've introduced this need to migrate the same workbook all over again to get that latest version over to the cloud site. On the other side of things, if we're thinking about your viewers or your explorers, Maybe they're in the middle of a high pressure week, they have a dependency on content as they're used to it in Tableau server, and if you migrate content and they're greeted by a difference to their normal routine, that could create some frustrations. And as much as possible, we want to avoid any undo complexities in the life of your users over the course of migration. So, what might be the best way to instill some change management around a migrated workbook. Let's think about a scenario where we want to discourage the use of a workbook on Tableau server and instead point our users to its cloud equivalent. The one that we're keeping fresh, the one that sits in this new environment with added functionality. So there are two approaches that we could take to a scenario like this. First, you could modify the version of that workbook as it sits in Tableau server literally editing it to display a text box with a description that says, this content has been moved. It can be found in its new location on Tableau cloud through this hyperlink. This is great in that it leaves no ambiguity around what version should be used and it definitely catches the attention of your users when they attempt to use the version in Tableau server, but it does require modifying each dashboard in Tableau server, and it adds a manual and then a manual layer to the migration process. Now, inner works preferred method is to use curator for seamless redirect to the cloud site. So when a user attempts to access content that's been migrated unbundnownst to them whether it lives in server or cloud, that experience looks the same. If you're unfamiliar, curator is Interwork solution for a fully customizable analytics portal. It's a great way to centralize your reporting. And as we think about its use in terms of a migration, your users could navigate to a dashboard through curator And with no mind for where it lives, whether on server or cloud, we can channel the URL that we want to call when they access that dashboard to deliver to them the newest version as it sits in Tableau cloud. We love this option because it allows you to migrate content gradually and really dual run Tableau Server in Tableau cloud while you're helping your users make that transition. And then lastly for change management, it's just as important to think about the data sources that support the workbooks you're migrating as you're moving them to the cloud environment. Again, we don't want your users' experience to be visiting the cloud site, saying great my content is here, but it looks like this is outdated. So, definitely making sure that you're tending to data sources that support the workbooks you're migrating so that things are staying fresh, your workbooks are up to date, and we're just enhancing that user experience from the very beginning as you complete your cloud migration. Let's talk about a communication plan now. So, this is less technical, but just as important. And it is really about delivering expectations to your users before during and after the migration. As Colby called out, There are some considerations around subscriptions or custom views as these will need to be rebuilt in your Tableau cloud site after the content has been migrated. So we want to make sure that you're enabling your users with information to recall how they build this subscription or a custom view. Maybe it's been some time since they've done this. I find myself subscribing to things, and then not thinking about subscriptions until I need to create a new one, and sometimes I even stumbled to find what icon is it at the top of the navigation bar. So you wanna help your users move forward with confidence by distributing how tos for them. We've seen these delivered effectively through videos, centralized knowledge bases where you can share just short instructions about how to do things like create subscriptions or rebuild custom views, If you are using curator to help with your migration, curator has this great option of including a tutorial as you send your users content that sits in tablet cloud, you can actually have a little drop down that guides them through the process of rebuilding the subscription or the custom view on that content. And then thinking about just the migration timeline in general and how we tee up expectations around where content's going to live? What is the larger plan? You'll want to be sure that you are approaching your users with messaging like here's what's changed about how you access your content, here's where you can find the latest version, or if it's not been migrated yet, On this date, please look for your content in its new location in tablet cloud through the hyperlink provided here. Something of that so that you're being as transparent as possible with your users. And then the fun part is getting your users excited about the new functionality that they'll have available to them in Tableau cloud. For your developers, we recommend encouraging them to download the latest version of Tableau desktop start exploring and getting a hold on all of that new feature functionality that is for many of you based on that poll, a large part of the reason you're migrating to cloud. And if you're not sure where to start with empowering your users to get the most out of Tableau, Interworks enablement practice specializes in making sure your organization is getting the most out of Tableau and we have some great workshops, webinars, and things to support you how you work to educate your users. Lastly, we'll talk about Tableau Bridge. I've noticed some commentary on Tableau Bridge in the chat, this is specific to organizations that have on prem data. So think about Microsoft SQL Server or file based data, for example, If all of your data is hosted on Snowflake, entirely, Tableaubridge will not be required for your org, but it is needed for cases in which you connect on prem data. So as some background, if you are unfamiliar with Tableau Bridge, it's a client software that runs on a machine inside your network and it works to allow Tableau cloud to connect with your on prem data and keep it fresh. Just to reiterate in the absence of Tableau bridge tablet cloud cannot keep that on prem data fresh, so it's important that if you meet this criteria, you take some time to think about planning for your bridge deployment. I'll mention here that Interworks has an hour long Tableau Bridge foundation workshop where we really deeply go into these aspects of planning for Tableau Bridge, But since we don't have all that time today, there are a few areas that I'll call out specifically. So I think we've spent a bit of time on this already, but just to reiterate for Bridge to keep those on prem data sources fresh, they'll need to be published out to your cloud site. Any connections that you have embedded in your workbook that connect to on prem data, you're going to want to care for by publishing them out to the cloud site as hosted sources separate from the workbook space support because only then will bridge be able to keep them fresh. Again, this is specific to on prem data with a snowflake hosted source for example, No concerns with embedding that connection in your workbook, but for tablet bridge to do what it does best, you need to have that on prem data published out. Then we'll want to think about a virtual machine on which you'll install your bridge client. This will have to be a Windows operating system and keep in mind that each virtual machine can support one bridge client. We refer to virtual machine because this is a better then what's sometimes tempting, which is to install a bridge client on your personal laptop or a developer's laptop, we don't want bridge competing with with resources from other applications. And so in an ideal setting, you would install that bridge client on a virtual machine that's dedicated to that purpose. When possible, we also advise installing and configuring at least two bridge clients. The reason for this is because with two clients, they're able to take advantage of pooling. And pooling distributes those data freshness tasks to clients available within the pool. So, if for some reason one of your virtual machines goes down or a client on that machine becomes unavailable, pooling will allocate that data freshness task to the other client in the pool, and it just gives your data the best chance at seeing fresh, seeing updated for the best experience for your users. And then, of course, we want to allot for the time it'll take to test your connections once you've got those published over to your cloud site if you do have a Tableau bridge dependency, we wanna make sure that we're proving out that Tableau bridge can keep that data fresh, that you've worked out any of those configurations that might need to be tweaked to support this. So, Tableaubridge is a good chunk of planning if it does meet organizations criteria of having on prem data sources, but we do have a lot of resources available. We have six part blog series, I think we have the first in that series that we'll share with the chat. And if you're looking at this and thinking about how tableau Bridge will apply to your deployment of Tableau Cloud or you want some other info, this bridge series that is on our blog covers the whole gamut of things from installation, configuration, security, scheduling, so that is a great resource that should be available to you in the chat. I think it's time for another poll. So let's just pause for a minute because we have thought a lot about considerations, planning, different strategies. Let's take a minute to think about which area of planning feels most pertinent to your organization. Maybe you don't have a use case for Tableau bridge and one of the other areas we talked about feels more prominent to you. Seeing a lot of change management, governance authentication, scripting, yep, And fair amount of Tableau Bridge. You're not alone in your use of Tableau Bridge, more often than not, my clients do have on prem data, and so bridges, something that typically does enter the conversation as we're helping our clients think about in migration to Tableau cloud, and it is a good option for keeping your on prem data fresh. Okay. It's actually an exact tie between tablet bridge and governance authentication and scripting and those are two areas among a handful of others that Interimberts has some really great resources for you, so we'll be sure to follow-up with those links and things in the chat and would be happy to talk with you through any further details in those areas. Okay. Next up, let's talk about the migration itself. In fact, before I do that, I wanna just speak to one other topic regarding the planning. Interworks is aware that there's a lot to be considered. There's a lot of boxes to check and things to trying to anticipate, and it can be a lot to do on your own. So, as part of our migration support services, we offer a master plan, which helps you anticipate and solution for blockers and any of these considerations that are making you feel like there could be some added complexity in your migration to cloud. We know it's a big undertaking. And so, the migration master plan will help you in that effort, and allow you to move forward confidently with your migration. So, good segue into what the actual migration looks like. We spent so much time talking about how we how to get here. I don't wanna shy away from some of the logistics about the hands on migration, because I know It's fair that you'd wanna know what was actually involved to get my content from point a to point b. So let's talk content migration. At this point, we're assuming we've already accounted for those prereqs, the considerations that Colby brought up. We're gonna just quickly run through what could be a manual process to migration, and then I'll call out areas where a content migration tool can be a huge help for us. So let's look at step one here, publish all published data sources from Tableau server to Tableau cloud. This is a great first step because it gets those data sources hosted in your cloud site and ready for you as you move those dependent workbooks to the cloud site. Then for each data source in each workbook, we have a structured process or decision path that can be followed. So if that data source is published, you'll just update the connection within your workbook to point to the version of that published source that you just moved over to the cloud site. No worries there. If the data is embedded, this is where that consideration for what data type we're connecting to comes into play. If it's an on prem data source, want to publish it out to cloud as a hosted data source like we've spent a bit of time talking about already, so that it can be supported by Bridge. And if it's a cloud hosted embedded data source like Snowflake, for example, Tableau cloud won't have any issue keeping that embedded connection fresh inside your workbook. You'll repeat this process for each source in your workbook and then publish that workbook out to Tableau cloud, scheduling any necessary extract refreshes to support that content. I know this can feel overwhelming as we think about it in terms of migrating larger environments, but the content migration tool can be used to help migrate workflows. Published data sources, permissions and projects in scenarios where your site project and content structure is not changing. So, content migration tool typically comes with the advanced management license. However, a prerelease version is available to you for your server to cloud migrations, and you can use that within a ninety day window to help with this process. It's a big help particularly for environments whose data sources are in Snowflake or on another cloud hosted platform. But I do wanna call out here that content migration tool does not migrate subscriptions, users, custom views, or favorites among a couple of other things. So that's where we'd be happy to help you with that process. Alright. So, That was our quick hands on migration recap. Now we're impounding you've made it to tablet and cloud nine, but you didn't have to go through that process alone. I want to reiterate that Interworks has put a lot of thought into how we approach these migrations, and our approach closely aligns with what we talked about today. Our efforts towards planning are just as mindful as how we actually wanna treat the hands on migration So, if you feel like you benefit from some support during your migration, let's just talk about Interworks approach in a bit more detail here. First up, we have a pre req. This is a simple set of questions that asks about your environment and just helps to inform a really easy thirty minute advisory discussion that we like to have with our clients. Basically here, we're thinking back to Colby's know your limit and we're working to identify any immediate blockers or considerations in helping you pursue your migration to crowd. That know your limits and all those considerations is a foundation to this pre req and we have that form linked in the lower left corner of this slide if you're interested in filling out that questionnaire right now, if you're not, no worries at all, we're so happy to talk with you about next steps and just have a chat before you get into the pre req. After the pre req, we move into the migration master plan. This deeply explores your environment and allows us to discover more about the architecture of your data ultimately resulting in a detailed plan of action to support your migration efforts. This is we can tie this back into the reducing frick the knowing your limits. This is the culmination of all that we can discover about the migration itself to make sure that the process of actually migrating goes as smooth as possible. And then for implementation and actually doing that hands on migration, Once those migration complexities are informed and addressed through the process of building that master plan, we're ready to help you with your hands on migration. Our implementation services take you through deployment and ensure that things go as smoothly as possible along the way. And when you work with Interworks, you have a team backing you. So, we've got so many knowledgeable, talented individuals who want this to be a huge success for you. So, we love to work with our clients in that way. And then finally, once you've migrated and your on tablet cloud are qualified keep watch team is available and dedicated to supporting your day to day at Tableau cloud operations, things like optimizing Tableau bridge, managing those clients so that you can truly be hands free when you've finished your migration to Tableau cloud, and you're not having to bother with any of that administrative overhead, which for many of you was the heart of why you're thinking about a migration. So, Keepwatch offers a great solution here. With all of that being said, I'm gonna go ahead and pass it back to Debbie. She'll share with you a couple other ways Interverse can support your analytics needs and closes out for the day. Thanks, Madeline, and thanks Colby. For all of that information, There's a ton of information that we presented today in this webinar. There are a lot of other ways that we can support you. So for example, if you are concerned about number of on prem data sources or many of you in the poll who expressed you know, questions or or, you know, wanted to know more about Tablebridge. We do have managed services to help you support those on prem data sources. Colby also mentioned that, you know, this migration may also offer an opportunity to really identify your content and really have that quote unquote garage sale. Part of that process may also be identifying workbooks that get a ton of usage and you absolutely need to keep, but may not have the greatest performance, so we can work with you to optimize that content. And offer training on your to your dashboard creators to help them create more performance and efficient workbooks moving forwards. And finally, the demand for data and native applications really continues to grow. So we are also seeing a lot of conversation with our customers about how to leverage embedded analytics. So if this is something that your organization is considering or, you know, maybe would like to open up self-service data to external consumers or applications that you may be offering to your own customers. It's a really important conversation to have around Tableau cloud as well. With that being said, we still have few extra minutes. I know there's been a lot of chatter going on in the chats and and also in the q and a. I want to take a minute here to pause quickly to cover any a couple open questions that we may have. One quick answer, I will say there was a question in the chat around gover government cloud in Tableau. So to Joel that there's no current specific government cloud offering. I know that there's been some conversation in Tableau about FedRAMP certification. So not currently. So just as a point of comparison, it doesn't exist today, but there may be a cloud offering in the future. Any other questions that anyone has in the cat? Then we do see a question about any other known roadmap from Tableau to have something other than Tableau bridge as far as refreshing your on prem data ghost Tableau bridge is the option at this point. Just scanning to see if there's anything else in that chat. Same as well. I think there was a comment of whether or not cloud may include EDU. Again, that that question may be great to pass to your Tableau rep to just ask anything also on the road map for educational institutions. You're not sure if the you know, if there are different considerations for government versus education. So it could be a great question to pass your rep about of the future road map. Then final question, I see a question here. Around, is there a sticker shock for licensing changes? I would say, you know, it really hugely depends on that environment, you know, the the migration process may open up, uncover some interesting discoveries about how those costs could change. For some consumers that could go up, but but for some consumers, it may certainly go down. Again, the migration process is an opportunity to really identify or take stock of all that usage and everything that you have, and that may be an opportunity again to kind of essentially right size your licensing, where it may not necessarily increase. But, again, I think that would depend on a case by case basis. Alright. Last question, there is a question there. On any additional tips on security, Colby, any comments that you might have there, there's a question around active directory where cloud doesn't support that currently. Yeah, it doesn't support kerberos. I'd say I'd say your best option is utilize an IDP if if your environment's not already set up for that. It's great way to integrate all of your business applications anyway, and Tableicloud can easily integrate in with the rest of those So, like I said, Tableau themselves utilize Okta and OktaScan for some of their sites, so Yeah. I would say that's that's a good next step if you if you can't use kerberos. Thanks, Colby. Yep. Awesome. Well, thank you so much everyone for attending our webinar today. We will be sharing a short survey following this webinar, so we greatly appreciate your response to that. Reach out to us if you'd love to chat a little bit more about a migration for you. There is a QR code here. That will help us just gather some information about your environment to just prepare us for that conversation. But if not, please do not hesitate to reach out to us to just chat further. We'd love to hear from you once again, the recording will be posted on our website, and you will get an email to get notified that the porting is live, and you'll get all those helpful links that we've been sending in the chat as well. So once again, thank you guys so for attending our webinar today, and we hope to hear from you soon.