SyteLine Upgrade Data Conversion Guide
Data conversion during a SyteLine upgrade ensures that all business data transitions correctly from the source version schema to the target version schema. While the Infor Database Upgrade utility handles most standard schema changes automatically, custom tables, modified standard columns, and complex data relationships may require manual conversion scripts. Open transactions, work-in-progress data, and historical records each present unique conversion challenges that must be addressed to maintain data integrity through the upgrade.
Schema Migration and Data Transformation
The Infor Database Upgrade utility applies a sequence of SQL scripts that alter table schemas, migrate data between restructured tables, add new columns with default values, and remove deprecated columns. Custom tables with Uf_ prefix are not modified by the upgrade utility but may need manual schema updates if they reference standard tables that changed. Data transformations handle scenarios where the target version stores data differently -- for example, a single field split into multiple fields, enumeration value changes, or unit of measure conversions. Each transformation must be scripted, tested, and executed as part of the upgrade process.
- Review the Infor Database Upgrade script manifest to understand every schema change applied during the upgrade
- Identify custom tables referencing standard table columns that are renamed, moved, or restructured in the target version
- Write data transformation scripts for custom data that requires reformatting to match new schema requirements
- Test all transformation scripts against a copy of production data to validate correctness before the upgrade window
- Create rollback scripts for each custom transformation to enable data recovery if conversion errors are detected
Open Transaction and WIP Handling
Open transactions present the most complex data conversion challenge because they span multiple tables and have in-flight state that must remain consistent. Open sales orders, purchase orders, production orders, and financial transactions must convert cleanly with all line items, statuses, and cross-references intact. Work-in-progress (WIP) data including job material issues, labor postings, and overhead allocations must maintain their cost layer integrity through the upgrade. The recommended approach is to minimize open transactions before the upgrade by accelerating order completions and closings during the pre-upgrade period.
- Run an open transaction aging report two months before upgrade to identify orders that can be completed or closed
- Freeze new long-lead-time order creation during the pre-upgrade period to reduce in-flight transaction volume
- Validate open PO, CO, and production order conversion by comparing line counts and amounts pre and post upgrade
- Verify WIP cost integrity by reconciling job cost totals before and after the database upgrade for all open jobs
- Test mid-process transactions (partially received POs, partially shipped COs) to confirm they resume correctly post-upgrade
Historical Data and Archival Strategy
Historical data including closed transactions, archived records, and audit trail entries must convert correctly but also present an opportunity for data archival. Large historical datasets increase upgrade processing time and target database size. Archiving older historical data before the upgrade reduces the data volume being converted, speeds up the upgrade process, and starts the new version with a cleaner dataset. SyteLine transaction history in the matltran, journal, and coitem_hist tables can grow to millions of records that significantly impact upgrade duration.
- Analyze historical data volumes in key tables (matltran, journal, coitem_hist) and estimate upgrade time impact
- Archive historical data older than the regulatory retention period to a separate database before the upgrade
- Verify that archived data remains accessible through read-only reporting after removal from the active database
- Estimate upgrade time reduction from archival -- large transaction history tables can add hours to the upgrade process
- Document the archival approach and retention policy to satisfy audit and compliance requirements post-migration
Ensure clean data conversion during your SyteLine upgrade. Netray provides data analysis, conversion scripting, and validation services for upgrade projects.
Related Resources
SyteLine Upgrade Testing Strategy
Design a comprehensive testing strategy for SyteLine upgrades including regression testing, performance benchmarking, integration validation, and UAT planning.
MigrationSyteLine Upgrade Downtime Planning
Minimize SyteLine upgrade downtime with detailed cutover planning, parallel processing strategies, and business continuity procedures during the upgrade window.
MigrationSyteLine 9 to 10 Upgrade Checklist
Complete upgrade checklist for migrating from Infor SyteLine 9 to SyteLine 10, covering Mongoose migration, database conversion, and form compatibility steps.