
How We Migrated a Seven-Year-Old WMS for a Multi-Site Operator
The warehouse system is seven years old and older than half the team. Data leaves it through manual SQL exports, and every new rule waits weeks. Receiving and shipping never stop, so the upgrade moves to next year again. In the words of the client's IT lead, someone has to pull the data out by hand through SQL. Hygge moved the WMS to Java services and PostgreSQL and kept the business rules and the data. It adds scanners, quality holds, FIFO and labels, and opens the warehouse to other systems through a REST API. API calls answer within 300 ms, and screens load within one second.





Is Your WMS Older Than Half Your Team?
Bring the list of modules your warehouse runs on to a 30-minute call with a Hygge architect. You leave with the order a migration would follow and what each step would replace.
Why the WMS Upgrade Keeps Slipping
The system works, everyone depends on it, and switching it off is the risk.
Data Pulled Out by Hand Through SQL
Reports and exchanges with the ERP depend on someone exporting data from the old database.
Every Change Waits Weeks
A new rule, document or label format sits in a queue for the few people who still know the stack.
The Warehouse Can Never Stop
Receiving and shipping run every day, so a big-bang switch is impossible. The upgrade moves to next year again.
Labels and CMRs Done Outside the System
Documents and labels get made in spreadsheets or fixed by hand at the dock.
Rules That Live in Two People's Heads
Years of warehouse logic sit in code and memory with little documentation. Losing one person stalls everything.
The Challenge
The operator's WMS ran receiving, storage, production supply and shipping across several sites. It ran for seven years on Oracle and an aging stack. Every change took weeks, and data reached other systems through manual exports. The warehouse had to keep running throughout. So the migration had to protect the business rules and the data the floor relies on every shift.
Keep years of warehouse logic and data, and put them on a stack that changes in days.
Our Solution
Hygge built Java services with PostgreSQL and Redis. The schema moves from Oracle with versioned scripts. A React web app runs on scanners in English, Hungarian and Chinese. Sign-in supports two-factor and hardware keys, and ten roles control who sees what. The modules follow the goods. ASN receiving comes with supplier time slots and putaway. Quality control has non-conformance reports, and FIFO allocation skips held batches. Then come material issue to production, CMRs and loading lists, Zebra labels with QR codes, and stock counts. A REST API with webhooks and more than thirty email triggers replaces the manual exports.
A modern WMS on Java and PostgreSQL, moved the way Hygge moves live systems: in stages, with data checked before each switch.
How the WMS Migration Solves It
Each module answers one of the reasons above.
Data Out Through an API
A documented REST API with webhooks sends receipts, stock and shipments to the ERP. The manual SQL exports retire.
Changes in Days on a Modern Stack
Java services, PostgreSQL and a React front end that any current engineering team can extend.
Receiving by Scan
ASNs from the supplier portal, booked time slots, scan-based receipt and putaway suggestions by zone and capacity.
Quality Holds That Stop Bad Stock
A damaged or failed batch goes on hold with its NCR. FIFO allocation skips it until quality releases it.
Documents and Labels in the System
CMRs, loading and picking lists and labels with QR codes print straight to Zebra printers.
Scanners in Three Languages
The same app runs on handheld scanners in English, Hungarian and Chinese, with ten roles and two-factor sign-in.
What Runs Without Anyone Pressing a Button
The warehouse rules the new WMS applies on every transaction.
Oldest Stock First
Outbound allocation takes batches in FIFO order and skips anything on a quality hold.
Damaged Goods Held
A damage flagged at receipt sends the batch to quality control with photos and notes.
Capacity Respected
Putaway suggestions follow the zone capacity limits set for each warehouse.
People Informed
Receipts, damages and holds trigger email notices and webhooks to connected systems.
What the New WMS Gives the Warehouse
What the new WMS gives the floor and the systems around it every shift.
API Response Time
Page Load on the Floor
On Handheld Scanners
With Role-Based Access
The Services Behind the WMS Migration
How the Migration Moved, Module by Module
Foundation and Data
Access and Master Data
Inbound and Quality
Outbound and Production
Documents, Labels and Stocktake
Industries We Serve
Industries where a warehouse system runs every shift and the upgrade cannot wait for a quiet week.
Logistics & Warehouse Automation
Operator interfaces for autonomous fleets, industrial integration and systems rebuilt without taking a working site offline.
Retail & E-Commerce
Recommendation engines, retail media platforms and the billing accuracy that decides whether store partners stay.
Solutions Behind the New WMS
The Hygge solutions this build draws on.
Warehouse Management System Development
A WMS on Java and PostgreSQL with receiving, quality holds, FIFO and labels.
Inventory & Fleet Management Software
Stock, batches and pallets tracked by scan across sites.
ERP Development
A REST API with webhooks sends receipts, stock and shipments to the ERP.
More Products Hygge Has Shipped
Other systems Hygge built around the way a team already works.
WMS Migration: Questions Buyers Ask
Do we have to stop the warehouse for the switch?
Will our data and rules survive the move?
Can the floor use it on our scanners?
How do other systems get warehouse data?
What did the client get at handover?
Let's Build Something That Matters
We're your one-stop Digital Engineering Partner. Tell us the process, product, or data problem you're trying to solve, and Hygge scopes AI and software work around the business result you need.
Tell Us What You're Building
Share the product, process, or data problem behind the request, along with the systems, data, or timeline the build has to work around.
Get an Audit-Backed Consultation
Hygge reviews the systems and data behind the request, so the first call opens with real specifics on the table.
Receive a Scoped Proposal
A plan with the approach, team, timeline, and cost, built around the business result the project needs to hit.





















