Big Ambitions: How to Move a Business to a New Location

Secure the new site before you close the old one

The order matters more than the method. Lease the new location first, while the existing business is still trading and its setup is still visible, because everything you need to reproduce at the new address is easier to read from a running business than from a closed one. Check the new lease against the equipment and shelf space you intend to bring, since a smaller unit quietly caps what you can move and turns a relocation into a partial rebuild. Budget for a period where you are paying for both sites at once. That overlap is not waste; it is what lets you prove the new location works before you lose the ability to fall back.

• Lease the new site while the old one is still trading.
• Compare the new floor space against the equipment you plan to move.
• Expect to carry both leases briefly and budget for it.

Write down the supply setup before anything moves

This is the step that separates a clean move from a week of broken deliveries. Before touching the business, record every supplier contract attached to it, every warehouse-to-shop route that feeds it, the stock targets on each product, and the staff assigned to the location. Community reports about moving a shop describe these links not following the business, and players who moved headquarters staff describe losing contract settings and having to rebuild routes from the warehouses to every shop by hand. Whether that is intended behaviour or a rough edge, the practical response is the same: capture the configuration while it still exists, because reconstructing it from memory afterwards is where the real cost of a move shows up.

• Record contracts, routes, stock targets, and staff assignments first.
• Moving headquarters staff is the case most likely to reset supply settings.
• Reconstructing from memory is what makes a move expensive.

Move the physical setup, then relink supply

With the new lease secured and the configuration recorded, move equipment and staff across, then rebuild the supply links rather than assuming they followed. Reassign employees to the new location, recreate the supplier contracts against the new address, and rebuild each warehouse route to point at it. Then push one product through the whole chain and watch it arrive on the shelf. Only when that single product has completed a full cycle should you close the original site. If deliveries fail at the new address, work through the same dependency order used for any delivery problem, starting from the destination stock target rather than rebuilding routes at random.

• Reassign staff to the new location explicitly.
• Recreate contracts and routes against the new address.
• Prove one product end to end before closing the old site.

Decide whether the move is worth it at all

Relocation costs a moving fee, some proportion of your equipment value if you sell rather than transport it, and the time to rebuild a supply chain that currently works. Those first two are version-sensitive numbers that guides quote inconsistently, so confirm the current fee and any resale rate in your own build rather than planning around a figure from an older write-up. Judge the move the way you would any large discretionary spend: a better location that raises daily customers for a business already limited by foot traffic can pay for itself, while a move made because a different street looks better usually will not. If the real problem is capacity or staffing rather than address, moving will not fix it.

• Confirm current fees and resale rates in your own build.
• Count the rebuilt supply chain as part of the cost.
• A capacity or staffing problem does not get solved by a new address.

What follows a business to its new address and what does not

Relocation is supported, and a moving service exists in the game, but the part that costs players a working save is not the furniture. Community reports on moving a shop consistently describe the same pattern: the physical move is the easy half, while supplier contracts and the warehouse-to-shop routes attached to the old location do not carry themselves over. Players who move headquarters staff describe losing contract settings and having to rebuild routes from the warehouses to every shop by hand. That makes the safe order clear even though exact fees change between builds: secure the new site first, write down every contract, route, and stock target while the old site is still running, then move equipment and staff, and only close the original once one product has completed a full supply cycle at the new address. Treat any specific moving fee, per-item charge, or equipment resale rate you read in a guide as version-sensitive and confirm it in your own build, since these are community-reported values rather than published specifications. The decision itself should be judged like any other large discretionary spend: a move that costs a week of profit and a rebuilt supply chain needs a reason better than a nicer street.

• Contracts and warehouse routes do not follow the business automatically.
• Keep the old site running until one supply cycle completes at the new one.
• Treat quoted moving fees and resale rates as community-reported and version-sensitive.

Plan this task in the current save

Start by defining the result you need in this save and the smallest change that can produce it. For this topic, the useful evidence is the state before the change, the exact action taken, and the result after a complete game cycle. Keep relocation and moving service, contracts and routes after moving, keep both sites briefly visible while planning so a purchase or layout change does not hide the original problem.

• Decide whether you are moving a shop, a warehouse, or headquarters.
• List every supplier contract and delivery route that touches the location.
• Confirm you can afford to run both sites during the overlap.
• Check the new lease size against the equipment you plan to bring.

Follow the workflow in a testable order

For this task, begin by making sure you secure the new location before closing anything at the old one. Do not jump to the final setup until that starting condition is visible in the save. Later steps depend on earlier ones, so confirm each dependency before continuing. The last checkpoint is to rebuild supply links and confirm one product arrives before closing the old site. This sequence remains useful when an exact price or interface label changes because it preserves the underlying cause-and-effect chain.

• Secure the new location before closing anything at the old one.
• Record the existing contracts, routes, and stock targets in full.
• Move or repurchase equipment, then move staff to the new site.
• Rebuild supply links and confirm one product arrives before closing the old site.

Diagnose the result without rebuilding everything

The first misleading signal to rule out is this: Deliveries that stop after a move usually mean routes were not relinked. Return to the last confirmed checkpoint and compare it with that condition. Avoid changing every route, employee, object, or setting at once because broad edits destroy the evidence needed to identify the cause. Work through the remaining failure modes individually, keep the save time and game version with your notes, and retest after one controlled correction.

• Deliveries that stop after a move usually mean routes were not relinked.
• A contract pointing at the closed site will not follow the business automatically.
• Staff left assigned to the old location will not appear at the new one.
• A smaller new lease can silently cap the equipment you intended to move.

Measure whether the change actually helped

The first useful measurement for this page is to confirm one full supply cycle completes at the new location before closing the old. Capture it before the change and again after the relevant operating period. A screen that looks correct is not enough when schedules, deliveries, production, customer traffic, or status refreshes are involved. Use the remaining measurements to show whether the result persists, and keep costs separate from revenue so a temporary cash movement is not mistaken for sustainable performance.

• Confirm one full supply cycle completes at the new location before closing the old.
• Compare daily revenue before the move and after a full operating week.
• Track the total cost of the move against the reason you moved.
• Record which contracts and routes had to be rebuilt by hand.

Keep the answer accurate for the current version

The main version check for this topic is to confirm current moving fees in the running build rather than an older guide. Big Ambitions changed substantially during Early Access and reached version 1.0 in 2026, while search results still surface older interfaces, prices, capacities, and feature sets. Use official release information for what shipped, dated community evidence for practical workflows, and the current save for exact values. The checks below identify which claims require reverification before being repeated as current facts.

• Confirm current moving fees in the running build rather than an older guide.
• Recheck whether the in-game moving service covers the item types you own.
• Treat any equipment resale rate quoted by a guide as version-sensitive.
• Verify headquarters behaviour separately from a plain retail relocation.

Frequently asked questions