Yard Rotation Planning for Migratory Beekeepers

The most profitable migratory operations rotate through 6 to 10 crop types per season. That's not just diversification for its own sake. It's the strategy that maximizes hive utilization, spreads weather risk, and keeps revenue flowing through a season that otherwise has significant idle periods between single-crop placements.

Planning a full-season yard rotation is the most complex scheduling task in commercial beekeeping. You're coordinating bloom windows that shift with weather, contract dates that were negotiated months ago, truck capacity, crew availability, and hive health, all simultaneously, across hundreds or thousands of miles.

No competitor offers season-long rotation planning tied to both bloom data and contract timelines the way PollenOps does. Most rotation planning happens on a whiteboard or in a spreadsheet, rebuilt every season from scratch.

TL;DR

Most states require a Certificate of Health or Certificate of Veterinary Inspection issued by the origin state before out-of-state colonies can enter.
A California-to-Florida-to-Pacific-Northwest-to-Northern-Plains circuit is the most common full-year migratory route for large commercial operations.
Interstate permit coordination requires lead time; certificates typically need to be obtained 7-30 days before entry depending on the destination state.
Moving 1,000 hives requires 2-3 truck loads per move, with fuel, driver wages, and DOT compliance as the primary variable costs.
Operations that plan their annual circuit 6-8 months in advance can sequence pollination contracts and honey production to maximize annual revenue per hive.

What Rotation Planning Actually Involves

Yard rotation for migratory beekeeping means thinking about your hive inventory as a continuous flow, with hives entering one crop cycle as they exit another and repositioning happening in the windows between bloom peaks.

The planning challenge has three layers:

Layer 1: Crop sequence. Which crops can follow which, given geography and timing? Almonds into cherries works well geographically in the West. Blueberries into honey flows in the North works for some operations.

Layer 2: Contract timing. Your contracted delivery dates may not exactly match ideal bloom timing. The rotation plan needs to satisfy both your contract obligations and the biological reality of when each crop blooms.

Layer 3: Operational capacity. Your trucks, crew, and hive strength all constrain when and how fast you can move. Rotation planning that ignores operational capacity fails in execution.

PollenOps rotation planner generates a visual season timeline from January almonds to fall honey. This visual representation is what turns the three-layer planning problem from something you try to hold in your head into something you can see, adjust, and execute against.

The Typical Migratory Season Rotation

Anchor: California Almonds (February–March)

For most West Coast migratory operations, California almond season is the season anchor. Almond bloom demand drives the highest per-hive rates and the most concentrated move schedule.

Hives from wintering yards in California, Arizona, or the South need to be in place by early to mid-February, depending on regional bloom timing. The window is tight. Almond bloom lasts roughly 2-3 weeks, so all hive placements need to be complete before peak bloom.

Post-almond, hives exit California orchards in late February through mid-March. Where they go next defines the first rotation link in your season.

First Rotation: Cherries and Early Tree Fruits (March–April)

Sweet cherry bloom in Washington State typically follows California almond by 4-6 weeks. This creates a natural rotation window: exit almonds, move north to cherry country.

Cherry bloom windows are tight: 5-10 days per orchard at a given elevation. Operations running multiple cherry contracts need to sequence moves by elevation (lower elevations bloom first) to cover multiple windows with the same hive set.

PollenOps cherry bloom alerts adjust for elevation, so you know when each specific yard will hit peak bloom rather than relying on the regional average.

Second Rotation: Apples and Pears (April–May)

Apple bloom follows cherry in most regions. The rotation from cherries to apples can work smoothly if your contracted yards are in proximity. Washington and Oregon have both cherry and apple production, making same-region rotation practical.

Timing for apple contracts varies by variety and region. Hive removal timing also varies. Some contracts specify removal at petal fall, others at a defined date. Know your pickup triggers before planning the next move.

Third Rotation: Blueberries (May–June)

Highbush blueberries in Michigan, New Jersey, and the Pacific Northwest, plus lowbush blueberries in Maine, require significant hive numbers during a compressed bloom window.

For operations rotating from western states, the logistics of getting hives to Michigan or Maine are substantial. Many operations build their blueberry contracts around hive sets that don't need to be in California for almonds, running separate hive tracks on parallel seasonal routes.

Fourth Rotation: Summer Crops and Honey (June–August)

Cucumbers, squash, melons, and sunflowers fill the summer pollination calendar. Clover, wildflower, and sunflower honey yards can be interleaved with late summer pollination contracts.

Many migratory operations use summer as both a pollination and honey production period, placing hives in honey-producing environments between pollination commitments.

Fifth Rotation: Fall Buildup and Winter Prep (September–November)

Hives move to wintering locations in the fall. For operations in cold northern states, this means moving south or to locations where bees can maintain a winter cluster without dying. For California operations, winter yards may be in the Central Valley or almond-adjacent areas where the cycle begins again in February.

How to Plan a Full-Season Rotation

Step 1: Map Your Committed Contracts

Enter every signed contract into PollenOps with contracted delivery dates, yard locations, and contracted hive counts. These are your fixed points: the dates and locations you've already committed to.

The PollenOps rotation planner displays these contracts as a timeline. You can immediately see the contracted sequence and the gaps between placements.

Step 2: Overlay Regional Bloom Timing

PollenOps overlays regional bloom forecasts for each crop onto your contract calendar. You can see whether your contracted delivery dates align with expected bloom timing or whether there's a mismatch that needs to be resolved with the grower.

For your second and third rotation opportunities (crops you haven't contracted yet), the bloom calendar shows when different crops in different regions will be open. You can identify open bloom windows that align with your hive availability.

Step 3: Identify Rotation Windows

Between your committed contracts, there are periods when your hives are available for repositioning. These windows vary in length, sometimes two weeks between crops and sometimes six.

Mark each window on the rotation calendar. Which ones are long enough for a meaningful additional crop placement? Which are just repositioning time with no contract opportunity?

For commercial bee yard management, the yard availability during rotation windows depends on which yards are under active contract. PollenOps yard status tracking shows which yards are occupied and when they'll be available.

Step 4: Plan the Geographic Rotation

Draw the geographic arc of your season. Where are your hives in February? Where do they need to be in April? In June? In August?

The efficiency of your rotation is largely determined by this geographic arc. Operations that plan a continuous northward or southward arc (following bloom timing) move hives efficiently. Operations with contracts that require backtracking pay for it in fuel and timing.

For seasonal pollination contract calendar, the geographic visualization in PollenOps helps you see whether your rotation arc makes geographic sense before you've committed to the contracts.

Step 5: Assess Operational Capacity at Each Transition

For each rotation transition, exiting crop A and entering crop B, verify that your truck capacity and crew availability support the move. If a transition requires moving 400 hives from California to Washington in a 10-day window, how many truck runs does that require? Do you have the trucks and crew?

Flag transitions that may strain your operational capacity and plan either to supplement (rent trucks, hire additional crew) or to limit your contract volume at that point in the season.

How to Avoid Overlap Between Two Simultaneous Rotations

Many experienced operations run two parallel rotation tracks with different hive sets on different crop sequences simultaneously.

Track A might follow almonds → cherries → apples in the West.

Track B might follow southeastern states in spring → Midwest blueberries → North Dakota sunflowers in summer.

Managing two simultaneous tracks requires separate sub-calendars in PollenOps, each tracking its own contracts, bloom windows, and move schedules. The tracks share resources (trucks, crew) at transition points, which is where conflicts arise.

The critical overlap prevention principle: plan shared resource usage at transition points before committing to contracts on both tracks simultaneously. If the same truck needs to support both tracks in the same week, you either need a second truck or one track needs to shift.

FAQ

How do I plan a full-season pollination yard rotation?

Start by mapping your committed contracts in PollenOps to establish your fixed seasonal timeline. Overlay regional bloom forecasts to verify timing alignment and identify open windows for additional crop placements. Plan your geographic arc for the season, mapping where hives need to be at each stage, and verify that transitions are operationally feasible. Identify capacity constraints at high-demand transition points and plan resources accordingly. Build the rotation in the PollenOps planner so every contract, bloom alert, and move is visible on a single seasonal timeline.

What is the typical order of crops in a migratory season?

The most common West Coast rotation sequence for large migratory operations is: California almonds (February) → Pacific Northwest cherries (March–April) → Pacific Northwest apples (April–May) → Midwest or Northeast blueberries (May–June) → summer honey and summer crops (June–August) → fall wintering preparation (September–November). Specific timing varies significantly by year based on weather, and by region based on local variety mix and elevation.

How do I avoid overlap between two simultaneous yard rotations?

Create separate rotation tracks in PollenOps for each simultaneous hive set. Build each track's contract calendar independently, then overlay them to identify shared resource conflicts. Pay particular attention to transition windows where both tracks need trucks or crew simultaneously. Resolve conflicts at the planning stage, before contracts are signed, by adjusting contract dates, supplementing fleet capacity, or limiting contract volume on one track during peak overlap periods.

What is the most common full-year circuit for US migratory beekeepers?

The classic commercial circuit runs: winter buildup in Florida or southern Texas, California almonds in February, Pacific Northwest tree fruit (cherry, apple, pear) in April-May, Pacific Northwest or northern Midwest berry and clover crops in June-July, summer honey production in North Dakota, Montana, or Minnesota in July-August, and fall honey extraction and requeening before the cycle restarts. The exact circuit depends on contracted commitments, hive capacity, and the operator's regional relationships.

How do you coordinate state entry permits for a multi-state circuit?

State entry permits and health certificates require lead time: most states want certificates issued 7-30 days before entry. For a circuit that crosses 5-6 states, this means overlapping certificate applications where a certificate for the next state must be initiated before the current state's placement ends. Some operators use a permit tracking calendar that accounts for the lead time required for each destination state. PollenOps includes a permit tracking feature that alerts operators when certificates need to be initiated based on planned move dates.

What are the most common mistakes new migratory operators make?

The most common errors are underestimating transport costs, failing to secure contracts before building hive capacity, not accounting for state entry permit lead times, and neglecting varroa management during the compressed pre-almond preparation period. New operators often also underestimate the administrative load of managing 10-20 contracts across multiple states -- tracking payment status, compliance documentation, and crew scheduling simultaneously requires systems, not just a spreadsheet.

Sources

USDA Agricultural Research Service
Bee Informed Partnership
American Beekeeping Federation (ABF)
American Honey Producers Association
USDA Animal and Plant Health Inspection Service (APHIS)

Rotation Is How You Maximize Your Season

A single-crop operation leaves revenue on the table. Two well-planned rotations using the same hive inventory can generate 40-60% more revenue than a single crop placement per season.

Get Started with PollenOps

Migratory operations face the most complex coordination challenges in commercial beekeeping: permits across multiple states, staggered delivery windows, and fleet logistics that have to work precisely across hundreds of miles. PollenOps was built to handle multi-state, multi-grower, multi-crop operations at this level of complexity.