When a specialty pharmaceutical company acquired a complementary product line, it gained more than new revenue. It also inherited a second accounting system, a third-party logistics arrangement with its own inventory records, and a finance team that was suddenly reconciling three sources of truth every month.

With a board meeting on the calendar and an audit to follow, the company set an ambitious goal: bring the entire business onto a single cloud ERP in less than six months.

The starting point

Before the program began, the company’s operations looked much like those of many fast-growing life sciences businesses:

  • Two general ledgers with different charts of accounts
  • Inventory and batch data held by a logistics partner and updated weekly
  • Manual consolidation in spreadsheets, taking up to fifteen working days per close
  • Little visibility into product margins by market and channel

None of these tools was designed to support a regulated, multi-entity business at scale.

Designing for speed

Speed was a requirement, but so was compliance. The program team, led jointly by the company’s finance director and Oraya®, agreed on a few principles at the outset:

  1. Standard first. SAP Cloud ERP best practices would be adopted wherever possible, with any deviation approved by a small steering group.
  2. One chart of accounts. Harmonizing financial structures was treated as a business decision and settled in the first two weeks.
  3. Integrate, don’t replicate. Rather than rebuild the logistics partner’s warehouse functions, the team set up a standard daily integration for stock, batch and shipment data.
  4. Validation in parallel. Validation documentation was produced alongside configuration and testing rather than at the end.

Five months, four phases

The program followed a structured plan:

  • Prepare (weeks 1–3): governance, scope confirmation and data ownership agreed
  • Explore (weeks 4–8): fit-to-standard workshops covering finance, procurement, sales and inventory
  • Realize (weeks 9–17): configuration, integrations, data migration rehearsals and testing
  • Deploy (weeks 18–21): training, cutover and hypercare

Weekly steering meetings kept decisions moving, and a shared issue log gave everyone the same view of progress. When a gap surfaced in the handling of returned goods, the team resolved it with standard functionality and a small workflow change instead of custom code — keeping the plan intact.

Protecting the business during cutover

With product shipping to pharmacies and distributors every day, there was no room for a pause in fulfillment. The team scheduled cutover over a month-end weekend, froze master data changes two weeks in advance and ran a final reconciliation of open orders, batches and balances before switching over. A small command center of finance, supply chain and IT staff stayed on call through the first two weeks of hypercare, resolving questions the same day they were raised.

Training followed the same practical approach. Rather than generic system courses, each team rehearsed its own day-in-the-life scenarios using migrated data, so the first live transactions felt familiar.

Results

The company went live on schedule and closed its first quarter on the new platform without a single late entry. Within the first six months:

  • The monthly close dropped from fifteen days to six
  • Batch and expiry information became available daily instead of weekly
  • Product margin reporting by market was available on demand for the first time
  • The annual audit required far less preparation time

“We expected the project to be hard,” the finance director said. “What surprised us was how quickly people adapted once there was one system everyone trusted.”

What made the difference

Looking back, three factors stood out. First, leadership made decisions quickly and stood behind them. Second, the scope was kept deliberately focused, with further capabilities planned for later waves. Third, the company chose a partner with experience in regulated industries, so compliance was built in rather than bolted on.

These principles apply well beyond pharma. Our article on building a cloud mindset explores the habits that help any organization get value from cloud ERP faster.

Considering a consolidation of your own? Contact us to discuss your timeline.