How to Bring a Newly Acquired Location Into Your Operating View in 30 Days

The deal closes on a Friday. By Monday the new location is yours on paper and invisible in practice. Its sales figures arrive as a spreadsheet on the fifth of the following month. Its inventory sits in a legacy ERP that nobody at headquarters can log into. Its customers live in a local CRM, and its books close on a different calendar from everyone else's. Leadership is accountable for a site it cannot see.

The usual answer is a full migration: move everything onto the group's standard systems, then start reporting. Migrations are sometimes the right long-term call, but they are slow, and they put visibility at the end of the project instead of the beginning. For months, or longer, you manage a business unit by phone calls and month-end surprises.

This article lays out a different sequence: connect first, consolidate later. It covers how to integrate acquired business systems well enough to get a working operating view in 30 days, while the site keeps running on the tools its people already know. The same approach works for onboarding a new location you opened yourself, and for any multi-site systems integration where one more site has to join a group that already runs on a shared view.

Why a new location stays invisible for so long

Post-acquisition operations visibility fails for ordinary reasons, and none of them is a lack of effort.

The systems were chosen independently. The acquired business bought its ERP, CRM and dealer management system (DMS) for its own needs, years before you arrived. Fields, codes and definitions reflect those needs, not yours.

Reporting depends on a person, not a system. Somewhere there is an office manager who knows which export to run, which columns to delete and which numbers to correct by hand. When that person is on leave, the report doesn't arrive.

Visibility is treated as the reward for migrating. Nobody asks for a dashboard while the migration is "about to start," so the interim stretches out.

Nobody owns the gap. IT is handling email accounts and licences. Finance is focused on the first close. Operations wants numbers but doesn't know which system holds them.

Consider a group with twelve locations that acquires a thirteenth. The twelve report through a shared pipeline and a weekly stock view. The thirteenth sends a spreadsheet that takes someone two hours to reformat. Its "units in stock" figure includes items on hold, which the other twelve exclude. The group's totals are now slightly wrong, and no one can say by how much.

How to diagnose the gap

Before you build anything, find out how blind you actually are. A few checks, which take an afternoon, will tell you.

• Trace one customer. Pick someone who has dealt with both the new site and an existing one. Can you see both histories in one place? If not, you have two customers where you should have one.
• Trace one asset. Choose a vehicle, a part or a piece of equipment at the new site. Find its current location, status and cost without calling anyone.
• Ask for yesterday. What did the site sell, book and invoice yesterday? If the answer takes more than a few minutes, or comes from a person instead of a screen, the view is manual.
• Count the re-keying steps. Follow a number from the local system to the group report and count how many times someone retypes, pastes or reformats it.
• Find the single points of failure. List who holds credentials, who knows the export routine and who understands the local chart of accounts.

Write the results down. They become your baseline, and they make the priorities obvious. If the finance answer is slow but inventory is fine, start with finance.

What the gap costs

Missing visibility rarely announces itself as a line item. It shows up as small losses that accumulate.

Time. Someone re-keys data every week, usually a skilled person doing clerical work. Managers also spend meetings arguing about whose numbers are right instead of deciding anything.

Inventory. Say a part is sitting idle at the new site while a neighbouring location orders the same part from a supplier. With no shared stock view, no one knows. Capital stays tied up, and the customer waits longer than they needed to.

Lost deals. Enquiries that land in the local CRM don't flow into the group's pipeline, so they miss the follow-up rules and alerts the other sites rely on. A lead that would have been chased within the hour sits for two days.

Mistakes. When "closed," "sold" and "available" mean different things in different systems, consolidated figures mislead. Decisions get made on them anyway.

Burnout. The local manager spends evenings assembling reports, and the acquired team starts to feel like a second-class unit that headquarters only contacts to ask for numbers.

Customer frustration. A customer who bought from one of your sites turns up at the new one for service and is treated as a stranger. They have to explain their history again, and they notice.

None of these requires a dramatic failure. They are what a fragmented operation looks like day to day.

A 30-day plan for linking the new site

The target is a working operating view, not a finished integration. By day 30 you want trustworthy numbers on a shared screen, alerts that reach the right people, and a clear picture of what to consolidate later, if anything.

1. Days 1–5: Inventory the systems and name owners. List every system the site uses: legacy ERP, local CRM, DMS, finance package, spreadsheets, phone and messaging tools. For each, note who administers it, what data it holds, and whether it offers an API, a database connection, scheduled exports, or none of these. Assign one person on each side as the decision-maker.
2. Days 3–8: Choose a short list of measures. Pick eight to twelve that leadership will actually use: sales and bookings, open leads, stock on hand, aged inventory, open work orders, receivables, cash position. Resist adding more. A small set that is trusted beats a large set that is questioned.
3. Days 6–14: Get read-only access and map the data. Connect in read-only mode first, so the local team's operations are untouched. Then map the fields you need against your group definitions (more on this in the next section).
4. Days 12–20: Stand up the connections and the unified view. Pull the mapped data into a central layer on a regular schedule. Match customers, assets and orders so that each exists once at group level, even if the source systems still hold their own copies.
5. Days 18–25: Build the view and the alerts. Put the chosen measures on one screen alongside the other locations. Add alerts for the things that hurt when missed: leads uncontacted past a threshold, stock below minimum, invoices past due.
6. Days 25–30: Reconcile and review. Compare the central numbers to what the site's team believes is true. Fix mapping errors, agree on definitions, and record what is still manual. Then hold a first review with local and central leaders using only the shared view.

Expect rough edges. A legacy ERP with no API may need scheduled exports in the first month and a deeper connection later. That is acceptable, provided you label each number's freshness so nobody mistakes a daily extract for a live feed.

Data mapping decides whether anyone trusts the view

The connections are the visible part of the work. The mapping is the part that makes the numbers believable.

Start with the entities that matter most: customer, asset (vehicle, part, equipment or unit), order, location and account. For each, build a simple crosswalk document that records the source field, the group field, any transformation, and who approved it. A spreadsheet is fine at this stage. It also becomes useful documentation later, whatever you decide about migration.

The hard cases are always definitions. Take "available stock." At the acquired site it may include items reserved for customers. At your other sites it may not. "Closed deal" might mean a signed order in one CRM and a delivered, invoiced sale in another. In finance, the local chart of accounts will not line up with yours, so you need a mapping from local accounts to group reporting lines before consolidated margins mean anything.

Customer matching is the other trap. The same person may appear as "J. Alvarez," "Jon Alvarez" and an email address with no name. Decide up front which fields determine a match (email, phone, tax or company identifier) and what happens when confidence is low. Sending uncertain matches to a person for review is better than merging records automatically and creating errors that are hard to undo.

Finally, keep the mapping with the business, not buried in code. When the next acquisition arrives, you will want to reuse the pattern, and your own people should be able to read it.

Mistakes that slow the 30 days down

Trying to fix every process at once. The first month is for seeing. Process redesign comes after you can see what is broken, and some of it will turn out not to matter.

Writing back too early. Pushing data into the acquired site's systems before you understand them risks corrupting records and losing the local team's goodwill. Read first, then automate carefully.

Ignoring the local team. The people at the site know why the odd field exists and which report really matters. Involve them in the mapping, and show them the view as soon as it works. They should be its first users, not its subjects.

Chasing real-time everywhere. Some measures need to be live, such as lead response and stock-outs. Others, like margin by month, don't. Match the refresh rate to the decision.

Leaving ownership vague. Once the view exists, someone must own its accuracy, handle changes when the local system is upgraded, and respond when a connection breaks.

How Ninjaz and the Ninjaz Operating Platform fit

The Ninjaz Group is a managed-services partner for multi-location enterprises, and this kind of work sits across its three service layers. Managed Transformation covers strategy, design and build. Managed Link is the integration layer Ninjaz builds, owns and maintains between your existing systems. Managed Business Operations covers managed IT and day-to-day running after go-live.

An engagement typically follows three steps. Blueprint maps the operation and finds where work is done twice, where data goes stale and where money leaks. You keep the map. Build & Link connects what you already have, with no rip-and-replace, so software you have already paid for stays in place. Operate keeps it running after go-live.

The technical core is the Ninjaz Operating Platform, an integration hub that Ninjaz deploys and runs. It has connectors to the kinds of systems a new site is likely to bring: CRM, ERP, DMS, inventory and warehouse systems, POS, helpdesk, telephony, messaging channels and finance. A unified data layer holds one record per customer, asset and order. The Command Center then shows live KPIs and alerts across locations, so the new site appears next to the others instead of in a separate report. Inventory and asset views span sites, and role-based access with an audit trail helps with governance when a newly joined team needs controlled visibility.

Some limits are worth stating plainly. Connecting systems does not remove every process problem, and a site running a poorly maintained legacy ERP will still have one. The platform gives you a clear view of that problem and a basis for deciding what to retire, keep or migrate. Some systems are easier to connect than others, and the first month's timeline depends on access, data quality and how quickly decisions get made on your side. The aim is to move visibility from the end of the project to the beginning.

Start with the view, then decide what to migrate

A newly acquired or newly opened location doesn't have to stay in the dark while a long migration plan takes shape. Link its systems to central oversight, agree on definitions, and put its numbers beside everyone else's within a month. Then use what you've learned to decide, with evidence, what should be consolidated, what can stay, and what should be retired.

If you're preparing for an acquisition or already have a site that isn't visible, book a consultation and we'll walk through your systems and where a 30-day view would start. If you'd rather see what the finished picture looks like first, take a look at the platform demo.