In many plants the need for ERP shows up the same way: stock in one file, open projects in another, purchase requests in email. Each file is tidy on its own; the trouble starts when information moves between them. This article walks through how an Excel-run firm can plan an ERP move without stopping production. If you want the concept first, see our What is ERP? guide.
1. List the files people actually use
Start day one with an inventory, not software: which files does the team open every day, and who updates them? You usually get three core lists:
- Stock list: material code, grade, size, quantity, bin.
- Project list: customer, deadline, owner, status.
- Supplier and account list: company name, contact, terms.
If those three are clean, half the migration is done. Merge rows where the same material was typed two ways (e.g. “S355 plate 10mm” and “Plate S355JR 10”).
2. Define stock types for your materials
The single “description” column in Excel must become separate fields in ERP. Plate needs length, width and thickness; pipe needs diameter and wall; welding wire needs diameter and kilograms. That is why stock tracking in İnsya ERP starts with stock types: each type brings its own fields and the list filters by them.
3. Migrate open work; leave closed jobs in the archive
Trying to import five years of every project stretches the go-live for months. Bring open projects and open quotes into ERP; closed jobs can stay in an Excel archive. When project tracking starts with live work, the team uses the system from week one.
4. Tie purchasing to stock
The first concrete win is often in purchasing: if material reserved for a project already sits in stock, you do not order it again. When request, PO, goods receipt and incoming inspection run as one flow, the “did it arrive?” emails between warehouse and purchasing stop. See purchasing.
5. Keep permissions simple at first
Giving everyone everything — or locking everything — on day one both backfire. Start by department: warehouse sees stock and receipt, purchasing sees orders, the project team sees projects and quotes. Role detail can come later.
6. Introduce the team to the UI
İnsya ERP’s windowed desktop uses windows, a taskbar and search from one box. Still, run a short intro in week one and show the Ctrl+K command palette — the fastest way to find a record. Tour the desktop UI.
Regional differences
Pace depends on plant scale. On large sites with many people, permissions and audit trails matter more; at SME scale, fewer clicks matter more. For region-specific notes in Turkish, see our Tekirdağ, Kocaeli and Bursa ERP pages.