Batch Migration Checklist: What to Do Before the Technician Ever Arrives

Ask any batch control technician what separates a smooth migration from a chaotic one, and they'll tell you the same thing: it's almost never the install day itself. It's everything that happened — or didn't happen — before the install team showed up.

The producers who come out of migrations on schedule, with systems running clean and operators comfortable, aren't just lucky. They spent two to four weeks doing the unglamorous prep work that most producers skip. The ones who skip it spend the first half of install day tracing unlabeled wires, hunting down outdated schematics, and trying to remember which version of a mix design is actually current.

None of this prep is complicated. But skipping it is what turns a four-day migration into a painful one. Here's what to do before the technician ever arrives.

1. Audit and Clean Up Your Mix Designs

Your batch system's mix design library is the asset that matters most in a migration. It's also the one most likely to be a mess after 15 or 20 years of modifications, workarounds, and version drift.

Before your data gets imported into the new system, go through the library with fresh eyes:

• Identify duplicate or near-duplicate recipes and consolidate to a single authoritative version
• Flag any mix designs that haven't been used in 12+ months — decide whether to import or archive them
• Verify that each active mix design reflects current specs, not an older formulation that's been superseded
• Note any recipes with unusual or undocumented modifications so your tech team knows what to expect during import

Migration is your best forcing function for a data cleanup you've probably needed to do for years. Don't import the mess — fix it first.

2. Document Your Current Integrations

Anything connected to your batch system needs to be cataloged before cutover. Things that work silently in the background have a way of breaking silently during a migration — and you won't always notice immediately.

• List every system that currently communicates with batch: dispatch, QC, ERP, ticketing, invoicing
• Document how each integration works (data direction, frequency, format)
• Identify the person who owns or supports each integrated system — you may need them available during cutover
• Confirm with your migration team how each integration will be handled after go-live

3. Update Your Plant Wiring Schematics

Wiring changes accumulate over decades. A conduit gets re-routed. A sensor gets added. Something gets bypassed and nobody updates the drawing. After 20 or 30 years, the schematic on the wall often bears only a passing resemblance to what's actually in the panel.

Having accurate, current schematics in hand before the technician arrives can eliminate half a day of install time that would otherwise be spent tracing wires manually.

• Pull your existing wiring diagrams and review them against the current physical setup
• Note any changes that have been made since the drawings were last updated
• If your schematics are significantly out of date, have an electrician walk the system and mark up a current version before the migration date
• Provide finalized schematics to the installation team before they arrive onsite

4. Label Your Wires and Cables Ahead of Time

This one sounds minor. It isn't. Unlabeled wires turn a straightforward physical swap into a detective exercise — and every mystery burns install time.

• Label all signal cables and wires connected to the batch controller
• Label the plant-side termination points as well as the controller-side ends
• Pay particular attention to any wiring that's been added or modified outside of the original installation
• If the 48-pin plant control cable has been field-modified, document those changes

An hour spent labeling before install day saves two to three hours of tracing during it.

5. Choose Your Migration Window Deliberately

The timing of your migration matters as much as the preparation. The goal is a low-pressure window that still gives you enough active work to dial the system in.

• Target a low-volume period: weekends, slower weather months, or the off-season before your busy stretch
• Avoid scheduling during your highest-volume weeks — you want margin if something needs adjustment
• Don't schedule into a completely dead period either; you need some real orders running through the new system before you declare success
• Confirm that your install window gives the tech team enough time to complete installation, run test batches, and resolve any issues before you're back to full production

6. Capture Your Current Jog and Feed Times

Before the old system goes dark, screenshot or print every configuration screen that contains settings you'll want to replicate. Jog times, feed times, moisture correction factors, and other calibration settings serve as your baseline for configuring the new system — and they're gone once the old system is decommissioned.

• Screenshot or print all current jog and feed time settings
• Document moisture correction factors for each aggregate bin
• Record any custom timing sequences or batch parameters that aren't part of the standard configuration
• Store these records somewhere accessible on install day — don't rely on memory

7. Line Up Your Stakeholders Early

A batch migration doesn't happen in a vacuum. Several outside parties need to be scheduled around the same install window, and they each have their own availability constraints.

• Schedule your scale calibration company for shortly after installation — the new system needs to be calibrated before it runs real orders
• Notify your admixture supplier so they can be available if dispenser configuration needs to be adjusted
• Confirm electrician availability in case any wiring work needs to be done during or immediately after install
• Alert your dispatch team and key customers to the planned migration window so nobody is caught off guard

8. Validate Imported Data Before You Batch Live

Once your mix designs have been imported into the new system, do not run real orders until you've spot-checked them. Importing is not the same as verifying.

• Select a representative sample of your most-used mix designs — at minimum, your top 10 by volume
• Compare each one against the source record in the old system, field by field
• Flag any discrepancies for correction before go-live
• Have your QC team or plant manager sign off on the validation before the first live batch runs

The Difference Between a Four-Day Migration and a Four-Day Headache

None of the items on this list are technically difficult. Most can be completed by plant managers and operators without outside help. What they require is time, attention, and the discipline to do them before the install window — not during it.

The technicians who show up to a well-prepped plant can focus on the installation. The ones who show up to an unprepped one spend half their time solving problems that could have been avoided. The difference shows up in how long the migration takes, how many issues arise during cutover, and how quickly your operators feel comfortable on the new system.

If you're planning a batch migration and want a structured walkthrough of what the process looks like for your specific operation, contact Sysdyne to schedule a migration consultation.