Share and Enjoy !


Danny Ryan:Hello, this is Danny Ryan and welcome to the ThreeWill Podcast. Today, I have Chris Edwards here with me. Hey, Chris. How’s it going?


Chris Edwards:Hey, doing great.


Danny Ryan:Good, looking forward to getting an update from you. You’ve been busy, my man.


Chris Edwards:I always try to stay busy all the time. Try to.


Danny Ryan:Keeps you out of trouble.


Chris Edwards:Yeah, hope so.


Danny Ryan:Hope so. How are the puppies?


Chris Edwards:They are all adopted except for one. We’ve decided to adopt one.


Danny Ryan:To keep one, very nice.


Chris Edwards:There was struggle is trying to get a name. Figured it out when we finally got one.


Danny Ryan:What’s the name of the-


Chris Edwards:Sheldon.


Danny Ryan:Sheldon, sounds kind of formally dressed or something. Let’s get to it. I wanted to get an update on … I know you’ve created a trial version of the Migrator Tool.


Chris Edwards:Right.


Danny Ryan:I just wanted to get an overview of what that is and just catch up on things. I know you’ve been working on a video as well of what Migrator does and demo for me and just catching up with you as far as what things you’ve been up to lately.


Chris Edwards:Migrator, it is … Basically it’s a initial visual interface that allows someone to just download it. They want to see how large their Jive environment is. We typically work in terms of number of places. When I say number of places, in Jive there are different kinds of places. There’s the concept of the space, concept of a group, concept of a blog and a concept of a project. We just call all those places just to have a generic name term for it.


Danny Ryan:Okay.


Chris Edwards:One of the first things we do in a migration is we do an inventory check. We basically pool all of the different number of places and then a basic hit on the content. To have that initial conversation is hard to know how the day of a customer is. The Migrator utility in its current state doesn’t actually migrate content. It’s not what its intention is at the moment. We’ll talk about that in a minute.


Danny Ryan:The trial version of it, it just goes out and does these counts for you and just get-


Chris Edwards:Yes.


Danny Ryan:Okay.


Chris Edwards:It’s designed to be the super simple. All its trying to do is gather your Jive Instance URL, basically what you use to get the Jive. A user name and password that … In this case, the user name should have the access to all the different places that we need to find. Typically, it didn’t have to have right access-


Danny Ryan:Just real access.


Chris Edwards:Just real access that needs to be able to use the API behind the scenes and actually get hold of the places themselves. Then what it does, it goes off and does, this is magic behind the scenes, it pools all the details and just report a summary. It just allows that conversation to be very clear in terms of when we are looking for the number of places looking for a size of what you guys … What a particular Jive particularly has. We have a clear talking point and clear denominator to work off of.


Danny Ryan:Partially it’s kind of funny because when we’re talking about doing pricing based off of places …So many times I say species not places. I’m saying the right word places. I had some folks who prospects who were saying, “Okay, that’s great. How do I find out what that is?” I would be like, “Ah.” There’s not a real place you can go to. I’m assuming in the Jive admin where you can go see or just show you the same information, correct?


Chris Edwards:There’s not a clear way of saying, “Okay Jive, how many places are there and what does that break down? I’ve not been able to find a clear indicator of that. That’s what the simple utilities in its current state is designed to do.


Danny Ryan:There’s also a very real. This is almost like what you often do with projects for flashing one through the pipes which is seeing if somebody can test it against their Jive or whatever they happen to be running Jive-wise. This is just hitting drive, it’s not hitting SharePoint or doing anything with regards to Microsoft 365 or SharePoint.


Chris Edwards:Yes, that’s actually a great point. It’s only hitting your Jive Instance, so it is not … Before there’s backend information. It’s not recording information other than what’s in the log file, it’s log goes to the really application apps. In the video I pointed that out because I know what that is.


Danny Ryan:You’re storing the credentials anywhere-?


Chris Edwards:We’re not storing the credentials anywhere. The intention was to not do any of that. It’s really just an exercise to get the number of places to have that conversation.


Danny Ryan:Where does this go? I know one of the things I’d love to have is just 2, because a lot of people ask, “Can you just migrate one place for me?” I know maybe eventually if there’s some arm twisting going on and you have enough time we may be able to get to that or maybe not. Who know? We may need to work into it.


Chris Edwards:I’d love to look into it.


Danny Ryan:I know that’s something we want to do. There’s also maybe getting a little bit more information about sizes of things or what are the things are on the backlog right now or things that you want to add to the trial version?


Chris Edwards:The trial version, the next major … The logical thing to do would be to go a little deeper in terms of the contents. One of the things we do is … Part of the inventory process is we capture the number of places but we also do an initial high level pool of content that actually pool the binaries, not do the full mass of pool but the high level details of what’s in the content that allows us to get the number of content per place.


The beautiful thing about that is to do that in a simple way, adapt to the utility then we can actually start talking about how do we group all places in such a way that we’re able to batch them up. We can do them in a very consistent way. If we wanted to migrate 100 or 200 or maybe 1,000 at a time, that 1,000 we identify is similar to the next 1,000 and not guessing in terms of how long something is going to take. We get more predictable with how long an actual migration is going to take. The next phase would be more predictable, has a more predictability to the output and how long things will take to do.


Danny Ryan:Very nice.


Chris Edwards:It just helps us plan and it adds to the overall process of how migrations are done. That information will be super useful to have.


Danny Ryan:It’s a nice, I appreciate you creating a little video and I’ll put a link to the video in the notes in this podcast, but just walking through what the typical drive migration looks like and what the tool does. I know it’s a command line tool so its doing what it’s doing and it’s writing to a log file and you … I really appreciate you going through what the whole process is. That just makes it more real to me and for folks who want to see what does it look like to do an actual migration.


Chris Edwards:We’re trying to keep things simple. We’re trying to go after stuff that truly makes sense. We want to help people be successful in their migrations. We don’t want to overdo it or over-engineer it. At least we’re very specific about where we’re going after, ask the right questions and make sure we’re able to things correctly. Also estimate things correctly so we don’t over blow the budget or anything like that.


That’s the only designed to be … Someone to go from end to end, be predictable about it and be successful the whole process. Also, keeping the tool simple, allows us the customer is done very easily. Someone, “Oh, I don’t like the that works.” I said, “Wait.” The whole migration process, I want to change something about it. I’m going to make it very easy for us to adapt to that.


Danny Ryan:Very nice.


Chris Edwards:That’s the plan. That’s your idea.


Danny Ryan:You are in a middle of migration right now, right?


Chris Edwards:Yeah.


Danny Ryan:How is that going?


Chris Edwards:Going pretty well. Looking forward to getting this one under the belt as well, but it’s good it’s a pretty big one.


Danny Ryan:Big like certain amount of content or big like number of spaces or number of places?


Chris Edwards:Number of places.


Danny Ryan:How? Do you mind me asking?


Chris Edwards:We’re actually migrating 2500 but then archiving over 10,000 so it’s a fairly large effort.


Danny Ryan:Very nice. Well done.


Chris Edwards:Yeah.


Danny Ryan:Well done. That’s it for now. I appreciate these little updates and continue your hard work. There’s lots of people who are contacting us about migrated from Jive to SharePoint and Microsoft 365 and it’s amazing what you guys have built over the last couple of years. It’s not just the tool, it’s also the whole process and the far that you guys have put behind this that I appreciate.


Chris Edwards:We’re also looking at improving how we can really leverage the SharePoint. The SharePoint functionality in what it does. I’m really trying to change the way we think about … This is not your bunch of wikis. Let’s just not migrating Jive content, let’s make this content come alive in SharePoint and really take advantage of that. We’re looking into that as well.


Danny Ryan:I think we’ve recently seen some of the new you. All I changed is the SharePoint and some of them smell a little Jive like. They’re trying to go a little bit more down that pass. Hopefully we’re getting more towards they’re moving a one to one and the experience is similar to … In SharePoint to what you have in Jive. It’s because there some transition and there’s some change right now and hopefully we’ll see Microsoft 365 continue to improve the whole UX experience and then getting the content and hopefully everybody will be happier With that improved experience.


Chris Edwards:Absolutely. Looking forward to seeing that continue to improve.


Danny Ryan:Thank you for taking the time to do this, Chris.


Chris Edwards:All right, thanks.


Danny Ryan:Thank you everybody for listening. Have a wonderful day. Take care. Bye bye.



Share and Enjoy !

Related Content: