Migrating custom functionality from SAP Commerce Product Cockpit to Backoffice PCMT
3 Backend Developers, 1 Team Lead, Quality Assurance Engineer, Business Analyst, Project Manager
SAP Commerce Cloud (Hybris), Angular, Solr, Spring, Java, Microsoft SQL Server
Challenge
SAP Commerce Cloud (Hybris) released a new version, deprecating support for the client’s existing version. This posed a challenge for the client, as the Product Cockpit (PC) used for catalog and product management was no longer supported. The new Backoffice PCMT (Product Content Management Tool) introduced structural changes, requiring a full migration of custom functionalities.
The key challenges includes:
- Feature Compatibility – Many customized features in Product Cockpit were not available in Backoffice PCMT.
- Process Optimization – The client’s workflows were built around the legacy system, requiring process adjustments.
- Business Continuity – The migration had to be seamless with minimal downtime and zero disruption to ongoing operations.
Feature gap analysis & Process optimization
Objective: Identify gaps between the old and new systems while streamlining processes.
- Conducted a full audit of the client’s customized Product Cockpit features and compared them against native capabilities of Backoffice PCMT.
- Identified deprecated features, missing functionalities, and new opportunities within the updated system.
- Collaborated with business stakeholders to reassess existing workflows, eliminating redundant steps (e.g., simplifying promotions setup, catalog, and product management).
- Provided recommendations on adapting to Backoffice PCMT and outlined necessary customizations to maintain operational efficiency.
Development & Migration strategy
Objective: Migrate essential features while ensuring full compatibility and scalability.
- Developed a prioritized migration roadmap, focusing on:
- Critical functionalities (e.g., product enrichment, attribute management, promotions, versioning).
- High-impact automation for catalog workflows.
- User access and permission management to align with Backoffice PCMT structure.
- Re-implemented key customizations, ensuring they were compatible with the new architecture.
- Built custom extensions where the new system lacked native features to replicate legacy behaviors.
- Refactored existing integrations to align with Backoffice PCMT’s data model and API structure.
Testing & Validation
Objective: Ensure a smooth transition with zero operational downtime.
- Developed comprehensive test cases for functional, integration, and user acceptance testing (UAT).
- Conducted parallel runs where both Product Cockpit and Backoffice PCMT operated simultaneously to validate accuracy.
- Engaged end-users early in the testing phase to gather feedback and refine UI/UX adjustments.
- Ensured data consistency and backward compatibility during the migration process.
Deployment & Rollout
Objective: Deliver a seamless go-live experience with minimized risk.
- Implemented a rollback strategy to mitigate potential risks.
Provided onboarding sessions and user training to ensure smooth adoption of Backoffice PCMT.
Results
100% successful migration of all essential functionalities to Backoffice PCMT.
40% reduction in manual catalog management tasks due to workflow optimization and additional integrations.
Enhanced performance & UI experience, leading to faster product setup and approvals.
Zero downtime & seamless transition, ensuring business continuity without disruption.
Other Case Studies
With the Right Software, Great Things Can Happen
QA Audit for EMEA bank
Facet Search for E-Commerce
Voice Interface for Warehouse Employers
Warehouse Management APP
POS Check Constructor
Temperature Monitoring System for Warehoses
HR Helper Bot
Flexible work formats
For convenience we offer several standard models of work with our clients.
Time and material
Model works best when you don’t have a clear scope and want to be deeply involved in the development process.
Choose it if:
- you want to follow agile methodologies
- you need to be flexible due to quickly changing requirements and taste hypothesis time to time.
- you don’t have strict deadlines
All of that doesn’t mean you go in blind. Just like in the fixed-price model, you start your cooperation with planning, but only for the upcoming week or two. So instead of determining and fixing requirements for the whole project, you start fast and can further adjust the scope and priorities.
Fixed-capacity
This model focuses on ensuring the efficiency and velocity of the team. To achieve this, the supplier must ensure that different skill sets of members are assigned to a development squad to effectively deliver the project.
Choose it if:
- you want to follow agile methodologies
- you would like to have a fixed budget for a certain period, but don't have a clear idea on the defined scope of work or specifications
- you understand further support steps and define continued predictable costs
We need to work with the client to clarify the scope of work and prioritize the backlogs before the next iteration starts. As the project progresses, it allows the client to mold the project along the way to take advantage of newly released features.
Fixed-price
Model works best when you don’t have a clear scope and want to be deeply involved in the development process.
Choose it if:
- you want to follow agile methodologies
- you need to be flexible due to quickly changing requirements and taste hypothesis time to time.
- you don’t have strict deadlines
All of that doesn’t mean you go in blind. Just like in the fixed-price model, you start your cooperation with planning, but only for the upcoming week or two. So instead of determining and fixing requirements for the whole project, you start fast and can further adjust the scope and priorities.
The discount is applied annually for a period of 6 months.
We provide discount system for long-term cooperation customers. If the threshold is reached for the sum of all orders from one customer, a discount applies to all new subsequent projects.
