Systems, Data, IT, and Administrative Cutover

17.1 Updating ERP, WMS, TMS, MES, HRIS, Finance, CRM, and Procurement Systems

The system’s impact assessment should begin with a complete application inventory. The move team should identify every system that references facility location, operating unit, warehouse, work center, cost center, ship-from point, ship-to point, employee work location, tax jurisdiction, customer routing, supplier delivery, equipment identity, inventory location, or compliance record. The obvious systems are not enough. Many move failures come from secondary applications, reporting tools, portals, spreadsheets, label engines, or interfaces that no one included in the cutover plan.

ERP is usually the central system of record. It may control plant codes, warehouse codes, inventory locations, purchasing, production orders, sales orders, shipping, finance, costing, fixed assets, and reporting. The team should define whether the move requires a new site code, reuse of an existing code, closure of an old code, or parallel operation across two codes during transition. This decision affects inventory visibility, financial reporting, tax, customer orders, supplier deliveries, and historical comparability. It should be made deliberately, not left to whichever configuration is easiest.

Warehouse management systems require location-level readiness. New zones, aisles, bins, docks, staging areas, quarantine locations, returns areas, replenishment rules, pick paths, pack stations, printer assignments, scanner profiles, labor standards, and cycle-count plans may all be required. If the WMS supports both the old and new sites during a phased move, the team must define how inventory transfers, order allocation, picking priority, and replenishment will work across locations. A warehouse cannot operate cleanly if system locations do not match the physical layout.

Transportation management systems control shipment execution. The move may change carrier pickup schedules, lane assignments, tendering rules, freight rates, routing guides, origin codes, delivery commitments, parcel pickup accounts, trailer-drop rules, dock appointments, and documentation. TMS updates should be tested with real carriers and realistic shipment types. A shipment that rates correctly but prints an incorrect origin address can still create customer receiving failures, carrier billing issues, or compliance problems.

Manufacturing execution systems may be deeply tied to the physical site. Work centers, equipment IDs, line names, recipes, production routes, electronic batch records, operator terminals, labor reporting, quality checks, machine interfaces, and process parameters may need updates. If equipment is moved and reinstalled, MES configuration should match the new line sequence and equipment identity. For regulated or quality-sensitive operations, MES changes may require validation or controlled change approval before use.

HRIS, payroll, timekeeping, scheduling, and labor systems must reflect where employees work and how they are paid. Changes may include work location, supervisor, shift, department, cost center, badge access, time-clock location, payroll tax jurisdiction, attendance policy, overtime rules, union or bargaining-unit information, and employee communications. These updates should be coordinated with HR, finance, legal, security, and operations. A facility that is ready to operate still fails on day one if employees cannot clock in, access the building, or appear in the correct schedule.

Finance systems should be reviewed for cost centers, profit centers, fixed-asset locations, lease accounting, depreciation, project accounting, inventory valuation, freight accruals, tax, insurance, intercompany transactions, and reporting. If the move involves consolidation or shutdown, finance also needs to manage stranded cost, asset write-offs, old-site closure costs, and duplicate operating costs. Finance should not receive system changes after the fact; it should help define how the move will be represented in the books.

CRM, customer service, procurement, and supplier-management systems should also be included. Customer records may need new ship-from locations, service territories, escalation contacts, pickup instructions, certificates, and account notes. Procurement systems may need new ship-to addresses, receiving contacts, purchase-order templates, approval routes, supplier portals, and contract references. The move team should test the end-to-end process, not only the individual application fields.

17.2 Network, Telecom, Security, Badge Access, Printers, Scanners, and Shop-Floor Technology

Digital infrastructure is part of site readiness. Employees can tolerate some unfinished cosmetic items, but they cannot run modern operations without network access, phones, scanners, printers, security systems, devices, and shop-floor technology. The IT workstream should treat the new site as an operating environment, not a generic office or warehouse connection.

Network planning should begin with carrier lead times, circuit capacity, redundancy, firewall rules, switching, wireless coverage, cabling, network closets, server rooms, device density, and cybersecurity requirements. The plan should identify which areas need wired connections, which need Wi-Fi, and which require resilient connectivity. Warehouses with racking, cold rooms, production equipment, metal structures, and high ceilings need coverage testing in the actual operating environment. A Wi-Fi design that works on paper may fail once racks, inventory, machines, and people are present.

Telecom readiness includes voice lines, call routing, contact-center queues, emergency phones, conference rooms, paging systems, intercoms, mobile coverage, voicemail, and customer-facing phone numbers. Office and customer-service moves require particular care because call handling may be part of the service promise. If phone routing changes during cutover, the team should test inbound calls, outbound calls, transfers, voicemail, emergency calls, and after-hours coverage. Customer-facing numbers should not be changed casually unless the communication plan is ready.

Security technology includes badge readers, access groups, door schedules, cameras, alarms, visitor management, gates, key control, guard systems, restricted areas, and monitoring. Badge access should be tested by role and shift, not only by administrator login. Employees may need different access for offices, production areas, warehouses, labs, server rooms, hazardous materials storage, records rooms, or secure cages. Contractors and temporary workers require controlled access and expiration dates. Security should also coordinate with HR so that terminated, transferred, or nonmoving employees do not retain inappropriate access.

Printers and scanners are small assets with large operational impact. Receiving, shipping, production, quality, maintenance, offices, customer service, and finance may all depend on local printing or scanning. Label printers are especially critical because they connect physical product to inventory, carrier, customer, and compliance systems. The team should test each printer with the actual forms, labels, barcodes, documents, network path, user permissions, and workstation assignments that will be used at go-live. A printer that works from IT’s laptop may not work from the scanner, terminal, or user profile used on the floor.

Shop-floor and operating technology includes handheld scanners, tablets, terminals, scales, PLCs, HMIs, sensors, cameras, machine interfaces, quality instruments, environmental monitors, battery chargers, mobile carts, kiosk computers, time clocks, and digital performance boards. These devices should be inventoried, configured, assigned, charged, mounted, protected, and tested in their final locations. Spare batteries, charging stations, cases, cables, mounts, and device management tools should be available before startup.

Cybersecurity should be built into the cutover. New network segments, vendor remote access, temporary connections, contractor devices, cameras, controls, and shop-floor systems create exposure if rushed. The team should define access rights, password policies, device enrollment, patch status, firewall rules, remote-access approvals, data backup, logging, and incident response. Temporary solutions should have expiration dates. A temporary connection installed to make startup easier should not remain unmanaged for years.

IT support coverage should match the move schedule. During cutover, the site may need extended support hours, floor walkers, help desk prioritization, vendor technicians, spare devices, and a direct escalation channel to the move command center. IT should not be expected to support go-live through normal ticket queues alone. Startup issues need rapid triage because a scanner, badge reader, printer, or network outage can stop an operating area.

17.3 Master Data Changes: Addresses, Tax, Banking, Supplier Records, Customer Records, and Compliance Documentation

Master data is the administrative foundation of the move. It defines how the company, suppliers, customers, employees, regulators, carriers, banks, and systems recognize the new site. Master data changes must be governed because they cross functions and often have external consequences. An incorrect address, tax code, supplier record, or customer record can create shipment holds, invoice errors, rejected deliveries, compliance gaps, or payment delays.

Address data should be reviewed wherever the facility appears. This includes legal address, physical address, mailing address, ship-to address, ship-from address, remit-to address where applicable, billing address, emergency address, tax address, registration address, website listings, email signatures, templates, portals, certificates, licenses, insurance policies, customer forms, supplier forms, and carrier records. The team should distinguish between address types because not all of them change in the same way or at the same time.

Tax implications should be reviewed with finance and tax specialists. A facility move may affect sales and use tax, property tax, payroll tax, local business taxes, incentives, customs, excise taxes, environmental fees, and reporting obligations. It may also affect customer invoices, supplier invoices, freight tax treatment, and employee work-location records. Tax data should be updated in the relevant systems before transactions begin from the new site. Incorrect tax setup can create downstream cleanup that is difficult and visible to customers or auditors.

Banking and payment data may be affected even when bank accounts do not change. Vendor forms, customer onboarding forms, remittance instructions, lockbox references, invoice templates, payment approvals, purchasing cards, site-level accounts, petty cash, deposit processes, and fraud-control records may reference the old location or responsible personnel. If the move changes who approves payments, receives checks, manages deposits, or handles invoices, the administrative process must be updated and controlled. Banking-related changes should follow stronger approval and fraud-prevention controls than ordinary address changes.

Supplier records should be updated with new ship-to locations, receiving contacts, dock rules, tax information, certificates, insurance requirements, safety rules, purchase-order templates, and portal data. Suppliers that deliver hazardous materials, regulated materials, temperature-controlled goods, customer-specific components, or high-value items may need additional documentation. Procurement should confirm that suppliers have updated their systems and that open purchase orders reflect the correct destination.

Customer records should be updated with new ship-from data, pickup instructions, service contacts, certificates, routing information, tax setup, EDI data, account notes, contract references, and customer-specific documents. Some customers require formal vendor-master updates before they will accept shipments or pay invoices. Others require approval of a new manufacturing, storage, or shipping location. The move team should identify these requirements before customer orders are cut over.

Compliance documentation should be updated in parallel. Permits, licenses, certificates, safety data, insurance records, quality certifications, audit documents, controlled procedures, regulatory registrations, environmental records, customs records, security documentation, and customer qualification packages may all need new-site information. The team should ensure that documents are not only updated internally but also distributed externally where required. A customer may not care that a certificate was updated if it was never uploaded to their portal.

Master data governance should include a change freeze where appropriate. In the days around cutover, uncontrolled updates to customers, suppliers, items, locations, tax codes, or system rules can create inconsistent transactions. The team should define which data is frozen, who can approve exceptions, when updates occur, how changes are validated, and how rollback or correction will work. Master data cutover should have the same discipline as equipment or system cutover.

17.4 Cutover Testing and Go-Live Support

Cutover testing proves that the new site can transact before the business depends on it. Testing should be end-to-end, role-based, and performed as close as possible to real operating conditions. The objective is not to prove that each system screen opens. The objective is to prove that the facility can receive, produce, inspect, store, ship, bill, pay, track, report, secure, and support work from the new location.

The test plan should be organized around business scenarios. For supply chain, test purchase order creation, supplier delivery, receiving, inspection, putaway, inventory transfer, quality hold, release, picking, packing, shipping, carrier pickup, and freight documentation. For manufacturing, test production order release, material issue, equipment interface, labor reporting, quality checks, batch or lot records, label printing, finished-goods receipt, and inventory availability. For office and service operations, test employee access, customer calls, case routing, document storage, approvals, reporting, and collaboration tools.

Testing should include edge cases. Normal transactions may work while exceptions fail. The team should test damaged goods, partial receipts, overages, returns, canceled orders, customer pickup changes, lot-controlled materials, serialized items, temperature excursions, inventory adjustments, manual labels, urgent orders, after-hours access, visitor registration, failed scans, printer outages, and approval escalations. Startup is when exceptions are most likely, so exception testing is not optional.

Mock cutovers are valuable for complex moves. A mock cutover rehearses the sequence of data updates, system changes, device activation, user access changes, communication steps, validation checks, and go/no-go decisions. It exposes timing conflicts, unclear ownership, missing approvals, and weak rollback plans. A full mock cutover may not be needed for a small office move, but any move with inventory, customer shipments, production, regulated processes, or multiple systems should rehearse the critical path.

The cutover runbook should be detailed enough to guide execution hour by hour where needed. It should list tasks, owners, start times, dependencies, expected duration, validation step, escalation contact, and rollback or contingency action. It should also include communication points: when users are notified, when suppliers and customers are informed, when leadership receives status, and when the site is approved for specific transactions. The runbook should be reviewed with every workstream that has a cutover action.

Go-live support should be organized as hypercare. Hypercare is the period immediately after go-live when the move team provides elevated support, rapid issue resolution, and close performance monitoring. It should include a command center or equivalent coordination forum, issue log, severity definitions, escalation paths, floor support, IT support, functional experts, vendor contacts, and leadership check-ins. The goal is to resolve startup problems before they become customer, safety, quality, or financial failures.

Support should be located where the work happens. Floor walkers can observe scanner issues, user confusion, printer problems, badge access failures, label errors, and workflow gaps faster than remote support can. Office moves may need visible help desks, meeting-room support, network support, and manager support. Manufacturing and warehouse moves may need IT, operations, quality, maintenance, and engineering personnel on the floor during early shifts.

After go-live, the team should reconcile data and transactions. Inventory balances, open orders, open purchase orders, shipments, receipts, employee time, customer invoices, supplier invoices, fixed assets, and financial postings should be reviewed for accuracy. Early reconciliation catches problems while they are still understandable. Waiting until month-end can turn small cutover errors into complex accounting, inventory, and customer-service issues.

17.5 IT and Master Data Cutover Checklist

The IT and master data cutover checklist should be used before the go-live readiness gate and again during the first days of hypercare. It should be owned jointly by IT, master data, operations, supply chain, finance, HR, procurement, customer service, and the move leader. The checklist should focus on evidence, not verbal confidence.

IT and Master Data Cutover Checklist

• Application inventory: Confirm every affected ERP, WMS, TMS, MES, HRIS, finance, CRM, procurement, quality, maintenance, security, reporting, and portal system is identified.
• System owner: Assign a named owner for each application, interface, device family, data set, and cutover task.
• Configuration changes: Confirm plant codes, warehouse codes, work centers, locations, docks, printers, routes, cost centers, shifts, access roles, and approval workflows are configured.
• Integration testing: Confirm interfaces between systems have been tested using realistic transactions and error handling.
• Network readiness: Confirm circuits, switches, Wi-Fi, network closets, firewalls, VPNs, redundancy, and monitoring are active and tested.
• Telecom readiness: Confirm phones, call routing, conference rooms, paging, contact-center queues, voicemail, and emergency lines are tested.
• Security readiness: Confirm badge access, cameras, alarms, gates, visitor management, restricted areas, contractor access, and terminated-user access controls are ready.
• Device readiness: Confirm scanners, printers, tablets, terminals, scales, time clocks, kiosks, shop-floor devices, batteries, chargers, mounts, and spares are configured and tested.
• Label and document testing: Confirm customer labels, carrier labels, pallet labels, compliance labels, packing lists, bills of lading, invoices, certificates, and forms print and scan correctly.
• Master data updates: Confirm addresses, tax codes, customer records, supplier records, item locations, ship-from points, ship-to points, banking references, and compliance documents are updated.
• External portal updates: Confirm customer portals, supplier portals, carrier systems, regulatory portals, certification records, and insurance records reflect the new site where required.
• User access: Confirm employees, supervisors, temporary labor, contractors, vendors, support teams, and administrators have appropriate access and inactive users are removed.
• Business scenario testing: Confirm procure-to-pay, order-to-cash, receive-to-stock, plan-to-produce, pick-pack-ship, hire-to-pay, and incident-response scenarios are tested.
• Exception testing: Confirm partial receipts, returns, damaged goods, quality holds, inventory adjustments, failed scans, printer issues, urgent orders, and customer pickup exceptions are tested.
• Cutover runbook: Confirm tasks, owners, sequence, timing, dependencies, validation checks, communication points, rollback actions, and escalation contacts are documented.
• Data freeze: Confirm freeze scope, freeze dates, exception approval, communication, and post-freeze validation process are defined.
• Go-live support: Confirm command center, floor support, help desk priority, vendor coverage, shift coverage, issue log, severity rules, and leadership cadence are ready.
• Reconciliation plan: Confirm inventory, orders, shipments, receipts, invoices, employee time, fixed assets, and financial postings will be reconciled after go-live.
• Open risks: Confirm unresolved IT and data risks have owners, contingencies, escalation triggers, and go-live impact documented.
• Go-live approval: Confirm accountable leaders have approved go-live, approved limited go-live, or delayed go-live based on evidence.

The checklist should use practical status definitions. Ready: the item is complete, tested, and supported by evidence. Ready with conditions: the item may proceed only under defined limits with named follow-up actions. At risk: the item could affect service, safety, compliance, finance, or operations and requires leadership attention. Not ready: the site should not proceed with the affected process until the gap is resolved or a formal contingency is approved.

IT and master data readiness should not be assessed only by the technology team. Operations should confirm that transactions work at the point of use. The supply chain should confirm that suppliers, carriers, inventory, and shipments transact correctly. Finance should confirm reporting, costing, tax, assets, and posting logic. HR should confirm employees can access, clock in, and appear in the correct systems. Customer service should confirm customer records and communication paths. The operating owner should confirm that the site can run.

The administrative cutover is complete only when the digital operating model matches the physical operating model. The new facility must be visible to systems, usable by employees, recognizable to external parties, and controlled through accurate data. When the cutover is done well, no one celebrates the systems. They simply work, which is exactly the point.