Magaya-käyttöönoton tarkistuslista jonka käymme läpi ennen tuotantoa

A Magaya rollout rarely fails because of the platform. It fails because the operation was never mapped properly before configuration started, and the gaps only surface once real shipments are moving.

Over repeated implementations across the Nordics and wider Europe, the same sequence keeps producing clean go-lives. It is deliberately front-loaded: the slow, unglamorous discovery work happens before anyone touches a configuration screen.

1. Map the workflow you actually run

Not the one in the process document. We sit with operations and trace a real shipment end to end: quote, booking, documentation, customs, invoicing, and the handoffs in between. Every manual workaround gets written down, because each one is either a configuration requirement or a process to retire.

2. Inventory the surrounding systems

Magaya is rarely the only system in the building. Accounting, ERP, carrier portals, customer spreadsheets, and reporting tools all touch the same data. Before configuration, we list every integration point and decide which are day-one requirements and which are phase two.

3. Decide the module scope honestly

The platform covers supply chain, the freight portal, rate management, customs compliance, WMS, and CRM. Very few operations need all of it immediately. Scoping to what the team will genuinely use in the first six months keeps the project shippable and the quote defensible.

4. Configure against the map, not the demo

Configuration follows the workflow map produced in step one. This is where the earlier discovery pays for itself: decisions are already made, so configuration becomes execution rather than a series of open questions.

5. Migrate data early and test it twice

Customer records, rate tables, and open shipments move well before go-live, so there is time to find the problems. A migration validated a week out is a very different experience from one validated the night before.

6. Train on live scenarios

Generic training does not stick. We train each role on the shipments they will actually process, using migrated data, so the first live day is a repeat of something the team has already done.

7. Stay on hand for the first live week

Go-live is not a handover. A dedicated contact stays available through the first week of real traffic, because that is when the remaining edge cases appear, and they are far cheaper to fix while the project team is still assembled.

None of this is exotic. It is simply ordered so the expensive discoveries happen when they are still cheap.