Table of Contents

Introduction & Key Findings

Introduction

Key Findings

Expectation vs Reality

The Urgency to Migrate

Top Triggers

Top Benefits

Average Annual Oracle Database Costs Before Migration (License + Maintenance)

Reduction in TCO

Estimated vs Actual Time to Complete the Migration to PostgreSQL Planned vs. Actual

Downtime During the Migration to PostgreSQL

Top Expected vs. Actual Challenges in the Migration Process

Managing & Consuming PostgreSQL – Planned vs. Reality

Demographics – Job Responsibility and Seniority

Demographics - Industries

About Stratoscale

3

4

5

8

9

10

11

12

13

14

15

16

17

18

19

20

Introduction

In this report, we analyze the responses of those who are in different phases of planning to migrate from Oracle to PostgreSQL (101 respondents), as well as the responses of those who are already in the process of or have completed their migration (105 respondents). We then present key findings by comparing between these two groups, which we refer to, respectively, as “Before” and “After” in the report.

206IT, DevOps, Software Architects, App Dev Managers and Database Managers

© 2019 Stratoscale 4

101Planning to migrate

105Already migrated

Stratoscale’s annual Oracle to PostgreSQL Migration Report compares the challenges and best practices of companies before and after migrating from Oracle to PostgreSQL databases. The results are based on responses from 206 IT, DevOps, Software Architects, App Dev and Database professionals from around the world, collected through an online survey conducted in Q2, 2019.

Key Findings

© 2019 Stratoscale 5

Urgency to migrateCompanies are in a rush to migrate at least 10% of their Oracle database footprint.

86% of the “Before” group plan to migrate more than 25% of their Oracle footprint over the next 12 months.

36% plan to migrate more than 50% of their Oracle footprint.

36%

86%

Top triggers driving migration

52%

51%

48%

Digital Transformation

Cost Reduction

Move toPublic Cloud

Reduction in TCO is better than expected

57%

68%

While before migrating,

After migrating, actually

expected at least 20% improvement in TCO.

reported an improvement in TCO of 20% or more.

Key Findings

© 2019 Stratoscale 6

Surprising benefits after migration

64%

48%

While before migrating,

After migrating, only

expect cost reduction to be the top benefit.

still consider cost reductionto be the top benefit.

After migration, respondents realized additional benefits they had not expected.

As planned or less

As planned or less

Key Findings

Time taken for the migration

Downtime experienced during the migration

68%

66%

32%

34%

More time

More time

About two-thirds of the companies complete the migration as planned or sooner.

Two-thirds of the companies experienced the same or less downtime than they had planned.

The majority of post-migration respondents opted to manage and consume PostgreSQL as a managed service (34% more than those who had planned to do so before migrating).

Managing and consuming PostgreSQL

63% Managed service

9% DIY

29% Enterprise product

© 2019 Stratoscale 7

The Urgency to Migrate

All respondents in the “Before” group reported that they plan to migrate a minimum of 10% of their Oracle footprint to PostgreSQL over the next 12 months.

86% of them plan to migrate more than 25% of their Oracle footprint, and 36% plan to migrate more than 50% of their Oracle footprint over the next 12 months.

91% of respondents in the “After” group reported that they had already migrated more than 25% of their Oracle databases to PostgreSQL.

60%

50%

40%

30%

20%

10%

0%

60%

50%

40%

30%

20%

10%

0%

Less than 10% 10%-25% 26%-50% 51%-75% More than 75%

Less than 10% 10%-25% 26%-50% 51%-75% More than 75%

15%

8%

50%

38%

30%

37%

6%

16%

0%

1%

Figure 1: Percent of Oracle footprint the “Before” group plans to migrate to PostgreSQL over the next 12 months

Figure 2: Percent of Oracle footprint the “After” group already migrated to PostgreSQL

© 2019 Stratoscale 9

Top Triggers

The top three triggers driving a decision to migrate from Oracle to PostgreSQL are digital transformation, cost reduction and part of a strategic move to the public cloud.

While cost reduction is one of the primary (but obvious) reasons companies migrate from Oracle to PostgreSQL, this question shows that they place at least equal (if not greater) importance on their need to transform themselves to achieve the speed and agility required to support the pace at which the market expects them to create and update their apps.

The need for companies to digitally transform themselves is of equal (if not greater) importance as reducing costs when deciding to start their Oracle to PostgreSQL migration.

0% 10% 20% 30% 40% 50% 60%

52%

51%

48%

39%

35%

32%

28%

Figure 3: Top triggers driving the decision to migrate from Oracle to PostgreSQL

52%

51%

48%

Digital Transformation

Cost Reduction

Move toPublic Cloud

Digital transformation

Pressure toreduce costs

Moving to the public cloud

Transition to open source

Support modern applications

Contract with Oracleending soon

Enableself-service

© 2019 Stratoscale 10

Top Benefits

The same top three benefits were both expected before and gained after an Oracle to PostgreSQL migration. These are: reduction of costs (64% expected), ease of use (44%) and improved stability (34%). However, after migrating, additional benefits became more prominent.

For example, while 64% of respondents in the “Before” group saw cost reduction as a top benefit, only 48% in the “After” group saw it that way. Instead, other benefits received greater importance after completing the migration.

An increase was seen in improved stability, with only 34% of respondents expecting it before migration, but 40% experiencing it as one of the top three benefits after a migration.

Another surprising and significant increase was seen in supporting developer innovation. While 27% of respondents expected to benefit from developer innovation, in fact, 39% realized this benefit as a result of migrating from Oracle to PostgreSQL.

Migrating from Oracle to PostgreSQL presents some surprising benefits people do not expect.

0% 10% 20% 30% 40% 50% 60% 70%

48%

42%

40%

29%

30%

20%

39%

30%

25%

7%

64%

44%

34%

32%

28%

28%

27%

27%

26%

9%

Figure 4: Top 3 expected vs. actual benefits to gain by migrating to PostgreSQL

Reduce cost

Easy to use

Improve stability

Gain deployment flexibility

Strong community

Eliminate lock-in

Support developers innovation

Reduce licensing complexity

Be free of Oracle license audits

Leverage a feature- rich platform

Expected Actual

© 2019 Stratoscale 11

Average Annual Oracle Database Costs Before Migration (License + Maintenance)

We asked both survey groups what their average annual costs were for their Oracle databases including license and maintenance costs. The group planning to migrate (“Before”) reported on their current costs, the group that had already migrated (“After”) reported on their costs before starting their migration.

With cost reduction being the top benefit of an Oracle to PostgreSQL migration and the #2 driver it comes as no surprise that those who already migrated previously had significantly higher annual Oracle costs, compared to those who are “a step behind” – the companies who are still in the planning phase.

The most significant difference can be seen with companies having a spend of $3M or more. This group represents 38% of all respondents.

71% of companies in this group already completed the migration, while 29% were still in the planning phase.

40%

30%

20%

10%

0%

<$100K $100 - $500K

$500K - $1M

$3 - 10M $1 - $3M $10M+

10%

37%

21% 20%

7%4%3%

22%

27%

21%

17%

10%

Figure 5: Average annual Oracle database costs before migration for both the “Before” and “After” groups

Before After

71% of $3M+ group

29% of $3M+ group

© 2019 Stratoscale 12

When comparing expected vs. actual reduction in TCO, most companies are positively surprised with a greater reduction in TCO than expected.

While 57% of companies planning to migrate expect to see a reduction in TCO of at least 20%, in fact, 68% of companies that migrated saw a reduction of 20% or more in their TCO.

There is also a significant difference when examining a 50% reduction in TCO. While 12% of companies planning a migration are expecting to see a TCO reduction of 50% or more, in fact, 19% are see a reduction of this magnitude.

60%

50%

40%

30%

20%

10%

0%

<20% 20%-50%No change in TCO

Over 50%

3%

41%45%

12%

5%

28%

49%

19%

Figure 6: Expected vs. Actual reduction in TCO as a result of migrating from Oracle to PostgreSQL

Reduction in TCO

Expected Actual

© 2019 Stratoscale 13

Estimated vs Actual Time to Complete the Migration to PostgreSQL

From those planning a migration, only 26% expect the migration take 6 months or less. 75% expect the migration to take more than 7 months and 40% expect it to take more than a year.

Most companies are not able to predict the actual time it would take. Only 39% of companies reported the migration took approximately as planned. 30% reported it took less than planned and 32% reported is took more than planned.

40%

30%

20%

10%

0%

50%

40%

30%

20%

10%

0%

<3 months

Significantlyless

(50%-90% less)

3 - 6 month

Less than planned

(Up to 50% less)

Approximatelyas

planned

More thanplanned

(up to 50% more)

Significantlymore

(above 50%more)

7 - 12 months

13 - 18 months

18+ months

24%

35%

39%

26%

26%

14%

6%

2%

15% 15%

Figure 7: Estimated time to complete the migration

Figure 8: Actual vs. estimated time to complete the migration

69% completed the migration as planned or sooner

69% of companies who completed their migration did it within the time estimated or sooner.

© 2019 Stratoscale 14

Planned vs. Actual Downtime During the Migration to PostgreSQL

From those planning a migration, only 14% expect to have less than 2 hours of downtime. 57% expect the migration to cause 6 or more hours of downtime, and 21% expect more than a day of downtime.

Most of companies are not able to predict the actual downtime during migration. Only 34% of companies reported downtime approximately as planned. 31% reported it took less than planned and 34% reported is took more than planned.

40%

30%

20%

10%

0%

40%

30%

20%

10%

0%

None

Significantlyless

(50%-100% less)

Under 2hours

2-6 hours

Less than planned

(Up to 50% less)

Approximatelyas

planned

More thanplanned

(up to 50% more)

Significantlymore

(above 50%more)

Up to a day

Up to two days

More thantwo days

9%

27%

9%

34%

36%

22%

12%

12%

5%

19%12%

Figure 9: Estimated downtime before migration

Figure 10: Actual vs. planned downtime experienced during migration

65% experienced the same or less downtime than planned

65% of companies who completed their migration experienced the same or less downtime than they had planned.

© 2019 Stratoscale 15

Top Expected vs. Actual Challenges in the Migration Process

There are some differences between the top 3 challenges companies expect before migrating, and the ones they report during and after they complete their migration process.

Before migrating, the top three challenges companies anticipate are minimizing downtime, migrating data and reliability. However, once companies have migrated their databases, the extent to which they experienced these challenges was significantly less than expected. Hence, for example, while 50% of the “Before” group selected minimizing downtime as one of the top 3 challenges, putting it in the #1 position, only 36% in the “After” group rated it among the top 3 challenges, pushing it to 4th position.

As a result, in practice, Team/skill set is in third place which is indicative of the challenges companies face due to the need to train and educate their IT teams to support PostgreSQL in their organization.

At the other end of the spectrum, day-two PostgreSQL ops, supporting hybrid cloud and self-service provisioning turned out to be challenging for more companies than expected. This is in line with companies’ eventual strategic decision to consume PostgreSQL as a managed service.

Supporting the use and management of PostgreSQL after migration turned out to be more challenging than expected.

0% 10% 20% 30% 40% 50% 60%

36%

39%

39%

28%

39%

28%

31%

12%

12%

24%

13%

10%

50%

49%

45%

43%

39%

30%

30%

29%

23%

15%

11%

4%

Figure 11: Top expected vs. actual challenges in the migration process

Minimal downtime

Integration risks: migrating data

Reliability

Securing PostgreSQL and compliance

Team / skill set

Integration risks: migrating code

Finding the right migration tool(s)

Implementing automation, DevOps

Managing multiple PostgreSQL clusters

Day-two PostgreSQL ops

Implementing a hybrid approach

Offering self-service provisioning

Expected Actual

© 2019 Stratoscale 16

When migrating from Oracle to PostgreSQL, companies have different options to manage and consume their PostgreSQL databases. We compared companies’ plans before migration with actual implementations after migration.

There are significant gaps between planning and reality. While 42% of companies planning a migration intended to use an enterprise product which includes support, only 29% of companies end up managing and consuming PostgreSQL in this manner representing a drop of 30%. In fact, the majority (63%) of post-migration respondents opted to manage and consume PostgreSQL as a managed service (which is 34% more than those who planned to use a managed service before migrating).

70%

60%

50%

40%

30%

20%

10%

0%

Managed service (on-prem or in the

public cloud)

Enterprise product w /support

DIY

47%42%

12%

63%

29%

9%

Figure 12: Managing & Consuming PostgreSQL – Planned vs Reality

Managing & Consuming PostgreSQL – Planned vs. Reality

Expected Actual

63% Managed service

9% DIY

29% Enterprise product

© 2019 Stratoscale 17

Demographics - Job Responsibility and Seniority

Job Responsibility Seniority

3% Architect

5% DevOps

11% App Dev Manager

11% DB Manager

70% IT

4% VP

5% President / Owner

15% Senior Manager

19% CxO

19%Director

38% Manager

© 2019 Stratoscale 18

Demographics - Industries

Industries

17% Other

3% Energy andUtilities

3% Automotive

3% Automotive

4% Retail/Consumer Services

5% Computer & Network Security

5% Education

6% Banking,Insurance,Financial Services

7% Healthcare

8% Manufacturing

38% IT Technology and Services

© 2019 Stratoscale 19

Stratoscale delivers a software-defined data center platform that enables true IaaS, DBaaS and CaaS in data centers and edge locations. Stratoscale runs on any hardware and is combined with cloud management features such as centralized user access management, self-service portals, integrated metering for showback / chargeback, and more.

In addition, Stratoscale delivers a suite of managed open source platforms for developers to accelerate application development and delivery. By offering public cloud APIs, Stratoscale enables multi-cloud and hybrid applications and supports advanced DevOps and Infrastructure-as-Code in enterprise environments.

For more information please visit us:

www.stratoscale.com US Phone: +1 877 420-3244 | Email: sales@stratoscale.com

About Stratoscale

Schedule a Demo