Migration and software
A careful migration checklist for a Dubsado-based studio
Editorial team · Reviewed
A studio with established Dubsado workflows has more to move than a contact list. Preserve the business decisions embedded in forms, stages and messages even when the destination represents them differently.
A practical sequence
- Inventory the forms, templates, stage rules and scheduled actions you rely on.
- Export the available records and keep accepted documents independently.
- Translate each active workflow into explicit triggers, waits, actions and stop conditions.
- Test the rebuilt journey with sample recipients and provider test modes before enabling it.
Work through an example
A follow-up sequence pauses when a client replies in the old process. Rebuilding only its timed messages would miss the most important behavior. The migration rehearsal includes a reply to prove that later messages stop.
Where judgement matters
A visual similarity between workflow editors is not compatibility. Review supported conditions, field mappings and message state individually. Keep a written list of manual bridges so the team does not assume an unfinished automation is running.
Make it usable
Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A Dubsado account may contain forms, workflows, projects and business-specific field names. Before switching, identify which information is available in the actual export and which behavior must be deliberately rebuilt. An import of contact rows does not demonstrate that an automation or client portal has been migrated.
| Decision | Why it matters |
|---|---|
| Map meanings rather than similar labels. | A field named status may represent a pipeline stage, archive state or payment condition. |
| Rebuild automation from reviewed decisions. | Copying a sequence without its stop conditions can contact the wrong clients after migration. |
| Verify one complete journey before bulk import. | The useful test starts with an inquiry and ends with the expected preserved records and no duplicate side effects. |
Make one usable artifact
Document one source workflow as trigger, conditions, waits, approvals, actions and stop rules. Rehearse its intended behavior with fictional contacts in the destination.
Then test the difficult case
A source field has no equivalent. Keep it in a lossless artifact or an explicitly mapped custom field, and disclose the limitation before moving live work.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.