Episode Summary
In this episode of RecChat our host Zach Malloch is joined by Implementation Manager, Brian Hatch and Director of Municipal Support Services, Cullen Barber to discuss the 10.3 versions "end of life" and what that means for current 10.3 users. The group touches on the schedule of end-of-life events, working with VSI to migrate to the 3.1 version of RecTrac, how this relates to MainTrac 10.2 users, extended support options through 2022 for 10.3 users, and the benefits of moving to the latest version.
Recording
Transcript
Zach Malloch 0:27
And that song must mean that it's time for RecChat. And we have a special RecChat today, as most of them are. I'm joined by Cullen Barber, our director of municipal services and support. And Brian Hatch, our manager of implementation services, maybe not exactly the titles, but hopefully close enough to to work for today. How's it going, guys?
Cullen Barber 1:04
Great. Thanks for having us.
Zach Malloch 1:05
Awesome. Good to hear. So we had a poll that we're just starting out here. So this, this topic is all about RecTrac 10.3 End of Life. And I'm gonna go ahead and stop the poll so that we can kind of show those results. So we have a fair number of people that are already on 3.1 today, and then the bulk of the conversation is really going to focus on people on 10.3, and how they could potentially get to 3.1. And why they would want to go there. But we have a lot of 10.3 users. And we have a fair number of people who haven't scheduled their migration yet. So that's kind of our ideal audience for this conversation. And so Cullen, might as well just get started. So what exactly does end of life mean for 10.3?
Cullen Barber 1:48
Yeah, it's, it's not as scary as it sounds. You know, we've used the word in the past retired or mature releases for certain products. And it's the first time we've actually I think, use the term end of life. Essentially, what what we're, we're looking to do is, is stop the development cycle on 10.3 RecTrac and WebTrac. We're already kind of, you know, bouncing into and bumping up against some technical challenges sometimes as we try to work on, on RecTrac 10.3. And, you know, as most folks know, RecTrac 3.1 is almost six years old next month. So back in December of 2014, we, we released the 3.1 product. So that's becoming fairly mature now. So really, what the end of life means for 10.3 users is that the development cycle will be we stopping. That doesn't mean you can't continue to use RecTrac 10.3. So maybe you're not quite in the position to do the move or migration, you can still continue to use it, it will just potentially affect what is what is supported. If there's some type of issue that developer needs to get into well, that's that's where things change, right. And that's where we're kind of cutting, cutting that off at a certain point. So essentially, as far as dates go, so June 30, of 2021 is what we're kind of announcing as the date. But there still will be some opportunity, if there's a significant issue in 10.3, we will try to address it through the end of 2021. But it has to be fairly significant. And we have to be able to actually technically do that. If there's some barrier with with the progress, or other tools that we use, we would not be able to do that. So there's some risk, obviously continuing to use 10.3, if something were to come up. We were offering some extended support past you June 30, of 2021. So if for example, as you have already scheduled your 3.1 migration, there's there's no additional charge for the Extended Support. It will just be included through 2021. Once we get to 2022 it's a little different stories, we want to work with each customer to see see what the barriers would be to not having a migration done, you know, in by the end of 2021 or 2022. I guess all should add this, this timeline effects some of our other products. So MainTrac 10.2 is also end of life. June 30 of 2021. I'm not sure we have too many folks still using that as his MainTrac has been migrated fully into the RecTrac 3.1 platform. We have extended the FinTrac time management support through June 30 of 2021. The rest of the modules within FinTrac, that is end of life at the end of next month. So December of 2020.
Zach Malloch 5:09
And so, with the end of life, and one of the questions that I got, and actually, I realized, I forgot to say this, if any of the participants have questions, we have the q&a portion, kind of at the bottom of our video window here and feel free to add, I see somebody just put a question in there. So that's great. So when you wake up in the morning of the day of end of life, is there anything immediately that people are going to notice? That's different?
Cullen Barber 5:35
No, no, not unless, you know, Windows or some other technical technical issue crops up 10.3 is still going to operate as is. And we anticipate people will still be able to use it. It's just if there's, you know, introductions of things that impact, you know, drivers for hardware, operating system changes, security issues, you know, credit card interface changes, those type of things, you know, we may not be able to change in the software after June 30, of 2021. So, I think it's best to kind of be prepared that if something does come up, there's some risk that certain feature or portion of the software may not work as expected, we may not have the ability to to fix it at that point.
Zach Malloch 6:25
All right, and a couple of the questions that are coming in. So is there a lot of these are kind of about the cost that would be involved, either with migration or with the Extended Support? Would there be a best place for people to go to get that information?
Cullen Barber 6:41
Sure, we'll include that with the response to the RecChat here. And we'll also include a webpage link that folks can go to, to look at it share with an organization as well. But yeah, there's there would be if you kept schedule your migration, in 2021, there would be some fees for the 10.3 support based on your number of users. So we're still working on the pricing. But I think for example, for a small organization, you know, two to five users, there would be a $300 fee, you know, for a six month period. So just to give some folks some idea. And we've also got some good information on what the process looks like to migrate to 3.1, and maybe maybe Brian can kind of fill us in on you know, what that looks like how to schedule it, what the process is, and, and give folks a good idea of what what 3.1 might look like.
Zach Malloch 7:47
Before you start with Brian real quick, because there's, there's actually two questions that kind of go directly to this. So Stacy's saying that for record retention issues, they feel like they need to keep 10.3 for seven years, just in case. And then Nancy is basically asking if the information transfers from 10.3 to 3.1. So if you could just like kind of have that in mind as answering the the migration question, Brian?
Brian Hatch 8:12
So all the information from 10.3, does carry over with 3.1 migration center, all that kind of answers, the retention question. So I feel like when you if and when you migrate, it'll it'll carry over. The process, I'm just gonna kind of throw the process out there for everybody. The very first step, if this is brand new for you, is really going to be reaching out and setting up what we call a discovery call. So it's kind of a semi formal call, where you kind of talk through how you use rec track, usually involve someone from it, just to kind of get everybody's questions answered, it gives us a kind of a base knowledge of how you use and what you use RecTrac for. And that kind of allows us to kind of determine the effort that's going to be involved to migrate you over. So we kind of determined the number of hours essentially with the remote option that it would take to to get you from where you are today to the 3.1 version. So it kind of starts there on kind of our side. And we'll send out some contact info for how you get you guys reach out to kind of start that process. From there kind of goes to sales, so they can actually get you an accurate quote. There's no, I guess, cost to upgrade outside of the the training costs. So that kind of our time to kind of get you to the new version is really worth where the costs come in. Once you kind of just kind of keep going with that process. Once you see the quote, and you've got to kind of agree to move forward. It then kind of goes to the scheduling piece. So we're going to look at our schedule and kind of obviously look at your schedule, get on a call and kind of determine what the timeframe is that we're actually going to try to get you on you know 3.1 Bye You know, x date. So we have a little conversation on that. And then from there, we kind of shifts over, you'll end up getting, you know, sign a consultant. And they'll work with you through kind of the whole process that we kind of have set up now to move through a test migration. So taking your 10.3 data, and kind of converting it over and the initial stages to allow us to do trainings and do testing and things like that. And then all the way through to again that the go live date, the migration date, where you actually do cutover, from 10.3, and you start processing in the new 3.1 version.
Zach Malloch 10:39
Perfect. And so we did have a question coming in asking if there's any difference in the end of life for RecTrac versus GolfTrac?
Cullen Barber 10:48
Yeah, it's actually it's good point. So RecTrac and GolfTrac. 10.3 is the same thing. Yeah. So the GolfTrac 10.3 would be on the same timeline as Rectrac 10.3.
Zach Malloch 11:01
Perfect. And then Brian, or Cullen had something else
Unknown Speaker 11:07
I just gotta mention, you know, one, one kind of myth we've heard for. So some folks have said, hey, well, if I go to 3.1, that means I have to be in the cloud. And you guys have to host it. But that's, that's not necessarily true. Even though 3.1 is a web based product, you can continue to self host, with your own servers if you want to. So it's not something where you're forced to go to the cloud, necessarily, when you go to 3.1, although we do have a lot of customers that have moved to hosting, and we can talk about some of the benefits of that if people are interested. So just wanted to put that out there, I think, definitely heard some folks say, Hey, you're gonna make us go to the cloud? Well, not exactly. You can still self host and have it on your own servers if you want to.
Zach Malloch 11:59
Yeah, so there are some questions kind of related to the the topic of record retention from before and data transfer. So you want stuff and he was saying is that they decided not to migrate a lot of their information, because they had a lot of stuff in 10.3. And that's kind of why they were maintaining that as a separate database. And they want to be able to keep that for for the 10 years for that record retention. So I guess the the question, and it's a little bit nebulous in this case, but you know, we're not actually they're not actually using 10.3. But they want to have it available and be able to spin it up and get access back to the database at some point in the future. With the vulnerability be if like, let's say, Windows servers, update, and progress 10 doesn't work on the new version of Windows, and then you could potentially have an issue getting it up and running.
Cullen Barber 12:54
That could be a risk, right? Yeah, that if, if you tried to transfer that database to say whatever the latest Windows Server operating system is, that's, that's where you run into trouble. But if you can even keep your existing server 10.3 server infrastructure running, that would be fine. I'm sure others will do that, too. That's that's probably not going to be just a few few folks. Imagine many will do that.
Zach Malloch 13:22
Alright, quick comment from Meghan saying that they migrated in August of 2019. And they are loving 3.1. Can't imagine going back to using 10.3. We've certainly heard that in some of the RecChats that we've had. So that thank you very much for that. Vote for the migration. did have a question about whether or not somebody could get scheduled for a migration before the cut off. And if for any reason, they weren't able to get the schedule to absolutely complete by then if they would then be incurring extra fees by migrating a bit later than that. If it's kind of our scheduling. That's a little bit of an issue.
Cullen Barber 14:00
Right. Good question. Yeah. So there would be no fees in 2021. If you've, if you've basically reached out to schedule, okay. So even if we, you know, you can't get scheduled to migrate by June of 2021. That's okay. We're really just looking for people to try to get get things moving. So yeah, so if you're not scheduled to migrate until, you know, December of 2021, that's okay. There's no additional fees there. It's, if potentially push into 2022. That's where we'd have to have a discussion on if there's additional extended support fees involved for 2022.
Zach Malloch 14:38
I think that that addresses a lot of the questions that are basically saying that their budgeting for 2021 might not come into play until June 31st. Right?
Cullen Barber 14:48
Yeah, exactly. So if they're running on a fiscal year, you know, July 1 to June 30. You may already be in your fiscal year that ends June 30. And you need to make sure you have it budgeted maybe four Are the July 1 2021, through June 30 2022. So that's fine, we'd have happy to work with folks on that, if it's a budgeting type issue, we just really want people to start thinking about it as, as we know that there's going to be some, some technology issues we're going to start bumping into we already, we already have to some degree for 10.3. So we just we feel is probably going to be more as we inch further into the future. We just don't want people to be caught in a spot where they're, they can't function or part of their business, you know, it doesn't work as well as it should. And they have to try to scramble and react really quickly as best to try to get things planned out as soon as possible.
Zach Malloch 15:45
Right. And so kind of going back to the planning thing, and this would be more of a question for you, Brian. So Ryan is asking or saying that they're interested in migrating to 3.1. But they currently feel like they're playing for paying for the full House of RecTrac where they're only using the living room. So they used to use more modules than they currently do. And then when the question comes up as far as what they're going to be migrating over and potentially be a conversation with sales about what modules they're licensed with. But then can you talk a little bit about some of the options that people have when they're deciding to do a migration? And what data they actually bring over?
Brian Hatch 16:18
Yep. So it's, it's kind of an individual conversation we have with everybody. So you know, what parts do you bring over, for the most part, you know, household data, and all module data is going to kind of come over. And in most scenarios, there's some different ones we can kind of get into, for different exceptions and special cases. But essentially, it all comes over. And you have some flexibility on the kind of pieces that works at work off those modules. So we call them rules and fees, questions in 3.1. So you can actually you have control to say, I want them for like the activity module, but maybe I don't want them for the facility module. So when we run the migration process, those are one of the things we get to choose. And typically, we bring everything over in a test migration, just to give you guys have a picture of what what it would look like if we do because that is the most popular option. But once you get a look at look at your data in the 3.1 database, in that test database, then you can kind of make a determination that the eldest came over, and then do I want that to come over and we do this again, for for the live migration. So there's definitely some flexibility and some options, kind of kind of built in there that some some customers really picked up to, to kind of reconfigure certain parts of their database just because they know it's going to be easier going forward to manage and update and kind of live with the new version, as opposed to do what they've always done in in 10.3, for example. So it's definitely a discussion we have with anybody kind of going through the process.
Zach Malloch 17:51
Right, and then talking about the process a little bit. So Nancy is asking is, are we doing this remotely? Are we still doing travel? Or can they save in those travel costs and have somebody on their side to help and further reduce the training side of things?
Brian Hatch 18:05
That's a good question. So obviously, this year was the last three quarters, we've been doing remote, all remote migrations, which has been new, it's kind of the reverse of what we were doing before, which is we required on site time, leading up to this year. And we've done maybe 40, 40 Plus migrations remotely at this point through this year, it'll probably be on pace for 50, plus, by the end of the year. We kind of follow the same kind of process, that would be if it was on site, we set up kind of training sessions the month or two prior to the live migration where we can introduce you to key concepts, again, your tests migration, your test database is really kind of a huge tool in that we do the trainings in the testing. And it kind of sorted out all the problems that we might run into the live migration and address them at a time when you know, things are less stressful. And then where things change a little bit is the live migration we could sell right? So whereas before we would have been on site. Now, it's just like we're doing now through a through a zoom session. Right now we do kind of two dedicated days is kind of what we plan around. So usually, it's a Monday or Tuesday. But again, there's some flexibility there, depending on what your needs are. So we'd be kind of dedicated getting the live migration done on a Monday. Usually, it's more reconfiguring and changing things on a Tuesday. So we work with you more or less all day on Tuesday to kind of get things prepped and ready to go for live processing in the database. From there, the rest of the week is kind of different for everybody. We try to schedule in kind of half day chunks. So you might do maybe only need a half a day on Wednesday, and maybe half day on Thursday. It just depends on your size and your needs, where we might do additional maybe trainings, maybe it's just we're available for you guys for questions and answers. As you're kind of now doing live processing those naturally kind of come up. But that's really the big difference. Obviously, instead of me standing in front of you, I'm now coming to you live through a zoom session. So it's quite a bit different. But the same, I guess, a couple of suggestions we found from folks, at least through the training phase. But even through a live migration is, if you had like a two computer or two monitor setup, we found that that really works best. So you can kind of watch what we're doing on one screen and maybe follow along with it on the other. Or in certain situations, if you have like, a training room kind of spaced out. And you can have us up on a projector with the same concept where you can kind of see what we're doing. Follow along, those types of things we found work really well. But they're not required. Because obviously, if people were all remote for whatever the reason is COVID. Or otherwise, you can, everybody could be at home join a zoom session, we could still actually do the trainings we would normally do and it would, we're pretty flexible on that front. So definitely pretty good success going remote, I actually think it's going to be probably one of our primary options going forward, even after pandemic we'll probably be maybe doing a mix still. But I think the remote options proven really worked well for folks. You mentioned the savings on that the airfare, the hotel expenses, things like that those can really add up and definitely make it a little bit more palatable for those aren't included.
Zach Malloch 21:31
And I wanted to talk a little bit about you just mentioned that we kind of customize that we have a discovery call with every customer and kind of discuss the best options for it. And we had two question or two more comments and questions come in that kind of illustrate opposite sides of that. So one is Robin said that she was very happy with the 3.1 migration, they migrated in March of 2019, they decided not to move anything over from 10.3. And they just rebuilt the database from scratch. And they're very, very glad that they have done that. And then the flip side of that Jamie just mentioned that they migrated, they finished migrating two weeks ago, after a couple of weeks or a couple of years of kicking the can down the road, they had a 10 plus year old database with over 11 million receipts. And it went much smoother than expected thanks to our buddy here, Brian Dillon and the whole VSI team can't recommend 3.1 highly enough so powerful and configuration options. His advice for those that have a migration in the future would be use the record chats, use the labs, use the other materials to learn and get prepared during that test migration phase, ask a lot of questions. And you're able to build all new fees and bring over all the history and it's working really well so far. So another really great kind of testimonial there. Thank you so much for that, Jamie. And then some of the other questions that are coming out here are, you know, kind of so Annie's asking a really good question about the type of preparation they could do. Is there anything that like just general sort of database cleanup? Or is that something that would be more specifically addressed during a discovery call Brian?
Brian Hatch 23:06
we definitely get into more specifics on a call that generally most people would look at maybe a household purge. So if you had a cut off of three or five years that you said, if they haven't had any activity in your database, that's a really common one that we see a lot of people end up doing. The other, I guess, common one that we'd call out would be like duplicate households. If there's anything we could address in, in the 10.3 database, as a preparation step, that's one that we can always highlight. And if you get those obviously cleaned up in 10.3, and then you're not dealing with 3.1. So there's other purchases and other things that could be done. And there's other standard ones that kind of are part of the process that you'll see with activity cleanup and different modules. A lot of men up, we end up doing them in the 3.1 version, because of it's much easier to kind of clean up and hide records in the new version, as opposed to trying to do the kind of old school purges in 10.3, but we will get into all those specifics, as we go through the preparation for the migration.
Zach Malloch 24:12
A couple of questions that are kind of related to each other. So what's what's a typical timeline, let's say an average customer, and let's say if you have an example of somebody that's really dedicated, and they want to have as as quick a turnaround as as possible.
Brian Hatch 24:27
So I guess if I was gonna throw an average, you've probably a swipe from start to finish right here to start the conversation today. The end, I think I meant to mention this earlier. So we're actually scheduling if we were to start the conversation today, we're actually scheduling into April right now, as far as getting you on the books, as of today. So there's a timeframe of three or four months, I guess, depending on when we actually start. On average, I would say leading up to now it'd be maybe a two to three month window It's been even closer to the norm maybe. But we have also done some kind of quicker turnaround ones over the course of this summer where, for whatever reason, they said, we've only got X amount of weeks to kind of prepare before, we have to do it before x reason. And then we basically did rather than doing like a training or two a week, because giving more of a dedicated layout over the course of a couple of weeks as opposed to a longer timeframe. And they worked out well. So there's no kind of right or wrong way that we found. But the more lead time you have, it's always great, right? So we always try to do the test migration. Probably almost as soon as possible after we can initially get things scheduled, right, we try to kind of get that on the books, just kind of check that out. Because that really opens up the door to you guys. Having access to your database, you have kind of help accessing kind of some videos and different tutorials that we have. So if you want to kind of self learn on any of this, you can, even before we get into our kind of dedicated training sessions with with our staff, so the same time we were kind of ramp things up, I guess, the month prior, right? Because if you're three months out, it's kind of hard to really get into it. But when you're a month out, that's really where, you know, once or twice a week, we kind of try to get everybody focused and prepared, leading up to that final go live week.
Zach Malloch 26:25
Great. That's, that's very good information. So, Cullen, this might be something that you've already answered, but maybe we could just reiterate. So Susan's saying that their organization has some big ticket product projects scheduled for 2021 might not be able to make a decision before the end of 2021. So could you revisit any options that might be there for extending into 2022?
Cullen Barber 26:48
Yeah, no, great question. So we're planning on extending some level of support for 10.3, you know, through 2022, we realize based on, you know, budgets, COVID. And even our scheduling, it's probably not gonna be possible for everybody on 10.3 to be, you know, migrated by the end of 2021, just doesn't seem like that's going to be a reasonable amount of time for everybody. So, yeah, we expect to have some some options, you know, through 2022. And I'm sure, you know, at this point next year, we'll be, you know, kind of clarifying what that looks like in 2022, as well.
Zach Malloch 27:26
All right, and then variations of this question has come in a few times, but along with the budgeting into 2021, maybe not having new funds available until July or even, you know, April or whatever. So, if somebody wanted to begin the process, what's the earliest they could begin the process before the funds would come due? So if they are kind of balancing that that beginning of the fiscal year sort of conversation here?
Cullen Barber 27:53
Yeah, I mean, I think we can start the discovery call process at any time, right? Start talking about it in the planning stages. So that would be kind of the first step. And then it's not really until we tried to actually nail down a scheduled date that we would want to know how, what the funding looks like. That That makes sense. But yeah, we could we can start anytime talking about what the discovery and start the plan and get a plan started with people really, at any time starting now.
Zach Malloch 28:23
Great. That's perfect. And then Christine had a question. So this is a little bit more in the database prep, and also comparing maybe a 10.3 capability to a 3.1 capability. So they're saying that with COVID, they've had to have people make appointments for using our pool and had to make those people make households normally, it would have just been like a daily admission type of thing. So they're curious if getting ready for this, if there's a way to purge household to only have those, those pool reservation records, and then kind of extending into the idea of 3.1. If they wanted to do something similar and reserve kind of hourly sessions, is there a way to do it without creating actual households?
Cullen Barber 29:07
Do you wanna try that Bri?
Brian Hatch 29:09
I could try it. It's a good question, I guess on the reservation piece without an account. We'd have to we have a few different modules that I guess people have been kind of using over the past few months to kind of accommodate those. We could definitely do something like, like tickets are one of the modules. There's a couple of modules that can do with that don't require actual household to be linked,
Cullen Barber 29:34
trip, trip or ticket potentially.
Brian Hatch 29:36
So we probably just have to talk through those options with them to kind of figure out what which one's the best fit because a few of them have different features or functions that may drive it one way or the other.
Cullen Barber 29:48
I think we would have to like the question about could we not bring over those reservations? That would be a little trickier task right to try to if they actually have a household in there. You know, they're only first sir and types of facilities, I think we'd have a tough time not bringing them over. If, especially since they're a more recent transaction, would you agree?
Zach Malloch 30:10
Yeah, I think you'd have to be getting into some more manual work going in and assigning a purged comment or something to the households then running household purge, but yeah, could get, but then you're potentially losing the records of those transactions anyway. And if you wanted to maintain those that could could be important. So Angela has a question. So she's curious if in general, is it better to consider starting over or to do a migration? Kind of a weighted question there guys,
Brian Hatch 30:46
I usually say, bring everything over or don't bring everything over as
Zach Malloch 30:49
Yeah, start from scratch, or bring everything in migrate.
Brian Hatch 30:52
I generally push people to bring bring things over, at least the complete start over is a bigger undertaking, it's, it's gonna require a lot more of an investment, I guess, as far as time and an effort really. So that's why I tend to push people towards bringing things over. And usually when we get into the details against this kind of a, it's a pretty common conversation we have is, when you when you have the reasons of why you don't want to bring something over the issue, people have specific ones, will we, as we talk through them, we can usually say, Well, it's because we don't like the coding scheme. Or if you don't like that the old records are there. And a lot of these reasons, we actually have a solution for right, we can automatically kind of clean up records and hide the old ones you don't see, we can do some conversions, bulk conversions to kind of get things set up the way you really want them going forward, but still not have to invest all the time and all the effort to to start from scratch. So there's, there's definitely a discussion that is behind and depends on the details.
Zach Malloch 32:02
Yeah, and Kristin made a good point that if you do the migration, and you pull the data over from 10.3, two 3.1, then that data lives in 3.1. And you don't have to worry about that maintaining the 10.3 database for for record retention purposes. It's a really good point. So Cullen another question just coming up about the budgeting sort of stuff. So Aaron is saying that their annual support is set to end on 1231 2020? If we renew support for 2021? Will it be at the budgetary numbers he was given earlier this year? Or will you have to reach out for an extended support?
Cullen Barber 32:35
Great, great question. So if if you've got if you scheduled your 3.1 migration, then the previous quote should be fine. If you haven't yet been able to schedule a migration, there's a potential for the Extended Support fees that they might kick in. So kind of depends on where you are in the process. But probably something to you, you want to circle back directly with, you know, with sales, or you can you want to shoot me an email I can I can get the process started. We can we can check on that for you as well. Because that depends on where you are in the process.
Zach Malloch 33:16
And so Ashley was curious if you could discuss the end of life for MainTrac. So she says their department has chosen not to migrate to the newer version, Will they still be able to use 10.2 as it currently exists? And how long would they be able to expect to continue using it in that case?
Cullen Barber 33:30
Yeah, yep. So kind of the same thing. So you can continue to have it running there on your servers and network. You know, the support for 10.2 MainTrac would end on June 30 of 2021. So that one's it's kind of a hard stop as far as trying to get help from a Vermont systems representative. You know, you still be able to use use the system as long as it's running on your servers and things like that. Any self help or tool we've already built you'd have access to as well.
Zach Malloch 34:06
Okay, well, that. That brings us actually three minutes past our time. So I want to let everybody know that we understand. And if they need to jump off that is totally fine. As of right now. We have no more questions. So thanks for all the time and dedication to answering those Cullen and Brian will kind of give another minute here as we're wrapping up. If anything else pops up. We can go there we go. Got another positive response, Stacey says that she's excited to upgrade to 3.1 in 2021 looking forward to doing what they need to do to get things ready for a smooth transition. And that's that's exactly what we're looking for. And yeah, getting some thanks so we'll go ahead and leave it there. Thank you, Cullen.
Cullen Barber 34:46
Great. Thank you, everybody.
Zach Malloch 34:48
Thank you, Brian. And we will we have recorded this we will be wrapping this up. We'll be posting it to the RecChat archives. We'll have a couple of documents that we'll be putting up there to accompany this As soon as we can so thanks everybody for your attention and questions and participation and we'll talk to everybody soon
Cullen Barber 35:06
thank you
Zach Malloch 35:10
if I can just hit that in button I can't do it with the question and answer still up here we go all right now we'll say goodbye to everybody