Operations / Field guide
Plan a dojo CRM migration without losing record ownership
A migration is a data and staff-process project. Before choosing a cutover date, decide what information belongs in the new system, who can authorize moving it, and how the team will confirm the result.
By SenseiStackCRM Editorial · Product guidance from the software publisher
Inventory the records you actually need
List student profiles, guardian relationships, programs, rank history, attendance, waivers, and billing references. Separate active records from historical material. Check the source system’s available export formats and the destination’s supported import process.
Do not assume payment credentials or signed documents can be moved like a spreadsheet. Confirm the supported process with the relevant provider. This guide describes preparation; it does not promise a one-click SenseiStackCRM import for every source system.
Map fields before copying data
Create a field map with source column, destination field, required format, and responsible reviewer. Pay particular attention to student identity, guardian links, dates, and program names. Avoid using a shared family email as the sole student identifier.
Review possible duplicates with a human who knows the roster. Keep a record of merge decisions and unresolved questions rather than silently discarding rows that do not fit.
Validate a small sample end to end
Use a representative sample: one adult, siblings with a guardian, a student in several programs, and a record with historical notes. Verify field values and permissions in the destination before scaling the process.
Count source and destination records, then inspect relationships and meaningful values. Matching row counts alone does not prove that a guardian is linked to the right child or a rank date survived correctly.
Plan the handover
Choose a clear point after which staff enter new work in the destination system. Document where historical records remain accessible and who handles corrections. Keep an authorized backup according to your business’s retention requirements.
Introduce staff workflows before inviting all families. Confirm schedules, access, and communication ownership so the first week is a controlled rollout rather than a simultaneous data cleanup and support launch.
Put it into practice
- Confirm authority and export/import support.
- Map fields and student identifiers.
- Review duplicates and family relationships.
- Validate a representative sample.
- Document cutover, backup, and correction ownership.