Migration from Dubsado
Migrate from Dubsado to BisHub
A practical migration guide for service providers moving from client workflows to full operations: what to move first, how to validate data, and how to connect customers, work, files, invoices, online payments, communication, and reports in BisHub.
Migration strategy
Dubsado migrations usually involve forms, client records, projects, workflows, proposals, invoices, payment records, files, templates, and client portal habits. The safest migration is staged: preserve clients, forms, workflow steps, projects, proposals, invoices, payments, files, templates, and follow-up rules, review imported data before committing, and move daily operations only after the team has tested the workflow in BisHub. Do not copy every old workflow step blindly. Use the migration to simplify how customers become paid work.
How to migrate without disrupting work
Use this as a practical cutover plan. The exact exports depend on your current system, but the validation sequence should stay the same.
- Step 01
Audit current data
List the records your team still uses every week. Prioritize active customers, open work, unpaid invoices, current files, team members, services, and payment status before older history.
- Step 02
Export from Dubsado
Use the exports your current system provides, then clean columns, normalize names, remove duplicate contacts, and separate clients, jobs, invoices, payments, services, users, files, and notes.
- Step 03
Map and review in BisHub
Bring the staged data into BisHub through CSV/import workflows, map fields, review the preview, and commit records only after the office team confirms the structure.
- Step 04
Run a controlled cutover
Run both systems for a short cutover window, test booking, communication, estimates, invoices, online payments, reports, and team access, then move daily work into BisHub.
Move this first
- Active clients, forms, projects, workflow steps, proposals, invoices, payment status, files, and templates.
- Intake questions that should become leads, booking requests, customer uploads, tasks, or client fields.
- Automations that still save time, including notifications, email follow-up, SMS follow-up, report automation, and task rules.
Validation checklist
Before the old workflow is turned off, check the records that affect customers, teams, invoices, payments, and reporting.
Workflow rebuild
Recreate only the automations that matter as BisHub workflows, notifications, email automation, SMS automation, and tasks.
Client record quality
Check forms, files, invoices, payments, notes, and active project details after import.
Client records
Confirm names, emails, phone numbers, addresses, contacts, tags, and duplicate handling before the team starts new work.
Open work
Check active projects, work items, tasks, schedules, files, assignments, and notes against the current system.
Invoices and payments
Verify invoice numbers, balances, payment status, payment accounts, revenue, expenses, and unpaid work.
Team access
Test roles, permissions, organization isolation, team assignments, clock-in access, and reporting visibility.
BisHub modules to set up during migration
Set these up early so imported records have a clear operational home from day one.
Leads
Set up Leads to give imported records a clear operational home for daily work, finance, communication, and reporting.
Learn moreWorkflow automation
Set up Workflow automation to give imported records a clear operational home for daily work, finance, communication, and reporting.
Learn moreProposals
Set up Proposals to keep sales scope, approvals, pricing, files, and invoice handoff connected after import.
Learn moreInvoices
Set up Invoices to validate balances, online payment status, payment accounts, revenue, and collection follow-up.
Learn more
Migration FAQ
Can we migrate from Dubsado to BisHub?
Yes. Start with the exports your current system provides, then use BisHub import workflows to map and review staged data before committing it to active operations.
What should we move first?
Move active customers, open work, unpaid invoices, current files, team users, service lists, and payment status first. Older archive history can move later if the team still searches it.
Do we need to migrate every historical record?
Usually no. A safer rollout starts with current operations, then adds history only where it improves support, reporting, compliance, or customer follow-up.
How do payments work after migration?
BisHub connects estimates, proposals, invoices, online payments, payment tracking, payment accounts, revenue tracking, profit tracking, and financial reports.
Can files and documents move into BisHub?
Yes. Teams can store files with previews, PDF preview, video preview, image gallery, OCR, AI document analysis, AI summaries, metadata extraction, and global file search.
How should we avoid breaking daily operations?
Run a short pilot, test booking, communication, files, estimates, invoices, payments, reports, permissions, and team access, then cut over one team or workflow at a time.
Plan your Dubsado migration
Start with active customers, open work, unpaid invoices, current files, team users, and payment status. Then expand the migration after the workflow is proven.