top of page

Insights

Moving Infor LN to the Cloud: A Practical Checklist for CSIE

A practical checklist for Malaysian manufacturers and distributors moving from on-premise Infor LN to Infor CloudSuite Industrial Enterprise (CSIE).

By Rick Loh, CEO, NW Solutions (M) Sdn Bhd

Many Malaysian manufacturers and distributors have run Infor LN on their own servers for years. It works, people know it, and the reports everyone relies on are built around it. Then the questions start: the server is due for replacement, the version is several releases behind, and it is getting harder to find people who can maintain both the hardware and the old customisations.

Infor CloudSuite Industrial Enterprise (CSIE) is the cloud edition of Infor LN. Moving to it is less about learning a new system and more about changing how your LN is run, extended and connected. This checklist covers what to sort out before, during and after the move.

What changes when LN moves to the cloud

In CSIE, Infor runs the infrastructure and delivers updates to the application. Your team no longer patches servers or plans large version upgrades every few years. In exchange, a few things work differently:

  • No changes to standard source code. Tailoring in the multi-tenant cloud is done through Infor's extensibility tools and personalisations, not by modifying LN itself.

  • Integrations go through Infor ION. Direct database links and file drops are replaced by ION and Infor's APIs.

  • Regular updates. New functionality arrives on Infor's schedule, so testing becomes a routine habit rather than a once-a-decade project.

None of this is a reason to delay. It simply means the preparation is different from a normal upgrade.

Before the move: know what you have

1. List every customisation. Go through modified sessions, custom reports, scripts and add-on tables. For each one, ask a simple question: is this still needed? Many customisations were built for a process that has since changed, or for a gap that standard LN now covers.

2. Sort what stays into three groups.

  • Covered by standard functionality in the current LN release, so it can be retired.

  • Still needed and can be rebuilt with cloud extensibility tools.

  • No longer needed, so it can be dropped with a short process change.

3. Map your integrations. Write down every system LN talks to: e-invoicing, banking, shop floor equipment, label printers, customer and supplier portals, spreadsheets that are uploaded each month. Note how each one connects today and who owns it. Each will need a route through ION or an API in the cloud.

4. Check your reports. Find out which reports people actually open. Old reports that nobody reads are a good thing to leave behind.

Clean the data before you move it

Moving to the cloud is the best chance you will get to fix data problems, because it is far easier to clean data before it is loaded than after.

  • Retire obsolete items, customers, suppliers and warehouse locations.

  • Check units of measure and conversion factors on active items.

  • Close or cancel old open orders that will never be completed.

  • Decide how much transaction history to bring across and how the rest will be archived and accessed.

  • Agree who signs off each data area: items, bills of material, routings, open orders, balances.

Plan at least one full trial load and reconcile it: inventory value, open purchase and sales orders, work in process and general ledger balances. A good rehearsal is what makes go-live weekend calm.

Do not forget the compliance links

If your on-premise LN already connects to MyInvois for e-invoicing, treat that link as a priority integration. Test submission, validation responses and cancellations in the new environment before go-live, and make sure finance knows who to call if a document is rejected in the first weeks. The same applies to any tax reports or statutory files your team produces from LN today.

Plan for the people side

The screens and the core processes will feel familiar to LN users, which helps. Even so:

  1. Name process owners in finance, purchasing, production and warehouse who will test and sign off.

  2. Write test scripts from real work, such as a full order to cash cycle and a month-end close, not just single screens.

  3. Set up a test routine for updates, so each new release is checked against your key processes.

  4. Keep the mobile and warehouse tools in scope. If you use NWSM Barcode or Insight, our Android app for Infor LN, include receiving, issue, production reporting and shipment scans in your test cycles so the warehouse does not discover a gap on day one.

After go-live: use what the cloud gives you

Once the system is stable, review the list of customisations you rebuilt. Some may now be covered by new standard features delivered in later updates. Look again at reports and dashboards, and at manual steps that could be handled through ION workflows. The move is not the end of the project. It is the start of a system that keeps improving without another big upgrade.

Talk to us

If you run Infor LN on-premise and are weighing up a move to CSIE, NWSM can sit down with your team, review your customisations and integrations, and help you build a realistic plan before any commitment is made. Contact NWSM at inquiry@nwsm.com or +603 7713 5388.

Connect with us.  

NW Solutions (M) Sdn Bhd

Address

Suite UG08 Emerald Plaza East, Lot 6, Jalan PJU 8/3, Damansara Perdana, Selangor 47820 Malaysia

Email

Tel

+603 7713 5388

Rights reserved 2026 by NW Solutions (M) Sdn Bhd

Thanks for submitting!

  • Facebook
  • LinkedIn
bottom of page