PLC programming, machine-specific training software, process improvement and PLC cleanup, custom applications, ERP connectors and data migration, from a controls engineer with 30 years on the plant floor. Remote work, or on site by arrangement.
New logic, upgrades and migrations, written in clear, documented ladder.
Windows and web tools built around how your plant actually works, plus custom test fixtures with the validation software to prove every part.
Get production data into your ERP, and orders out to the floor, without retyping.
Move years of data, or keep two systems in step, reliably, including from one ERP brand to another.
Interactive training built around your exact machine, so operators and maintenance techs learn on the equipment they actually run, not a generic example.
Make an existing line run better, and leave its program clean, documented and easy for the next person to maintain.
Changing systems? We script the move of your items, bills of materials, customers, vendors, open orders and balances from one brand to another — into Microsoft Dynamics 365, Acumatica, NetSuite, Epicor or whichever system you're moving to, in either direction. Business Central is only our most common example. Every run is checked, logged and reversible.
| From | To | What typically moves | How we connect |
|---|---|---|---|
| Oracle Agile PLM | Business Central | Item masters, multi-level BOMs, revisions, approved manufacturers, change history, attachments | Agile export files or the Agile SDK and web services, into the Business Central API and configuration packages |
| Dynamics GP, NAV or SL | Business Central | Master data, open documents, balances, plus the extra tables Microsoft's own migration tools leave behind | Microsoft's cloud migration, with our scripts for the remainder |
| QuickBooks Desktop or Online | Business Central or Acumatica | Customers, vendors, items, chart of accounts, open invoices and bills, opening balances | QuickBooks exports or the QuickBooks Online API, into the target's API |
| Sage 100 or Sage 300 | Business Central, Acumatica or NetSuite | Masters, open orders, inventory quantities and costs, history | Read-only ODBC or report exports, into the target's API or import templates |
| SAP Business One | Business Central or NetSuite, and back | Business partners, items, BOMs, price lists, open documents | SAP Service Layer or DI API, both directions |
| Epicor Kinetic | Business Central, and back | Parts, BOMs and routings, customers, vendors, open jobs and orders | Epicor REST API, both directions |
| Infor SyteLine (CloudSuite Industrial) | Business Central, and back | Items, current BOMs and routings, customers, vendors, open orders | SyteLine IDO web services, both directions |
| NetSuite | Business Central, and back | Records, transactions and saved-search history | SuiteTalk REST or SOAP, CSV import and saved searches |
| Odoo | Business Central or Acumatica, and back | Products, BOMs, partners, sales and purchase orders | Odoo external API (XML-RPC / JSON-RPC) |
| Exact Macola (ES, 10 or Progression) | Business Central, Acumatica or NetSuite | Customers, vendors, items and BOMs, open sales and purchase orders, inventory quantities and costs, GL accounts and open balances | Read-only SQL / ODBC (Macola ES and 10 run on Microsoft SQL Server; older Progression on Pervasive PSQL) or Macola exports, into the target's API or import templates |
| Arena PLM or SOLIDWORKS PDM | Business Central, Epicor or NetSuite | Released parts and BOMs, kept in step as engineering changes are released | PLM/PDM exports or APIs, as a scheduled one-way sync |
| Excel, Access or an in-house SQL database | Any of the above | Whatever you've been keeping by hand | Cleaned, de-duplicated and mapped, then loaded through the target's API |
Your combination isn't listed? If both systems can export data and the target has an API or import template, it can almost always be scripted. Ask.
We migrate to (and from) any of these: Microsoft Dynamics 365 Business Central and Finance & Operations, Acumatica, NetSuite, SAP Business One, Epicor Kinetic, Infor CloudSuite / SyteLine, Sage (Intacct, 100, 300, X3), Odoo, QuickBooks and Exact Macola — plus PLM/PDM, MES / CMMS, historians, and plain SQL, Excel or Access databases.
Run the old and new systems side by side during cutover. A cross-reference table maps every old ID to its new one, changes are picked up by date stamp, and clear rules decide which side wins a conflict.
A dry run goes into a test company first. Each live load writes a ledger of every record it created or changed, with a snapshot taken before it starts, so a failed load can be undone record by record. Posted accounting entries can't be deleted in any ERP, so those are reversed with matching entries instead, and moved as opening balances where possible.
Data is read the way a normal user can: reports, saved searches, Excel and CSV exports, or read-only ODBC. Loading uses the target's own import templates. Where a step truly needs an administrator, such as a one-time API user in the new system, you get one file and one instruction to hand them.
Typical figures for planning, not guarantees — confirmed after we see your data.
We ran four migrations through our ETL model, spanning small to very large data sets (about 15,000 to 177,000 records). These are predicted figures to show the shape of a project — your actual results vary from one system to the next with data quality, volume and customization, and your data may fall anywhere on or beyond this range.
| Example migration | Data size | Clean (1st pass → final) | Flagged to review | Timeline | Your team |
|---|---|---|---|---|---|
| QuickBooks Online → Dynamics 365 Business Central | Small · 15,170 records | 97.0% → 99.8% | 453 | 2–3 wks | ~28 hrs |
| Sage 100 → Acumatica | Medium · 74,450 records | 96.1% → 99.8% | 2,873 | 3–5 wks | ~40 hrs |
| Exact Macola ES → NetSuite | Large · 105,570 records | 96.0% → 99.9% | 4,240 | 4–6 wks | ~45 hrs |
| Epicor Kinetic → Dynamics 365 Business Central | Very large · 176,700 records | 95.9% → 99.8% | 7,182 | 5–9 wks | ~53 hrs |
Simulated on representative data sets from small to very large — a prediction, not a guarantee. The four sizes above are reference points only; your real counts, rates and timeline depend on your own systems. “Flagged to review” records are corrected and reloaded, which is what carries the first-pass figure up to the final.
Pick your current ERP, where you're headed and a rough data size, and we'll predict the shape of the migration. It's a model estimate — your real numbers depend on your own data and customization.
Two very different jobs wear the same name. Same-family upgrades (Rockwell legacy to Logix) are largely automated. Cross-brand conversions (one maker to another) are engineered re-writes, helped by tooling but never push-button. We do both — and we tell you honestly which one you have before you spend a dollar.
RSLogix 500 (SLC 500 / MicroLogix) and RSLogix 5 (PLC-5) to Studio 5000. A converter maps the N, B, T, C and F files to Logix tags and rebuilds the routines; we then clean up, document and validate against the real I/O.
Allen-Bradley, Siemens, Mitsubishi and AutomationDirect (CLICK PLUS / Productivity), in any direction. There is no honest one-click converter between brands — instruction sets, addressing, data types and analog/PID/motion all differ — so we extract your I/O list, tag map and logic structure, then re-implement it natively on the target and test it.
A working, documented program on the new platform, an I/O and tag cross-reference, a conversion report of every mapped and re-worked rung, and commissioning support. Your old program stays the live one until you sign off.
| From | To | How | Typical effort |
|---|---|---|---|
| RSLogix 500 (SLC 500, MicroLogix) | Studio 5000 (CompactLogix / ControlLogix) | Automated convert + engineered cleanup | Low – medium |
| RSLogix 5 (PLC-5) | Studio 5000 | Automated convert + cleanup | Low – medium |
| Allen-Bradley (any) | Siemens TIA Portal | Assisted re-engineering | Medium – high |
| Allen-Bradley (any) | AutomationDirect Productivity or CLICK PLUS | Assisted re-engineering | Medium |
| Siemens TIA Portal / Step 7 | Allen-Bradley Studio 5000 | Assisted re-engineering | Medium – high |
| Mitsubishi (GX Works) | Allen-Bradley, Siemens or AutomationDirect | Assisted re-engineering | Medium – high |
| Any brand | Any brand — your combination | Assisted re-engineering | By size & complexity |
Your combination isn't listed? If we can read the source program (file or PDF), we can scope it. Ask.
Same-family — RSLogix 500 / PLC-5 → Studio 5000:
Cross-brand — re-engineered to a new maker:
Typical figures for planning, not guarantees — confirmed after we review the program.
Cross-brand cost tracks program size and complexity, not the brand pair, so we price by size. Same-family (Rockwell legacy → Logix) is converter-assisted and runs at the low end. Final price is confirmed after we review the program file.
Suggested prices for planning, in US dollars — confirmed after we see the program. Send your .RSS / .ACD / .ap / TIA / GX file (or a PDF of the logic) and we'll scope it. Ask about a conversion.
Before any project starts you get an itemized scope of work. Every line says who does what, so management knows exactly which work is ours and which needs other contractors, and in what order.
Scopes and budgets are estimates based on the information provided and are confirmed after a site visit or review of drawings. Work outside the written scope is quoted separately and done only with written approval.
Pick the service, tell us about your equipment, and your message goes straight to the engineer. Replies usually within 2 business days.
Prefer e-mail? Write to sales@syonautomation.com.
Exact figures are confirmed in your written quote before anything is booked.
Use the form above, or e-mail sales@syonautomation.com. Replies usually within 2 business days.