In this video, John Ezzel. co founder of
bias Corporation, a managed service provider and
Oracle partner discusses the trade offs and moving
from on premises to SaaS ERP. And why a hybrid is
often the best approach. To learn more about cloud
era migration, and Oracle Cloud infrastructure,
click the link above or in the description below.
So I'm wondering, John, when you're working with
companies of buyers Corporation, what are the ones
that say have Oracle EBusiness Suite or JD
Edwards? What do they have to be willing to give
up? If they migrate most of their processes to
Oracle Fusion, cloud ERP.
So you hit on it before, but I'll tell you one,
two or three things you should give up right off
the bat is you give up controlling your own
upgrade cycle, you give up patching, you give up
coordinating the patch in between all those
different, you know, tertiary applications. So you
give that up. But you do get a chance to do a gap
analysis and really evaluate all those
customizations that you've developed over the
years. And the great thing about SAP and great
thing about Oracle is, you know, you, you are
given an application. And these these companies,
these these customers, these public sector
organizations, they expanded these applications
with hundreds or 1000s, of customizations. And
some of them some of that functionality is now
intrinsic in SaaS. Right. So if you do an
evaluation, think about all those patching all
that patching, you've done over the years, those
upgrades that you that you
passed over, and didn't do because of you know,
all the upgrades and you've customized yourself
into a corner, you give that up, maybe that
functionality is already built into the
application. So you never have to worry about that
patch again. So, and all those third party those,
those kimberleys, if you will, or those extensions
is customizations, and those integrations, maybe
those are all plugged in. But after you do that
gap analysis, and we call that our true north is
kind of a road, our roadmap and our, our analysis
and kind of business gap and technical gap
analysis. Once you do that, then you can say, all
right, well, at least if I can get 80% of what I
have today, and then the 20% that I don't have,
maybe I can do that as an extension in the past
layer, the platform as a service layer, the
integration layer, and then eventually, as that
functionality becomes intrinsic into the to the
SaaS product, I can shut that off. So that's the
ultimate goal. But then, you know, customers that
are, say, manufacturing customers that that
functionality might not be there yet in SaaS. So
then then you have to go with kind of an on prem
and cloud solution, a hybrid solution.
That kind of leads nicely into our next question.
I was wondering,
what are the situations where people end up with
hybrid cloud? Because I think on your website, I
read that, you know, hybrid is often the solution
I ended up going for. So what is it about their
typical situation where they would have to do that
you mentioned manufacturing as one but any others?
So manufacturing is one. And then you have you
know, we do a lot in financial services, we deal a
lot with federal government and many different
entities, utilities, retail. So where you might
have a hybrid scenario is,
Hey, I can move my financials, I can move my GRC,
I can move some aspects of my supply chain, I can
move that into the cloud right now. That's there,
it's proven. Lots of folks have already done it so
that that roads already been paid for you. If I'm,
like I said before, and processor discrete
manufacturing some of that secret sauce or some of
that functionality that that I've created over the
years, I'm not ready to put that into the cloud
yet, or the functionality is just not there yet.
Another scenario would be anything that's industry
specific, that may not be certified yet in the
cloud, whether you're dealing with, you know, some
public sector entities or some financial data
that's not been vetted. And and there might not be
a precedent yet for it to be in the cloud. Those
are some of the ones that are still hanging back
on prem that we've seen. And then you just have to
do the the hybrid cloud integration between those
two. Yeah, I was just about to ask about that. I
know that
I think that has to be a big part of it when you
go hybrid, I'm always curious to know how much of
it is integrating the business processes
themselves. And how much of it is like a lower
layer, like the database or middleware type, or
maybe it's all the above. It really is all of the
above. And, you know, doing that gap analysis
where you're able to map the business process
first. And you say, Okay, here's what we have. And
here's what we need. And whether whether that's
going to be on prem or in the cloud, that's going
to be up for roadmap discussion that everybody
puts it on the whiteboard, and we all agree on.
And then from the integration, some of it is easy,
you know, some of it, you know, you got API's
already laid out, laid out, you got already got,
you know, kind of that,
you know, integration platform already
established, and then some of it you have to
create on your own. And so we're still building
some of those out. But I think it's one of the
best practices that we've implemented is having
those kind of tough discussions up front and
showing what the dependencies are. Here's what
it's going to take to integrate. Here's the
testing that your folks are going to need to do,
you know, from the customer side from our side.
So, yeah, it's it's a bit of both still