Source assessment
Inventory the available exports, file formats, data owners, record counts, and legal retention needs.
- Export inventory
- Dataset classification
- Scope and ownership
Switching to Lexuno
Move to Lexuno Without Treating Migration as a File Upload
Assess the source, map each dataset, run a non-destructive dry run, resolve exceptions, reconcile balances, and approve cutover with evidence.
Source assessment Field mapping Dry runs Reconciliation gates
Migration Controls
A controlled process from source export to accepted destination.
Vendor-specific support and timing are confirmed only after Lexuno assesses the actual export, fields, volumes, and reconciliation requirements.
Mapping and transformation
Map source columns to destination fields with explicit handling for unknown, duplicate, and invalid values.
- Field mapping
- Format normalisation
- Exception lists
Dry-run validation
Simulate the import without presenting migrated records as accepted operational data.
- Non-destructive runs
- Duplicate detection
- Blocking errors
Reconciliation and sign-off
Compare counts and sensitive balances, resolve variances, and record acceptance before cutover.
- Entity counts
- Financial reconciliation
- Signed acceptance
Four-Stage Path
Assess, map, prove, then migrate.
A migration becomes trustworthy when each stage produces evidence for the next.
Assess
Confirm source access, export quality, scope, retention, risks, and accountable owners.
Map
Approve dataset and field mappings, transformations, identities, and exception rules.
Dry run
Import into an isolated validation path and reconcile counts, balances, and relationships.
Approve cutover
Resolve blockers, sign the reconciliation evidence, and schedule the governed transition.
Migration Boundary
What Lexuno will not promise before assessment.
A responsible migration page distinguishes an implemented process from an unverified vendor or production claim.
An adapter in source code does not prove that every vendor version or customer export can migrate automatically.
Completeness must be demonstrated through counts, exceptions, relationships, samples, and financial reconciliations.
Duration depends on exports, volumes, cleansing, mappings, approvals, and unresolved source issues.
Source records and mandatory retention evidence remain protected throughout assessment and cutover.
Switching to Lexuno FAQ
Frequently Asked Questions
Questions about source exports, dry runs, vendor support, reconciliation, and migration acceptance.
Can Lexuno migrate data from any legal software automatically?
No universal migration should be promised before the actual export, vendor version, fields, volumes, and data quality have been assessed.
Does Lexuno support CSV and spreadsheet assessment?
The migration architecture includes generic CSV and workbook pathways, but support for a particular export is confirmed through assessment and a successful dry run.
How is a financial migration accepted?
Acceptance should include record counts, exception resolution, general-ledger checks where applicable, debtors, WIP, trust balances, and responsible sign-off.
How long does migration take?
Timing depends on source access, export quality, dataset volume, mapping complexity, cleansing, dry-run results, reconciliation, and approval availability.
Will the original system be deleted?
A migration plan should preserve source access and required records until retention, acceptance, rollback, and cutover decisions are formally resolved.
Start with the export you actually have.
Request a migration assessment before relying on vendor, format, completeness, or timeline assumptions.