(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.data-privacy-src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-79651946-1', 'auto'); ga('send', 'pageview');

Project Description


Migration and upgrade from SAP BW 7.4 local to SAP BW 7.5
on HANA on AWS




Funeral services, funeral parlors, crematories and cemeteries management.


Funeral industry


Migration and upgrade from SAP BW 7.4 local to SAP BW 7.5 on HANA on AWS

Products y services


“Thanks to 3Hold, a migration expected to be complex was performed quickly and easily, providing business continuity in a flexible way.”

Albert Auset

CIO, Mémora

The client

Mémora is the leading group of funeral services, funeral parlors, crematories and cemeteries management in the Iberian Peninsula. In recent years, Mémora has won numerous public tenders for the construction and subsequent operation of funeral parlors, crematories and cemeteries.

Company Data:

  • 1,200 professionals
  • 125 funeral parlors
  • 26 crematories
  • 23 cemeteries
  • 130 recruitment offices
  • Turnover: 153 million

Mémora is present in 21 Spanish provinces thanks to the continuous investment effort made in recent years that has focused on the construction of new facilities, the acquisition of funeral parlors and the remodeling of facilities.

In addition, the Mémora Group participates in Servilusa, in Portugal, where it is also a leader in the sector with a market share of 5.5%, has a team of 300 workers and performs more than 5,500 services a year.

Since July 2017 Mémora belongs to the Ontario Teachers’ Pension Plan (OTTP), a Canadian pension fund.

Previous Situation

The increased complexity of Mémora’s reporting creation processes —mainly due to its latest acquisitions and growth in recent years— made it essential for Mémora to adapt its SAP BW platform and provide it with new functionalities, as well as greater speed in the management and processing of information.
It is then when they consider the possibility of upgrading their SAP BW from version 7.4 to version 7.5 and the migration of the Microsoft SQL Server database to SAP HANA.

This upgrade required new certified infrastructures for HANA, but Mémora was immersed in a project to renovate its data center, which made it difficult to add new environments at that time. On the other hand, the management required to have all the management reports as soon as possible in order to continue making decisions based on quality data at the right time.

The Challenge

The main challenge of the project was to have the new SAP BW 7.5 on HANA with the customer data in less than 2 months, also ensuring that the system met the high standards of security, stability and performance required by Mémora.

This new infrastructure in AWS had to be a network extension of their corporate network to be able to interconnect the new SAP BW with its source systems (SAP ERP, mainly) located in its data center and, in turn, that the users of all the Mémora offices could access to the new system in a transparent way.


A VPC and all the basic infrastructure for the new SAP BW 7.5 system was created, including private and public subnets, NAT Gateway, Security Groups, IAM accounts, etc.

To perform the migration from the customer’s data center, an exact copy of SAP BW 7.4 on AWS was created, and then the upgrade to version 7.5 was performed, while the database was changed to HANA using the SAP SUM with Database Migration Option (DMO) procedure.

To create the SAP transport layer between development and production instances, the Elastic File System (EFS) was used to simultaneously access a shared file system using a traditional file permissions model, file locking capabilities, and hierarchical directory structure via the NFS v4 protocol.

The instance for the primary application server (PAS), together with the central services (ASCS), was deployed in an Auto Scaling group across two Availability Zones, with a maximum and minimum of one active instance. This way, the AWS platform itself will monitor that there is only one active instance in any of the availability zones included in the group.

To control this possible movement of instances between availability zones, the Route 53 (DNS) service was used, resolving by name the active instance.
Finally, we used for SAP backups, a low-cost, throughput optimized EBS volume (st1) designed for frequently accessed, throughput-intensive workloads. Moreover, from time to time, database backups and its logs are transferred to S3 buckets in order to reduce their storage cost.

The scope of the SAP solutions included the migration, updating and configuration of a landscape composed of two environments (development and production) of the following SAP products:

• Two EC2 instances for SAP BW 7.5 on Windows Server and two EC2 instances for the HANA database on Suse Linux Enterprise Server

In addition to SAP environments, the following infrastructure was provisioned:

• An EC2 instance on Windows Server for HANA Studio which enables technical users to manage the SAP HANA database, to create and manage user authorizations, and to create new, or modify, existing data models in the SAP HANA database.


Are you facing similiar challenges?

We help you to design solutions that adapt to your business´needs

Name (required)



Email (required)


Subject (requerido)

Do you have an imminent project?
Noin one monthin three monthsin six monthsin one yearmore than a year

Project Type:
CloudSAPCloud & SAPIoTBig DataB2BB2C

Message (required)

I´ve read and accept the Privacy Policy