Architecture Changes: SyteLine 8 vs 10
NET remoting. SyteLine 10 replaces this with a web-based IFS framework served through IIS and the Mongoose application server. This shift affects every aspect of the user experience: forms render in a browser instead of a Windows application, customizations must be rewritten from WinForms to IFS patterns, and system administration changes from client deployment to web server management.
- All WinForms customizations must be rewritten or replaced, there is no automatic migration path for custom forms
- Event handler code must be refactored from SyteLine 8 event model to SyteLine 10 IDO event architecture
- User interface changes require comprehensive user retraining, the web experience differs significantly
- Infrastructure shifts from client deployment (each desktop) to centralized web server management (IIS + Mongoose)
Customization Assessment and Remediation
The customization assessment is the critical path of any SyteLine 8 to 10 upgrade. Inventory every customization: custom forms, modified stored procedures, event handlers, custom reports, and integration points. Classify each as: convert to SyteLine 10 equivalent, replace with standard SyteLine 10 functionality (many SL8 customizations are now standard features), or retire because the business need no longer exists.
This assessment typically reveals that 30-50% of customizations can be eliminated.
- Inventory all SyteLine 8 customizations: forms, stored procedures, event handlers, reports, and integrations
- Classify each customization: convert, replace with standard, or retire based on current business necessity
- Prioritize conversion of customizations supporting critical daily operations for the first testing cycle
- Engage business process owners to validate which customizations still serve active business requirements
Upgrade Execution and Testing Strategy
Execute the upgrade in a sandbox first, measuring the technical upgrade process (database schema changes, configuration migration) and identifying issues before they affect production. Plan 4-6 regression testing cycles with defined test scripts covering all business processes. Each cycle should run the full test suite, log defects, remediate, and retest.
Allow 3-4 months for testing in environments with 100+ customizations. User acceptance testing should involve actual end users performing real-world workflows.
- Execute the database upgrade script in a sandbox and measure total execution time for cutover planning
- Build regression test scripts covering all critical business processes: order-to-cash, procure-to-pay, plan-to-produce
- Plan 4-6 testing cycles with defect tracking, remediation, and retesting between each cycle
- Conduct formal user acceptance testing with end users performing realistic day-in-the-life scenarios before go-live
Try it here, free
NAV to Business Central Upgrade Assessment
Answer ten questions about your Dynamics NAV environment to see how ready you are to upgrade to Business Central and what to tackle first.
Frequently asked questions
What is SyteLine 10?
SyteLine 10 is the web-based release of Infor SyteLine (the product family also sold as CloudSuite Industrial). It replaces the SyteLine 8 Windows client with browser-based forms served from IIS and the Mongoose application server.
Can SyteLine 8 customizations move to SyteLine 10 automatically?
No. Custom forms and event handlers need to be rewritten or replaced, so start with an inventory of every customization and decide whether to convert it, replace it with standard functionality or retire it.
How long does a SyteLine 8 to SyteLine 10 upgrade take?
It depends mostly on the number of customizations and integrations and on how many test cycles you run. Sites with many customizations should plan several months of regression testing in addition to the technical upgrade itself.
Planning your SyteLine 8 to 10 upgrade? talk to our migration team about an upgrade assessment.