What moves
Everything the seller hands you has a place to land.
Exports, spreadsheets, a legacy database, a filing cabinet. Each record type maps to a PRO Enterprise object that already carries a branch.
Plan for each service division and every branch.
Portable sanitation, septic, roll-off and fencing have different assets, service schedules and billing rules. We map those workflows alongside the yards and teams that run them.
Companies
Define the ownership, invoicing and accounting boundaries. Separate-company books and consolidation requirements are scoped during discovery.
Service divisions
Identify the service lines, contract rules, asset types and reports each team needs.
Branches and yards
Map local customers, routes, inventory and team access, including the visibility head office needs.
Your proposal records what is shared, what stays separate, and which configuration or integrations are required. A branch is not a substitute for a legal entity.
Discuss your operating structureImplementation example · customer name withheld
Bringing another branch into a regional operation.
A multi-branch portable sanitation operator needed its customer, site and dispatch records brought into PRO. The recorded import for one branch included more than 7,000 customers, 24,000 site locations, 70 saved routes and 1,900 work orders.
What moved
Customer and site records, saved routes, route stops, work orders and user accounts were included in the branch rollout.
What needed attention
Driver and route branch assignments were checked and corrected so the records belonged to the right operating branch.
What stayed separate
Recurring contracts were handled in a separate import workstream. The branch import was one part of the implementation.
The lesson for an acquisition: define the record groups, branch assignments and billing workstreams before setting the cutover plan. Each source system needs its own scope and acceptance checks.
Discuss your acquisitionAgree the checks before the cutover.
The migration plan defines the records to move, the acceptance checks and the people responsible at each stage.
- Inventory the sourceList the customers, sites, units, contracts, balances and history to move, with record counts and source formats.
- Map the operationAgree the company and branch boundaries, service divisions, numbering, price lists, permissions and integrations.
- Test and reconcileReview a trial import and compare the agreed record counts and financial balances. Resolve exceptions and agree whether a parallel billing cycle is needed.
- Approve the cutoverAgree acceptance checks, the cutover date, responsibilities and a fallback plan before retiring the old workflow.
- Train and reviewTrain the teams on their workflows and check the first dispatch, billing and reporting runs after go-live.
What the controller gets
Give the controller a clear view of the operation.
Branch reporting
Review revenue, units on rent and receivables by branch. Define division-level and company-level reporting requirements before implementation.
Accounting that ties
Agree the accounting boundaries, source of record and QuickBooks integration scope, including how balances will be reconciled.
Branch-level permissions
The acquired team sees its own customers, routes and invoices. Head office sees everything. You decide when that changes.
Keep the mapping, branch configuration and training plan for the next acquisition. Each new source system and accounting boundary is reviewed before reusing the plan.
Closing on a company?
Tell us what the seller runs today and how many branches you will have after close. We come back with a migration plan and a proposal.