Entry types
Firms do not need to treat every rollout as migration. The starting point depends on whether visibility, structured inquiries, or broader platform operation should be relieved first.
- Profile: visibility and contact path without internal migration
- Intake: structured first information and document upload in the standard process
- Platform: digital file foundation, team roles, and further workflows
What can start without migration
Profile, standard contact, digital intake forms, an initial role structure, and new mandate inquiries can start without historical data transfer. Existing practice software can continue for accounting, deadlines, beA, or specialist workflows at first.
- No full replacement required before value starts
- No blanket transfer of historical files
- Existing systems become the input to the current-state review
Current-state review
Before a proposal, Jurono reviews existing systems, data sources, file formats, file logic, roles, deadlines, locations, privacy requirements, and go-live risks. No migration is promised without this review.
- Review source and export format
- Assess data quality and duplicates
- Name owners and approvals
Introduction plan
The introduction plan defines order, scope, responsibilities, and restrictions. It separates configuration from data transfer and records what is included in the package and what needs a proposal.
- Configure profile, intake, roles, and notifications
- Decide which processes go live first
- Schedule training, testing, and go-live
Supported migration
Verifiably supported scope includes structured master-data and profile-data imports, document transfer after source and format review, profile content, and intake/team configuration. Legacy systems, historical file holdings, and vendor formats are assessed individually.
- Supported: CSV/table mappings, structured profile data, reviewed document packages
- After review: data from practice software, DMS, website, or directory exports
- Not promised broadly: full historical file or vendor-system migration
Roles and responsibilities
Jurono owns technical configuration, import preparation, implementation planning, and product support. The firm owns data release, statutory retention decisions, legal prioritisation, internal roles, and acceptance.
- Jurono: setup, mapping, test import, training, and support
- Firm: data approval, privacy review, professional acceptance, and team communication
- Joint decision: go-live timing and restrictions
Training and go-live
Training focuses on the concrete starting processes, not an abstract product tour. Before go-live, roles, intake flows, notifications, procurement documents, and fallback paths are checked.
- Team training for lawyers, paralegals, and administrators
- Test with realistic sample inquiries
- Go-live support and follow-up review
Pricing and procurement
White-Glove is not a flat fee and not automatically included in every package. Effort, term, support level, and migration are proposed after the current-state review. Privacy and security review belong before production mandate data.
