Switch to DispHub
Plan your move
to DispHub
Start with your current workflow, data and launch requirements. Together we define the setup, scope of migration and sequence for bringing your team onto DispHub.
Agree each stage before the switch
The plan depends on your service. We clarify the data, people and external services involved before setting a launch date.
Review the current operation
Describe your city, fleet, booking channels, services and tariffs. Identify what the team needs to keep and what should change.
Define data and setup
Review the export available from your current system. Agree the records that can be transferred, the required format and the DispHub settings for your service.
Prepare apps and team
Prepare your logo and colours, identify the people responsible for dispatch and drivers, and agree how the team will learn the workflow. Confirm any payment or other provider requirements separately.
Agree checks and launch
Agree which bookings, tariffs and team actions to check, who confirms readiness and when to switch. Discuss whether a limited pilot or use alongside the current system is suitable for your setup.
What data needs to move?
Bring a list of the records you need. Transferability is checked against the available export and the destination fields; this list is a discussion brief, not a promise to import every record.
People and vehicles
Customer records, drivers and vehicles you want to use in the new system.
Operating settings
Tariffs, service areas, vehicle classes and additional services that need to be configured.
History and accounts
Order history, corporate accounts and balances require a separate review of their structure and availability.
Prepare for the first conversation
- Country, city, fleet size and services you provide.
- Current software and information about available export formats.
- Your tariffs, booking channels, logo and brand colours.
- A contact person, preferred launch period and any special requirements.
The launch date follows the agreed scope
Data preparation, required development, app publication and external provider setup can affect the schedule. Confirm these dependencies before setting the date for your team.
Full package · one-time
$2,000Your brand in four apps
A one-time $500 per app: passenger Android, passenger iOS, driver Android and driver iOS. The full $2,000 package includes your logo and colours, admin-panel branding and the dispatch workspace.
App branding is a one-time launch cost. The scope and terms of data transfer, team training, integrations and any individual development are agreed for your project before work starts.
Pay as your fleet completes orders
When a company creates and completes an order itself, it pays DispHub 1% of the full order value once. When the order is passed to another company and completed by that company, the company that passed it on and the company that completed it each pay DispHub 1% of the full value of that order. No subscription or per-driver fees.
Support and planned updates included
Before you get started
Can we keep our telephone number?
Tell us which telephony provider and number you use. The connection options and any changes are checked with the provider before being included in the launch plan.
Can we move all our historical data?
The scope depends on the export from your current software and the structure of the records. We confirm which data can be transferred and which needs to remain in the previous archive after reviewing it.
Is a pilot and team training included?
The pilot format, training, responsibilities and their commercial terms are agreed for your deployment. Describe your team and shift structure so these items can be included in the proposal.
Let’s plan your launch
Tell us about your service and current system. We can use that information to discuss the next steps and the scope of your DispHub setup.