Moving · how-to
The parallel-run playbook for cutting over during peak season: what migrates first, what finishes in the old system, and the one step you cannot undo.
Every owner who hates their current system has the same fallback plan: limp through summer, switch in the slow months. It sounds prudent. It is usually the most expensive option on the table. 11.8 percent of Americans moved to a different residence in 2024, and that demand does not spread evenly across the calendar. The same federal research on move seasonality puts the year's volume into exactly the weeks you are living through right now. Waiting until January means running your worst tools through your best window, then doing the migration when there is no revenue left to protect anyway. There is also nothing unusual about your situation. US moving services run $25.7 billion in revenue across 9,430 businesses, which means the typical operator is small. Small usually means busy, and holding the business together with a spreadsheet, a shared calendar, and memory. If that description stings, read why most moving companies are flying blind after this one. The point here is narrower: the tools that got you to peak season are the same ones dropping leads during it.
Put real numbers on what a bad migration costs, because "we lost some leads" is too soft to act on. BLS puts median pay for hand laborers and material movers at $18.12 an hour, so a three-man crew burns roughly $54 an hour in wages alone while it idles outside a house that got double-booked during a sloppy import. That is illustrative math off the federal median, not a study, so run it with your own payroll. Add the truck, the fuel, and the customer who watched your crew stand around and will never call you again. Now flip it to the revenue side. A lost four-hour job at a $150-an-hour crew rate is $600 gone, plus the wages you paid to not earn it. Multiply by Saturday, the day your calendar is fullest and your margin for error is zero. We wrote about what Saturdays really cost moving companies, and a hard cutover concentrates all of that risk into the exact days you cannot afford it.
The hard cutover, where you export everything Friday night, import everything Sunday, and go live Monday morning, is how migrations fail. One malformed spreadsheet column and your Tuesday jobs have no addresses. The parallel run trades speed for certainty. From day one, every new lead and every new booking goes into the new system, no exceptions, because new data entered fresh is data you can trust. Every job already scheduled, crewed, and confirmed stays in the old system and finishes there, delivered and paid, before that system gets turned off. Operators who run this pattern typically hold both systems live for one to two weeks. Your dispatcher works two calendars for that stretch, which is tedious. It is also the entire insurance policy. Settle the destination question on a slow week rather than during the cutover itself. We keep an OptimizeIt vs. MoveitPro comparison covering price, seats, and what ships in the box. The cutover is not the day you buy new software. It is the day you stop needing the old system to run a Saturday.
Most owners migrate in exactly the wrong order: they start with the full customer history because it feels like the whole business, then run out of patience before the important part. Reverse it. Open estimates and unpaid invoices move first, on day one, because they are revenue in motion and every day they sit in a dying system is a day nobody follows up. The next two weeks of booked jobs move second, checked line by line against the old calendar, because a missing address is the failure customers remember forever. History goes last, and it can wait. Old jobs, dead leads, three years of notes: export them, keep the file, and import them in week two or in November. Nothing about a move you delivered in 2024 needs to block a move you are booking today.
Almost every step above is reversible. If an import goes sideways, you re-import. The phone number is the exception, and it deserves its own paragraph of paranoia. FCC rules require simple number ports to complete within one business day, with multi-line business setups as the slower exception, so the port itself is rarely the bottleneck. The danger is sequencing: cancel your old phone service before the port confirms and you can strand the number your trucks, your yard signs, and a decade of customers all point to. Port first, confirm, then cancel. On OptimizeIt, the business phone line comes with the Plus tier, so your ported number rings inside the same system that holds the calendar. On Pro, the AI Voice Agent answers that line when every human you employ is carrying a dresser down a staircase, which during peak season is most of the time.
The reason this playbook is practical rather than theoretical is that the setup work is small. OptimizeIt is a moving CRM built around the estimate-to-job workflow, so day one looks like importing your open estimates, loading your rates, and sending your first quote from the new system that afternoon. Follow-up automation picks up the chase on every open estimate you migrated, which is usually where mid-season revenue was quietly leaking. After the job, review and referral asks go out without anyone remembering to send them. Pricing is public: Core is $79 a month with two seats, Plus is $159 with four seats and the phone line, and Pro is $239 with six seats and the AI Voice Agent, all on annual billing, with extra seats a flat $25 a month. The full detail is on the pricing page, and if you are still deciding what a purpose-built system should include before you commit to any switch, start with the moving CRM overview.
This playbook is not for everyone. If you are a one-truck operator with no office help and your next open Saturday is in September, the parallel run has no one to run it, and you should book the switch for your first slow week instead of forcing it now. If your current system is merely ugly but nothing is leaking, no dropped leads, no double-bookings, no unpaid invoices aging in silence, then mid-season is not your moment either, because the math above only pays when something is actually broken. And if you want the switch without the discipline, then wait. The discipline is the whole trick: one system for new jobs, the old one until in-flight moves close, the port before the cancel. A hard cutover in July is the one version of this that deserves its reputation.
Yes, if you treat it as a parallel run instead of a hard cutover. Book every new job in the new system from day one, let jobs already on the calendar finish in the old system, and keep both live until the last legacy move is delivered and paid. Operators who run this pattern typically hold both systems for one to two weeks. The mistake is not switching in July. The mistake is switching everything at once.
There is no defensible industry average, so plan from your own calendar instead. The setup work is measured in hours, not weeks: importing customers, loading your estimate templates, connecting your phone line. The parallel run, where both systems stay live, typically takes one to two weeks for operators who book new jobs in the new system immediately. The long tail is habit. Give your crew two Saturdays on the new tool before you judge it.
Money first, calendar second, history last. Open estimates and unpaid invoices move on day one because they are revenue in motion. Booked jobs for the next two weeks come next so nothing on the calendar goes missing. Full customer history, old jobs, notes, and dead leads can follow in the second week, or sit in an export file until winter. A move you delivered two years ago does not need to block a move you are booking today.
Not if you sequence it correctly. Number porting is regulated by the FCC and simple ports complete quickly, but the port is the true one-way door in any software switch. The rule that protects you is simple: never cancel your old phone service before the port confirms, because canceling first can strand your number. On OptimizeIt, the business phone line comes with the Plus tier, so you port once and every customer who saved your number still reaches you.
Core is $79 per month with 2 seats, Plus is $159 with 4 seats and the business phone line, and Pro is $239 with 6 seats and the AI Voice Agent that answers calls when your crew cannot. All prices are on annual billing, and extra seats are a flat $25 per month. Most moving companies switching mid-season start on Plus because the phone line matters during the port. See the full breakdown on the pricing page.
Let them finish where they started. Migrating a move that is already scheduled, crewed, and confirmed introduces risk with no upside, so the parallel-run pattern leaves in-flight jobs in the old system until they are delivered and paid. Your dispatcher works both calendars for a week or two, which is annoying but survivable. What is not survivable is a crew showing up to an address that never made it across in a rushed bulk import.