ERP integration
Keep the software you rely on. Connect it to modern manufacturing.
Older, server-based software can still be central to your business. SmartShopFloor can connect with on-premises legacy systems through options ranging from basic CSV data imports to bi-directional database integration, depending on the system and agreed scope.
On-premises, server-based software connected through CSV imports or scoped two-way database integration.
Is it a fit?
For manufacturers who cannot simply replace their existing system
- Your business relies on software running on an on-premises server.
- Production teams need scheduling and tablet-based execution alongside that software.
- You want an integration approach that reflects what the existing system can support.
Stays in Legacy Systems
- The business records you already maintain
- Established office processes
- Existing system responsibilities and controls
SmartShopFloor adds
- Production planning and work allocation
- Shop-floor execution on tablets
- Manufacturing progress and paperwork
How it works
The Legacy Systems workflow, step by step
- Step 1
Review the existing setup
Discuss the legacy software, how your team uses it and the manufacturing handovers you want to improve.
- Step 2
Choose the right approach
Agree whether CSV data imports meet the need or a two-way database integration is appropriate and supported.
- Step 3
Connect the workshop
Introduce SmartShopFloor scheduling and operator workflows around the agreed information exchange.
- Step 4
Test before going live
Prepare, run and verify user acceptance tests. Move into production only after your team approves the results.
Scope for Legacy Systems. Not every legacy system supports the same connection. CSV imports do not imply continuous or two-way synchronisation. Database integration, update frequency and supported business processes are confirmed after reviewing your setup.
Why manufacturers connect Legacy Systems
No forced replacement
Explore a connection that retains the software your business depends on rather than starting with a migration.
A practical starting point
A basic CSV import may be enough for an initial handover. A broader integration can be assessed where needed.
An agreed support boundary
Managed support covers SmartShopFloor and the agreed integration, with responsibilities for the legacy system clearly defined.
Implementation & support
Nothing goes live until you approve it.
Connecting Legacy Systems is a managed project, not a switch. We agree the scope, including any additional ERP customisation needed for your sales-to-production handover, then prove it with your own jobs before switching over.
Managed service. Ongoing support covers SmartShopFloor and its agreed integration. Your ERP or CRM vendor continues to support their own product unless agreed otherwise. Service terms are set out in your agreement.
- 01
Scope
Agree the workflow, the records in scope and any ERP customisation.
- 02
Configure
Set up SmartShopFloor and the connection within that agreed scope.
- 03
UAT prepared
Build test scenarios from your own real jobs.
- 04
Tested
Run the full quote-to-dispatch loop end to end.
- 05
Verified
Check results together and resolve anything outstanding.
- 06
Customer approved
Your authorised people sign off readiness.
- 07
Go-live
Switch over only after approval.
- 08
Managed support
Ongoing support for SmartShopFloor and the agreed integration.
FAQs
Legacy Systems integration questions
Can SmartShopFloor connect to software on our own server?
Yes, on-premises server-based software can be considered for integration. We review the particular software and your requirements before confirming the supported approach.
What is the simplest legacy integration option?
Basic CSV data import is one option. The information included and how your team prepares and imports it are agreed for your business.
Can a legacy connection exchange information in both directions?
Bi-directional database integration is an option where the existing system supports it. Suitability and the business processes covered are confirmed during scoping.
Will a CSV import keep both systems updated automatically?
A CSV import alone should not be treated as automatic, continuous or two-way synchronisation. We agree how updates will be handled and who is responsible for them.
Who approves go-live for a legacy integration?
Your authorised team approves go-live after user acceptance testing has been prepared, tested and verified. Ongoing support covers SmartShopFloor and the agreed connection, not unscoped maintenance of the legacy software.
Let's talk about your Legacy Systems setup.
Bring your current workflow and your questions. We will show you how SmartShopFloor fits and what a scoped rollout looks like.