According to Atlassian, over 90 percent of businesses use cloud software. Is your organization interested in becoming a part of that 90 percent by migrating to Atlassian Cloud?
With our six step process, E7 Solutions can help you make that move an easy one. We’ll start with an overall assessment that covers the technical and team elements of your organization. Then, we’ll get into developing a coordinated plan that will smoothly and effectively prepare your team, making sure we have the tools we need and a proper understanding of the environments. Once all of this is covered, we’ll validate and deploy.
Fear not, we always follow three core principles to ensure you’re putting your team in the right hands. Our promise to data integrity, commitment to time and schedule, and focus to minimizing user disruption are our high-level concentrations.
Click on the video above to hear how Ana Galofre and Michael Abdelnour explain how E7 Solutions gets Cloud Migration done, easy. Or skim through the transcription below.
Hey, Ana, how are you?
Hello, good afternoon. How are you?
I'm good. I'm good. Thanks.
I have a question for you, and this is going to... Topic is going to shock you. I want to talk about Jira Cloud, but I want to talk specifically about migration. We've stood up a lot of new customers on cloud. I have a lot of server on-prem customers. I want to walk them through this process. I've done a lot of research independently, but I was hoping you could just sort of give some insight into exactly what our process is and what the principles are behind that.
No problem. We have a six kind of step process for any server to cloud or data center to cloud migration, starts with an overall assessment. It's both a technical assessment and also kind of an assessment of the teams. Are there more than one physical location that we need to coordinate time zones? That kind of stuff. From that assessment, we develop a plan and we coordinate that and go over it with our clients' customers. We'll do full on prep, so the third step is prepare for it. What do we need to do in terms of tools that we're using or environments that we're standing up? The fourth step is we'll do a full pre-migration run, so we'll test the whole thing. Then, the fifth step is we'll validate it. The sixth step is we go with a full on production deployment.
Okay, great. Talk to me about... Two of those jump out at me, one, the assessment and, two, sort of the post-migration validation. How do we perform those? Is there anything about those steps, I would assume that's what most people would go through, that kind of sets us apart?
Yeah. Great question. We have three core principles to all of our data migrations. First one is data integrity, so we have to ensure that the data is there and it's accurate. The second one is that we kept to our timeframe and our schedule that we laid out. We want to make sure that we're doing this in the timeframe that we established as part of it. Then, the third one is keeping user disruption to a minimum. All of those steps I talked about, especially the ones that you highlighted, really emphasize we want to know what the user patterns are, especially if they're in more than one time zone. We want to know what we have to coordinate against, and we really want to limit the disruption to any user. Then, the validation one that you asked about, it's all about the data integrity. We want to make sure that the plan is rock solid. We know it works. We've already done it. We know the data is going to come across the way we expect it to. Data integrity is there. User management or, excuse me, user disruption is at a minimum and we're doing it on time.
I'm just thinking through sort of, as a client, what I would want to see. We're checking all of any add-ons, any integrations, all of that gets sort of part of that dry run.
Exactly. That's kind of the technical side of it, right? What else? What version you're running, what technical steps or firewalls, or what technical things do we need to consider? Then, the whole other aspect of the assessment is how do people use it, right? Do people need to be trained on the cloud? Do people... The way [crosstalk 00:03:39].
It's not exactly the same?
It's not exactly the same, right? Do they need to have any training as part of it, we need to support them? Then, really is anything going to change? We've talked before about some of the differences, so how they use it might be a little bit different. We want to make that as part of the consideration so that on the other side of the migration, those users are, excuse me, they are handed the tools to be successful in the new environment.
Okay. That's awesome. Sounds like a very cohesive, turnkey migration plan. I like it.
We try to make it as easy as possible.
Awesome. Thank you so much for your time. I'll talk to you soon.
Sounds good. Take care.
Okay. Bye Mike.