ERP & Operations

Multi-Branch ERP Migration

Migration from Al-Aseel to ABC ERP across pharmacy operations with rollout and user enablement.

EnvironmentBalsam AlUla Pharmacies
Period2022-2024
RoleIT Manager
LifecycleHistorical / completedHistorical production delivery from the 2022–2024 Balsam AlUla operating period.
Multi-Branch ERP Migration conceptual illustration for ERP & Operations
Conceptual IllustrationGoverned historical migration operating-model visual showing legacy ERP, readiness and validation, target ERP and multi-site rollout context.
Project overview

ERP change delivered across a live multi-site pharmacy environment

The migration moved Balsam pharmacy operations from Al-Aseel to ABC ERP while supporting users, branches and day-to-day continuity across 15 pharmacies, headquarters and five warehouses.

StatusHistorical / completedEnvironmentBalsam AlUla PharmaciesPeriod2022-2024
Context & challenge

The operating need

A multi-site pharmacy environment needed to change its core ERP without separating the software transition from branch readiness, user adoption and normal IT operations.

Role & responsibility

Ahmed's contribution

As IT Manager, Ahmed coordinated the technology transition, branch readiness, user support, infrastructure dependencies and operational follow-through.

Solution

How the work was approached

Environment: Balsam AlUla operations covering 15 pharmacies, headquarters and five warehouses.

The transition combined ERP rollout with practical multi-site readiness, user enablement and ongoing technology support rather than treating migration as a single cutover event.

Execution highlights

  • Coordinated migration activity across the pharmacy operating footprint.
  • Supported users through the change in daily ERP workflows.
  • Kept branch connectivity, endpoint, security and support responsibilities aligned with the ERP transition.
Security & operational controls

Designed for responsible operation

  • Public material describes the operating model without publishing ERP credentials, business data or private branch configuration.
  • Historical technologies are labeled as historical production rather than current-stack claims.
  • The case study avoids unsupported financial or productivity claims.
Key decisions

Choices that supported the outcome

  • Treat branch and user readiness as part of the ERP migration scope.
  • Maintain day-to-day IT support while the new platform was introduced.
  • Preserve historical context without presenting legacy ERP platforms as current technologies.
Lessons

What the work reinforced

  • ERP migration in multi-site retail is an operating change, not only a software deployment.
  • User adoption and branch readiness can determine whether a technically complete rollout succeeds operationally.
  • Technology leadership during migration requires coordination across systems, users, vendors and daily support.

Technology

Technology used in this work

The stack and platforms associated with this project.

ABC ERPhistorical production
Al-Aseel ERPhistorical production
About the project visuals

Governed historical migration operating-model visual showing legacy ERP, readiness and validation, target ERP and multi-site rollout context.

The visual is not presented as a production ERP screenshot. Business data, credentials, branch configuration and private operational records are intentionally excluded.

Solution architecture

How the solution is structured.

The major functional layers and how they work together.

01

Legacy operating model

Al-Aseel ERP supported the earlier pharmacy operating environment before the transition.

02

Migration & readiness

Data, users, workflows and branch readiness were coordinated for the move to the replacement platform.

03

ABC ERP rollout

The new ERP was introduced across the operating environment with user and branch support.

04

Multi-site operations

Pharmacies, headquarters and warehouses continued under the broader IT operating and support model.

Operational footprint

Scale and operating impact.

Selected metrics and characteristics that show the practical scope of the implementation.

15

pharmacies

Multi-site operating environment

5

warehouses

Plus headquarters operations

Core capabilities

What the solution enables.

The capabilities that make the project useful in day-to-day operations.

Migration coordination

ERP transition activities were coordinated around live pharmacy operations rather than treated as a standalone software install.

Multi-site rollout

Deployment and support covered pharmacies, headquarters and warehouse operations across the Balsam environment.

User enablement

Users were supported through the operational change so the new ERP could be adopted in daily work.

Operational continuity

IT management balanced migration activity with branch support, connectivity, security and day-to-day service continuity.

Copied