At the SyteLine User Network conference, my colleague Crystal Morris gave a great talk on some of the tools we use at JBT to help us migrate data from many disparate systems into SyteLine. Crystal is on the SyteLine integrations team here at JBT, and using the tools listed here has migrated 3 manufacturing locations and 5 sales/service/financial reporting locations to SyteLine 9.

Crystal requested that I upload these tools to SyteLinePSA. All of the files have been cleaned of sensitive data, and are cleared for sharing with permission from JBT. Along with each file will be a quick description from Crystal on what it does.

Items Mapping

This is the file I use to pull each table’s schema from SL9 then fill out the mapping from the legacy system.  This includes any transformations needed to the data as it is loaded into SL9.

Chart of Account and Unit Code Listing

This is a listing of the current chart of accounts along with any additional details needed for the accounts.  It is used to load into new sites and confirm the setup is correct in the Production environment

Chart of Accounts and Unit Code Accessibility Checks

This is the file which have the Listing linked in to confirm the setup in all sites and entities.  This includes the account exists and the following information matches the listing: Description, Accessibility by Unit Code, Account Type, Account Class, and whether there are Unit Codes associated with the account if they are Required or Accessible.

Customers

This file is used to pull all customers from the legacy and analysis which customers should be transferred to SL9 as well as cleanses and determines any transformations to load into SL9.  Customers to transfer is determined by recent activity, open orders (COs, PRJs, SCOs, SROs, RMAs), open accounts receivable, no indication it should be removed (Labeled “Do Not Use”, “Obsolete”, or “Cancel”), does the customer not meet the previous criteria, but is a Corp Customer, etc.  Next the Legacy Addresses are cleansed and lines up with existing Customers already in our Production Environment and duplicate records are identified and loaded as needed (Duplicates within only the Legacy are removed; Duplicates with the Prod Environment are labeled to use the Prod Customer Number.)  Lastly, additional information which may not exist or needs a complicated transformation are added to the final XrefCustNum and XrefCustomerMap.

Data Workshops

This is a listing of all the information which is reviewed with the Site Team during the Data Workshops to ensure we cover all of the topics.  During the Data Workshops, meetings are held with cross functional team related to the functional area which has an assignment.  As an example, the Item Master is included in the Inventory Functional group, but the setup requires input from the Sales, Purchasing, Production and Engineering departments.  The Inventory Functional Leader is assigned the task, but should get input from the other departments.

Items Checklist

This is a checklist to verify the data load.  Each functional leader is assigned to review 5-10 records in SL9 while comparing it to their Legacy system.  Any differences should be documented and logged on the issues list for further review and correction.

Master Checklist

This checklist is to keep track of all of the codes within each system as well as when and why something was updated.  There is usually a reference to a HelpDesk Ticket number which would provide further details.  This is very helpful when you are dealing with multi-site which may have different codes which is very hard to review side by side or in the same listing.

Open POs

This is a listing of Open POs from the Legacy system with the same parameters which will be used to transfer to SL9.  The file includes assignments as well as documenting the teams progress from the previous file and the inception of the project.

Replication Rules Seed

This file has formulas to determine what replication rules need to be setup between the sites and entities.

AP Aging Tie Out

This is a reconciliation of the AP Aging Report from the legacy system to SL9 after the data load to determine if there are any variances.

Conversion Validation

This file is used to do a field by field validation of the loaded data by comparing it to the legacy system with all transformations.

XrefUoM

This is a conversion file for the Unit of Measures form. The records from the Legacy system and SL9 are pulled and then mapped.  This file will be used when doing the transformation of the Legacy data.