Thank you guys all for being here today. I'd love to give you just quick, introduction about InterWorks before we get started. If this is your first time being with us on an InterWorks webinar, welcome, We are an analytics, consultancy, and we've got a global presence in, the US, Europe, and Australia. Many folks have heard of us through Tableau, as we're a long time Tableau partner. Tableau has amazing analytics products, and we love helping them get the most get our co clients and, folks, the most out of such a powerful tool. We can also provide broader expertise in addition to Tableau, we help customers solve and create strategies along the entire data spectrum so that includes everything from analytics to data prep data engineering, architecture, embedded analytics, training and enablement. So I highly recommend you visit the inter blog after this or at some point in the future where you can dive deeper around all the technology that we support and get lots of amazing advice and tips and tricks from our entire team. Be sure to also give us a follow on LinkedIn as well if you'd like to stay in touch with all things data and continue learning with us and learning about future webinars. We're excited today to talk to you about Tableau Cloud. And more specifically the possibility of migrating to Tableau Cloud if you are currently using the Tableau server platform. This topic is something that has come up with so many of our customers across the board. Tableau Cloud as an offering is evolving rapidly, and as organizations are looking to evolve their technology stack, Tableau Cloud could certainly be an option. My expert colleagues, Madeline and Colby, who've joined will introduce themselves shortly, and they've got a ton of great information on cloud migrations. And as Vicki mentioned, be sure to take note of the Q and A function. In Zoom today to drop any questions that you have, and, we'll be monitoring them to do our best to address them during the presentation or maybe at the very end. So without further ado, we go to the next slide, and I can introduce myself. I am Sarah Dorffman. I am an analytics architect I've been working with InterWorks for, five and a half years, and I'm, based in Los Angeles. I started my journey teaching Tableau top courses, and then moved on to consulting around Tableau and data. And now my current role, I specialize in advice clients and things like Tableau governance, cloud migrations. So yeah, Madeline on to you. Great. Thanks, Sarah. Good to be here with everyone today. I'm Madeline Cook, I'm an analytic consultant with Interix, and I'm based in Phoenix, Arizona. In my day to day, I don't my clients make the best out of their Tableau products through dashboard design and development and lately have been working lots with Colby and Sarah along with the rest of the migration team here at InterWorks to think about how we can support our clients with the most seamless migration experience. So really excited to be sharing these ideas with you all today, and I'll hand it over to Golby. Thanks, Madeline. I'm Colby Owens. I've been with InterWorks for about ten years, Tableau server realm, about eight of those. I'm with our Keepwatch services team, and I am going to get us started off here. So first, we're gonna go over kinda what we're gonna talk about today, today's agenda. We have the Tableau Cloud overview, so what is Tableau Cloud, why should you consider it? And then we'll go on to know your limits. So that's kind of all the limitations, maybe blockers, you might, come across. So we're gonna go through a lot of those. That's gonna be a lot of, my content. Reduced friction. That's one of my favorite parts of this because this is something you can do now. On your Tableau server just to clean it up pretty much. It's just kind of house cleaning. It's also a great way to prepare for the migration. Then I'll hand it over to Madeline for Planning For Success. That's kind of strategies as you plan for your migration. Ready Set migrate, we'll talk about act actually migrating and kind of expectations for that. And then cloud at last is when you're already on the cloud, what can you expect, and considerations after the migration? So the overview actually will take a poll first. We kinda wanna get an assessment of where you are right now in your journey to, the Tableau Cloud. So maybe you're already on it, maybe you're looking at it, maybe you don't even have Tableau server yet, but we'll see where you are. So just take a minute to answer that poll. It should pop up. And then we'll keep going. Oh, looks like that's probably all the responses we'll see here, Colby. Are you seeing the poll results on your side? Yeah. I see most people are in the right place. I'm sure if we're ready to migrate to Tableau Cloud kind of one loophole. So Yep. That's perfect. Cool. Not still on tablet server, but wanting to migrate. So really good good place to be. Nice. Alright. So, we're gonna kinda talk about this migration in a scenario. Our scenario is kind of moving house. So moving from one location to another, say you have a home or you own it or you rent it, but you have a whole house with all your stuff in it. And potentially some pressures might be on you. Like, you're getting too busy to to just upkeep it. You've got a lot of yard work to do, which you have to maintain. You're starting to accumulate clutter, so it's getting full in there. Or maybe you have some lifestyle, lifestyle changes that are affecting you that this kinda doesn't work for you anymore. So just say you have your home and you're just thinking about moving, and maybe to an apartment or to a condo, so maybe small or area plan, but it looks promising because there's, modern floor plans. There's regular landscaping that's kinda done by the property management team, so they take care of all the landscaping for you. They take care of the maintenance, so you kind of have a lot of new freedom. So some benefits there, maybe for your lifestyle change. So it's kinda how we're gonna frame this migration. So what is Tableau cloud? If you don't know? Tableau cloud is fully hosted by Tableau. So they host the software as a service analytics platform. So you don't have to manage or maintain that, that back end infrastructure. So there are some benefits to this. So you can see at the bottom here, there's access to the most up to date features. And zero downtime upgrades. That's pretty promising. So zero down downtime upgrades, that's pretty nice. They do upgrade whether you like it or not. So just know that it comes with some caveats, but you do get access to the most update features. They do performance tuning and scaling to accommodate the workload, so as you add more and more, pressure on your, Tap Cloud site, they can handle that. They deal with that in the back end. You don't have to think about it. And then integration with other cloud based platforms and quite a bit more. So I know it's a quick poll again, but, that's kind of how we're gonna frame the move from Tableau Server to Tableau Cloud. So what we wanna know is What, what's driving you to want this change or thinking about this change? So we're gonna have another poll real quick. Just to kinda get a overall assessment of where you, where your mind set is. Administrative overhead. That's that's the big one. Yeah. Straight overhead. I see new functionality, frequent updates. Don't have to worry about that. Right. Cost and licensing. Cool. Okay. Now thanks for filling that in. Alright. Well, that's awesome because the first thing we're gonna talk about is, administrative considerations. So right after this, but this is the part of know your limits. So administrative overhead is part of kind of the limitations as well, which I'm gonna talk about. Here's know your limits. We have an entire house that's full of your stuff, and you're moving to a smaller floor plan. Right? So you can't really fit everything in your house into an apartment. So you're gonna have to think about that limitation among other things, and plan for that. Right? So that's kind of this whole, why we're having this webinar. Right? Let's get an assessment, figure out the limitations and blockers, and plan for it. So here's our first one, administrative considerations. So we're gonna talk about the, backups and version control. So version control, I kind of already mentioned this. They are going to upgrade to the latest version, which is nice. You don't have to worry about it. You'll have access to the newest features. But you don't have a choice in the matter. If you're not ready, that's too bad. So, I would just say Make sure that, if you're on the cloud, make sure all of your desktop users, your content creators, are on the latest version of desktop as well, just so you don't run into the version issues. And then backup considerations. So in TableOS Server, we take backups, and then we can restore those. Right? If we lose something or something crashes or Someone deletes a project by accident, we can restore that, or we can restore the backup to some test server, grab the content and then republish it. So we had some options there. That's kind of gone in Table Cloud. So they they do take, a backup of the entire environment, and they keep it for thirty days. But they are not going to restore the entire environment with everybody's sites because you deleted your workbook. So you gotta think about that. So not a great, not great options for backup, so just don't accidentally delete stuff. Next, we have the repository data. So in Tableau server, what they call the repository is a Postgres database. That's where most of your stuff is stored. So a lot of your metadata, users group permissions, that kind of information is stored in a Postgres database. They call it the tablet repository. Some of you may have already enabled access, and connected to it, and built dashboards based on that repository data. That is gone in Tableau Cloud. You do not have access to the repository. Instead what they've done is they've curated, certain data sources based on the repository just for your site, and then they built dashboards that tell you about, your site's usage, and they call that admin insights. So the good news is you have some, some views into that, some data on your site, and you can connect to that and create dashboards if you wanted to. So that's called admin insights. And I believe we have, some links as well. We can throw some links to that in the chat, for more information. So that's another administrative consideration. If you did have repository stuff built, that's kind of gonna go away. We have t s m scripting. So t s m, pretty much you don't have to think about t s m anymore. If you're not sure what that is, then you're okay. But, TSM is just management of the back end, so taking a backup, restoring stopping, starting the server, taking zip logs, that kind of stuff. So, if you ever had any scripts built utilizing that, They're kind of moot now. So, and then last one for administrative considerations is the URL changes. That's going to be a specific, you're just a site on Tableau's Tableau server. Right? So You only have that site, so your URL is gonna be something like, AWS region, the online dot tab blue dot com, and then your site name, something like that. So, there's no built in way to get some custom URL there. So that's gonna be most of your administrative considerations for the change. Next we'll have data source consideration, so on prem data. So this is something I would say would probably cause the most impact to you during the migration or the most benefit if you actually spent some time to to change or move things. So it's your on prem data. Tableau Cloud does not natively connect to your on prem, on prem data. So they have Tableau Bridge, something called Tableau Bridge that acts as a proxy. You do have to install it. Usually, people install it on a virtual machine or something like that, but you install Tableo Bridge, and that has to be able to connect to your on prem data sources. And Tableau Cloud proxies through it to refresh those extracts. So any on prem data requires Tableau Bridge. That's what that means. I would say in preparation to if you can, get your data, live on the cloud, some cloud based data database. That would be the most beneficial. Next we have live connections. So Tableau Cloud has a certain number of, most of the large cloud based data sources you can connect to That's you're usually okay, but you should go through and make sure that if you're using any cloud based data sources, live connections to those, Just make sure Tableau Cloud can connect to them before you migrate. That would not be a good thing to find out afterwards. And then, some supported source types. So this, this just means Table Cloud does not support some published connections. So, for example, anything that's that's utilizing kerberos authentication, it can't connect to that. So if you're utilizing that, just know the limitations of Tableau cloud, go through what you have, and we'll have to change some of that stuff. Next, we have authentication. So group sync. If you have active directory set up on your Tableau server and you're kind of syncing AD groups, that kind of goes away. TableCloud doesn't really have a native way to connect directly to your active directory. You'll have to go through, like, SAML and ADFS. For authentication, if you wanna utilize if you still want to utilize your active directory. But it does support SAML's skin. So And I know this, because I know that Tableau themselves have some sites on Tableau Cloud, and they're utilizing Okta with SCIM, so I know it's, it does work. And then multi factor authentication. So MFA That is now as of February first, I think, of last year. MFA became a requirement. So If any of your end users are not used MFA, I think we all are now, but, just know that that is a requirement. So when you go to Table Cloud, MFA will need to be set up. And then trusted tickets and connected apps. So today Tableos Connected apps, they are optimized for embedding, those views, and metrics in external applications. So you there's two types of connected apps. You can configure. One is Direct Trust, and the other one is OOS two point o trust. You have a couple of different authentic, authentication. Long story short, that's just embedding something somewhere. Like a visualization, and giving your end users kind of an SSO or single sign on field to view that. And then capacity considerations. This might be one of the largest limitations for a lot of our clients, and that is A Tableau Cloud site has a hundred gigabit, gigabyte, sorry, limitation, on the site by default. If you have more information than a hundred gigabytes, that need to be migrated Tableau Cloud. You do have the option to purchase, which is another purchase. Data management add on license. And that gives you one terabyte. So you can increase, increase that to one terabyte, and then you shouldn't have space problems anymore. And then concur sorry. Concurrency. So this is also has to do with capacity considerations. Concurrency is eight backgrounder hours. Or create a license you purchase. So say you have one creator, you purchased one creator, that means you have eight hours that are put into a pool of hours for the backgrounders to run jobs. Right? So, like extract refreshes. So one creator, you can run extract refreshes for eight hours in a twenty four hour block, and then it resets. And it resets every midnight at UTC. So concurrency If you purchase ten creator licenses, that means you have eighty hours of pool hours, and so the backgrounders will just run eighty hours total time to run through all your jobs. That's kinda how that works. There's a few other ones, like, concurrency for your actual jobs. So how many can you run at a certain time? That's, ten jobs. So you can only have ten jobs running at a certain time. If you purchase advanced management, that can go up. So there are options to increase your these limitations. For purchasing advanced management or data management add on. All of your jobs have a maximum of two hours as well. So any of your long running jobs, so if you have an extract refresh that runs four hours for it to complete. It's not gonna be, it's not gonna be a thing on Tableau Cloud. You'll have to figure out some way to fix that. Oh, sorry about that. One other thing that I've that I've heard that some sometimes people are surprised from are flows are treated a little differently. So flows are not included in this, this background or hours. Flows are completely separate. And they'd be they utilize resource blocks. So with Tableau Cloud and your site, you get one resource block. That means you can run one flow at a time. You can run all day, but only one at a time. If you need to increase concurrency for running your flows, you purchase this other resource block. And then you can run two at a time all day. So that's how resource blocks work. That's just for flows. And I believe we threw some comments or, some links in the chat too to to help support this. Alright. So that's a lot of information. I kind of open the flood gates on you, but that's a lot of considerations. The holistic view here is You can't just migrate without thinking. There's a lot of stuff that goes into this. A lot of considerations and limits. So after going through this, I'm actually gonna throw up another poll, to see what of these limitations or blockers do you think would impact you? So let's take a minute to to answer that poll and then We'll keep going. I'll put this slide back up too so you can kind of see where things lie. Makes I didn't see what the answers are here. I think it's gonna sort of guide our efforts too within InterWorks to figure out where should we be spending time thinking about how to make this process easier for for our clients. And it looks like there's truly a very even spread, across those primary four options. Very even. Yeah. Capacity. Capacity is up there. Data source readiness. Yeah. And that's mostly what we I think we've ran into for those client migrations. Yeah. Nice. Alright. Well, good news. We can help. So we, We've done migrations before. We do assessments. So, hit us up and we can do we can definitely help you out. So now that we've talked about limitations, blockers, and say we're Okay. We're thinking about moving now. We're gonna migrate to the cloud. What can I do to prepare? So this is kind of the reduced friction. How do we reduce friction? If we go back to the moving house scenario, most of the time people have a garage sale. Let's get all of the clutter or things we don't need anymore. Only keep what's necessary, and let's get rid of let's get rid of stuff so we don't have to move it into the the smaller floor plan. Right? So that's kind of this, this scenario. So what we're gonna talk about is your current Tableoserve environment, and things we can look at to make this transition smoother, easier, cheaper, probably as well. So schedules, schedules can get out of hand. A lot of times people will, demand, hey, can I run this at just this time on these three days of the week? And you're like, well, I don't have a schedule for that. I'll create a new one, and you do that about four hundred times. So this would be a great way to clean up, go through the schedules, identify what's not even used anymore, or what you can consolidate and get rid of the, the other ones. So, schedules, that's a good way. Those are server wide, so they impact all of your sites. And then workbooks, so workbooks, again, those can easily get out of hand. Especially if you have, like, a sandbox site or project, and it's like the Wild West, and you have, like, four hundred test workbooks in there that hadn't been touched. And forever, each one of those have twenty five revisions behind them. So that's a lot of space, and, if if you can get rid of it, delete it. Get it off there. The more you can go through your content and clean it up, the smoother, cheaper, faster migration will be. So and this is the part this is the reduced, reduced friction section. I was saying, do it now, whether you migrate or not, because it's a great house cleaning. House cleaning thing to do. And then data sources. So plan for the the migration of on premises data to the cloud, the more you can get off of your on premise. If you can get everything, off of on premise databases, you can totally eliminate Tableau Bridge or the need for it, if you can. So otherwise, otherwise you'll have to have Tableau bridge. That's infrastructure. You will still have to manage So that's definitely a a big boost if you can do that. And then utilize host data sources to connect to multiple workbooks. So a lot of embedded, embedded data in your workbooks, if you publish workbooks constantly, and you were you're embedding the same data in every single workbook. It's it's really hard to narrow down What is actually the same data? What's not? So if you can publish a data source and then connect all your workbooks to that published data source. It reduces the size, and it it eases the migration as well. So I'll move it over to Madeline, so for, planning for success. Awesome. Thanks, Colby. That was all really great stuff. We'll have a couple more links coming your way through the chat over the next few sections here. So let's talk about what it looks like to plan for migration success. If you think back to the moving analogy, There'd be no reality in which he'd go to sleep tonight, expecting or hoping to move tomorrow to your new house, wake up the next morning, find the nearest U Hall, load a stuff or box up your stuff, then load it, move it. And there's just too much to, kind of move off the cuff and the same is true for your tableau server to Tableau cloud migration. So at InterWorks, we recommend a very thorough approach to planning your cloud migration And today, we're gonna talk about four areas that we recommend you dedicate some extra time to considering in advance of migration. So the first area that we'll talk about is governance. Colby Colby mentioned on the know your limits section. That one of the criteria for Tableau cloud, at least in the typical deployment is that you'll be hosting your content on a single cloud site. If today in Tableau server, you're running a handful of different sites, maybe one for Sandbox, one for dev, one for prod, you'll want to think about a governance strategy in consolidating those multiple sites into a single Tableau crowd site. Again, there are ways to get around this with the advanced management add on, but a typical cloud deployment includes one site. So, Debbie from InterWorks is one of our colleagues and she has shared some really great strategies around project governance that will share with you and I think we already have in the chat. One of our favorite strategies to separating content by projects is to create high level projects for each business unit. So one for finance, one for marketing, one for sales, for example. And then underneath these projects, you might a sandbox and a production sub project onto which you'd apply permission specific to who you want to see that content. So you'll want to make sure that project structure as well as who's responsible for promoting content from Sandbox to production and ultimately the permissions around those projects that all of that is well defined in advance of your migration. Now also related to governance are a couple features that might be new to you if you are currently living in an older version of Tableau's server. One of these features is collections. Collections allow you to organize your content in an easy to access list according to what's meaningful to you, not so much, based on what project that content lives in. So this is a really great feature for your Tableau viewers and explorers to use to create a centralized spot for all of their favorite content. You'd consider you'll be adding in some enablement around this feature as you do your server to cloud migration so that your users are aware that this is something that could really add value to their date to date experience in Tableau cloud. And then certified data sources they've been around for some time on Tableau server. They are also supported in Tableau cloud. And one of our recommendations is that as you're thinking about moving content from server to cloud and you're often doing this through, you know, very, very close lens, making sure you're doing this methodically, this lends itself to a great opportunity to certify data sources and build confidence around the data that your users are going to be using over in Tableau cloud. The next section we like to give extra consideration to when planning is change management. So this is easily overlooked, but really important as it relates to instilling confidence in your users, once they get to the Tableau Cloud site. The complexity of a migration from Tableau server to cloud doesn't often often doesn't mean that you'll start the day in server and end the day in cloud. Depending on complexities or things that we encountered during the migration. Though we try to make it, of course, as seamless and fast as possible, You do want to consider what that in between window looks like from starting the migration to finishing the migration and how you manage content that's been migrated somewhere in between. So if you think for a moment about your creators, if they're not aware that a workbook they own and maintain has been migrated to Tableau cloud and they're going back into server and publishing and iterating on the version in Tableau server you have created now duplicate efforts in that you'll have to migrate that piece of content again over to cloud. On the other if you have a team who's in the middle of a high pressure week who depends on a batch of reporting that sits in, the sales project, for example, And that experience is somehow interrupted because they weren't anticipating that the content has been migrated. That could just evoke frustration, confusion for your users, and we want to stay away from that as much as possible for the sake of really building adoption and adoption of your tablet crowd environment. So what could be some ways to manage communication around content that's been migrated? We'll look at two ways. One is more manual, a little more involved. The other, is more seamless. So we'll look at two approaches here. These are two among many, but, figured this would be a good way to look at two of the options we see most frequently. So first off, if you think about that workbook in Tableau server, you might modify it literally publishing up a new version of that workbook once it's been migrated to cloud, you can publish to TapOS Server, a new version of the workbook with a text box right over the top, that tells your users this content has been migrated. It now lives in tablet Cloud at this URL. In that way, there's no confusion or or ambiguity your users would log in to Tableau server and be met with that message that there's now a new location for this content But we do acknowledge that that requires an extra step on each workbook that you migrate. So there's another option that we love to use and that is using InterWorks curator for a seamless redirect of the URL that's being called in the back end as your users attempt to access a workbook. So if you're unfamiliar, innerworks or innerworks offers a product called curator, we've built it, and it is our answer to a fully customizable analytics portal, and it centralizes your reporting whether it lives in Tableau, in thought spot, ultimately acting as a centralized hub for you to access all of that reporting through the same interface. So as this relates to Table Cloud migrations, you'd be able to point your users through curator to access their content Regardless of whether that content lives in Tableau server or Tableau cloud, the way your users would access it stays the same And it's only from the back end that you're actually updating that URL to point to the cloud location of that content. So if you have interest in that mode of change management for your cloud migration. We'd love to share more with you about curator, and we may have sent, a link in the chat also if you're interested in that product. So just as important as change management, intending to the workbooks over the course of migration, also wanna make sure that we're thinking about the data sources that we migrate. Especially because we want the user experience when they first get to Tap Cloud to be really positive and be really affirming that things are fresh there. Our date is up to date. This is an advantage over the old way of you know, going into Tableau server, all in all, we want it to be a really positive experience. So, of course, making sure that data sources are actually refreshed and, reflect the newest data once you start sending your users to cloud is super important, and you'll want to make sure that you're thinking about scheduling refreshes on your extracts well in advance of sending your users over to the cloud site. That one's a bit obvious, but, in the midst of of all the things you're thinking about when you migrate that kangal overlooked. And then finally, it's really important to, let's see. Actually, I think we're on to the next slide. Colby. Perfect. So communication related to change management communication is sort of a subset of this. This is much less technical in nature, but it has to do with the strategy you use for being very transparent and communicating the upgrade and the, things that are happening over the course of migration to your users So if you think about custom views and subscriptions, these are an example of a content type that would need to be rebuilt by your end users following the migration. And for many of us, it's been a minute since we built a subscription on a piece of content. The whole point is you build your subscription. It's sent to you daily, and you don't have to think about resubscribing or or finding that view again. It shows up in your inbox. Well, if this is the case for your users and they're now being asked to rebuild subscriptions, to their content that now lives into Outlook Cloud. It's possible they've forgotten how to do that. So we'd like to make sure that we're enabling our users with how to's. These are delivered really well in the form of videos. Even Slack messages, really quick things that can act as a reference for your users as they are, sort of dialing in their experience over in Tableau cloud. You might centralize these resources in an internal knowledge base so that your users know where to go, to find what they need, And back to curator, if you are using that to support your migration, curator has a really great built in tutorial function which basically acts as a drop down or this kind of subtle overlay when your users visit a piece of content that can display whatever message you want. And in the case of migrations, that could look like, hey, want to set up a subscription to this report. Here's how you would do that. So another great use case for curator in terms of your migration. And that enablement really core to getting ahead of any confusion or, frustrations for your users. Then if we think about, you know, the exciting aspects of migrating to cloud is that we're have access to a handful of new features, many of which you probably didn't have in your Tableos servers, often the case that your server is a bit out of date because there's so much more that goes into upgrading that. So we want to make sure that you're getting your users excited about new functionality over in Tableau cloud that they'll have at their fingertips once the migration is complete. So a couple ways you can do that, you know, send messages through whatever communication channels make sense. Maybe you're targeting your Tableau Center of Excellence, and you're encouraging your Tableau developers to download the latest version of Tableau desktop so that they can get familiar with those new features just in time for that cloud migration to finish so that you can quickly get to reaping all of the benefits of TapLA Cloud once you've migrated. And if you have questions around how to enable your users or what resources you might be able to share, we have a wealth of resources available in our blog. We've been sending a couple links to the blog so far in the chat, but I encourage you to explore what's there we offer webinars and we have a really strong enablement team here at innerworks who can also help you think about the best way upscale year, developers in maximizing top load cloud. And finally for our migration planning, let's talk about Tableau bridge. Colby hit on this a little bit, a little bit ago, but Tableau bridge is an area that requires some special consideration if you have that on premises data. So SQL Server, MySQL SQL, if all of your data lives in Snowflake, Cablow Bridge is not required for your deployment of cloud. The first thing that we like to think about when it comes to whether or not Tableau bridge will be required for your organization is do you have access to a cloud hosted database or data warehouse that you could move your on premises data into. Sometimes it's the case that we see clients who have Snowflake or another cloud hosted data warehouse, but somewhere along the lines of migrating their on premises data into that system the process was interrupted. Not all of their sources landed in Snowflake, and now there is this tablet bridge dependency. The first thing we want to think about is could we move those on prem sources into Snowflake so that there's actually no need for bridge at all. Sometimes that's not the case, and that's okay. That's why Tableau Bridge exists is to connect cloud to your on premises data. So if this is a requirement for your migration, Interimorx has built a workshop called Tableau Bridge Foundation where we deep dive into installation, configuration, security. But for the purpose of today's webinar, we're just gonna talk about a handful of things that you'll want to keep in mind if you are installing or recording tablet bridge for your cloud migration. So first, you'll want to identify a virtual machine where you can stall and configure your bridge clients. Bridge right now is only available for Windows operating system, but as of Tableau twenty twenty three dot three, we expect it to also be available for limits. And only one bridge client can be installed on a given virtual machine. We do recommend a virtual machine over a personal laptop because we don't want bridge, which is responsible for keeping your data fresh, competing with other resources and other applications on a personal laptop are using. So virtual machine is the ideal way ago when it comes to installing your bridge client. And then when possible, we recommend installing a bridge client on at least two virtual machines so that you can take advantage of pooling. Pooling is possible when you have at least two bridge clients and it serves the purpose of load balancing and distributing those data freshness tasks among available clients in the pool. So it gives you the best shot at data staying super fresh, and it is our our recommendation that you always have at least two clients. And then once bridge is installed and pooling is configured, you'll of course want to test the connections to your on premises data. If you're looking at an extract trigger that extract refresh. If it's a live data source that bridge is supporting, you can, of course, make a change back on the data layer. And make sure that you're seeing that flow through your recording. We have a link to the first blog in a six part series that Sarah and I wrote together And that will also take you into a bit of a deep dive into all things catalog bridge if you are interested in learning more. So before we move on here, let's take a moment to pause and reflect on these areas of planning. I'm curious to know from all of you which of these areas feels like it might be, the bulkiest to plan for and the most substantial. What which of these topics really resonated with you? Pick up another pole here, tablet bridge, right off the back. Seeing a lot of Tableau bridge, and you're certainly not alone if you have on prem data that you expect to keep fresh with Tableau bridge more often than not, we're seeing that as the case rather than some, you know, someone who has all their data in a cloud hosted environment. And then I'm seeing a good chunk of responses around governance authentication and scripting, that ties back into some of those considerations call be shared with us, and that'll make sense. Cool. A bit of change management. Great. Thanks for the responses there. Alright. So planning is a really substantial part of your migrations and We've covered a lot. There's other things that might apply to your unique migration. So InterWorks has a migration planning service in which we help you think about potential blockers solution for those things so that you have a plan of action before you jump into the implementation of your migration. We don't want you to have to anticipate every blocker on your own. There are things that we have encountered by virtue of doing many of these. And so we're we're happy to help you in building your migration plan, and we'll talk a bit more about that in a minute. Let's go on to the migration itself. And I find this to be kind of an important topic because we talk a lot about considerations, how to plan for it. But what does migration actually mean and how would this look in a manual sense and what can we automate? So keep in mind that the strategy we're talking through here is sort of assumes you've already addressed the considerations that could be waived and we done our due diligence before we begin implementation. Go ahead to the next slide, please, Colby. This is what a manual migration process could look like. And don't worry there are parts of this that can be automated. I'll also add that this is what a manual migration would look like today come twenty twenty three dot three. This will change slightly. So we'll look at that in a minute. First step would be to publish all of those published data source that currently sit in Tableau server over to Tapau Cloud so that those published sources exist in both locations. Then on a workbook basis, you download that workbook and you'd evaluate the data source connections that sit inside of it. If that data is embedded, you'll want to consider is it private network data or is it cloud based data? The reason for that is that today Tableau Bridge only supports keeping data fresh that exists as a published data source, which means if you have an embedded on prem connection within your workbook, You would actually have to first publish that out as a hosted data source, reconnect your workbook to the hosted equivalent, and then publish the workbook. Colby, if you wanna flip to the next slide, we anticipate this process to become easier, fast because the twenty twenty three point three Tableau bridge no longer requires that you publish your embedded on prem data sources. So that means you could download the workbook. If there's a hosted data source, you would reconnect your workbook to the version of that source been published to the cloud site, and you're good to go. Any of those embedded on prem connections will be supported with this new version of Tableau Cloud. Of course, it would be a lot to do this all manually, especially with larger deployments of Tableau server. So let's take a look at what can be automated. Perfect. Thanks, Colby. So content migration tool is a really effective way to automate some of the mundane tasks surrounding content migration. C Tableau CMT as you might have heard it can help me migrate workbooks published data sources, project and user group permissions. It's not at this time able to support the re creation of subscriptions custom views, data driven alerts, or favorites following your migration. So if you have some dependencies around those unsupported items, Please reach out to us. We have solutions for these things, and we'd love to help you with these more manual aspects of migration. Alright. So that wraps up our, migration planning, what it looks like to actually migrate. You've made it to Tapload Cloud, but you definitely don't have to get there alone. The process that we walked through today and the structure of this presentation really closely aligns with our tableau cloud migration solution and how we like to think about that. So if you wanna jump to the next slide, Colby, I'll just share a couple notes surrounding how we view the phases of migration. First is what we call an initial advisory session. This is really a conversation. We want to hear from you what are your goals for Tableau Cloud? What are the pain points you're trying to solve for by migrating? This is just a really easy organic conversation that helps us understand what the right next step could be for you. During this conversation, we talk a bit about the considerations back in Colby's know your limits section of this presentation because we want to make sure that you understand at a high level, what will be possible in Tableau cloud as compared to how you're running your Tableau server today. So if you are like me, I prefer to know kind of what the substance and that conversation could look like in advance And in the lower left corner of this screen, we do have a link to a type form, which you could fill out or just look through before contacting us to schedule your initial advisory. There's absolutely no expectation that you complete this before we have a conversation, but it does shed some light on the types of questions, we love to get at during this conversation so that we are accurately explaining the migration process to you as it relates to your unique deployment. After our conversation, we like to help you with a migration plan. So this migration plan is where we really deeply explore your top load environment, the architecture of your data, and we identify potential issues along with solutions or recommendations for what could make sense to happen before you migrate after you migrate to make this the most seamless experience. By end of the migration plan phase, you'll have a detailed roadmap to act as a plan of action as you move into the hands on migration. We have a service for that too. We'd love to help you implement your tap server to cloud migration. With all of those complexities informed and solution for in the migration plan, we can get right into the actual doing of your migration. And in this phase, we apply our knowledge of Tableau task automation. We have a really great team with expertise in this area to make this as seamless a transition for you, the administrator, you the user, whatever, role you play in Tableau. Our goal is to make the transition from server to cloud as streamless as streamlined as possible. And then following implementation and and one of the reasons why I love how we think about migrations is you'll receive a year of post migration support from our keep watch team. So following implementation, we want to make sure that you have continued support for tablet bridge administration, questions around data strategy, governance, things that, you know, might surface after you migrate. And so it's with our experience keep watch team. You'll receive that year of post migration support. And then, of course, we have other services that we'd love to partner with you on, I'm gonna actually hand it over to Sarah to wrap us up with that bit. Thanks so much everyone. Alright. We can head on to that next slide. So thank you, Madeline and Colby. There are a myriad of other ways, like as Madelyn said at at InterWorks that we can support you. So, for example, if you're concerned about the number of on prem data sources and maintaining Tableau bridge in a possible migration we can assist with managing those services so you don't have to. Through our service called Keepwatch as she just mentioned. Colby mentioned the opportunity to reduce friction or have that garage sale. And part of the process maybe identifying those workbooks that get a ton of usage that you absolutely need to keep, but they don't have the greatest performance. So we can work with you to optimize those workbooks, and we can offer training, for your dashboard creators so that they will know how to create more performant and efficient workbooks, moving forward. And finally, the demand for data in you know, native applications only continues to grow. And Tableau Cloud opens up a ton of possibilities with embedded analytics. If you've got those external customers or applications where you want to include, self-service analytics and tools a curator can help with that. So we'll go on to the next slide. We've been addressing some of our questions throughout the webinar, I really appreciate everyone's time here today. And so let's, we're gonna be sharing a survey following, this webinar. We'd really appreciate your responses. If you have any other questions, for Madeline, Colby, or I, you know, please reach out to us at our email addresses that are up on the screen. You will receive a copy. A recorded of recording of this webinar will be sent out afterwards. And we have, if you wanna learn more from us, you can check out our blog. But feel free to reach out with any other questions. And thanks for attending today, everyone.