Skip to content
Switching from AJS

Evaluate a Controlled Move from AJS to Lexuno

Assess a potential move from AJS through source inspection, agreed mapping, non-destructive dry runs, exception review, reconciliation, and authorised acceptance.

No assumed connector Scoped mapping Reconciled totals Authorised cutover
Operational Scope

What to examine in switching from ajs.

Each capability should be evaluated against the firm's real records, permissions, review duties, and failure conditions.

Source inspection

Source inspection remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.

  • Connected source records
  • Named review authority
  • Visible exceptions

Agreed mapping

Agreed mapping remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.

  • Connected source records
  • Named review authority
  • Visible exceptions

Dry-run exceptions

Dry-run exceptions remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.

  • Connected source records
  • Named review authority
  • Visible exceptions

Accepted reconciliation

Accepted reconciliation remains connected to the wider matter or practice workflow, with responsibility and exceptions kept visible.

  • Connected source records
  • Named review authority
  • Visible exceptions
Controlled Workflow

Move from source evidence to an accountable outcome.

The exact configuration depends on the firm's operating model, enabled workspaces, data, and assigned authorities.

01

Define scope

Confirm the relevant matters, records, people, roles, branches, and decision boundaries before work starts.

02

Connect evidence

Attach the source records and context needed to understand, review, and reconcile the work.

03

Review exceptions

Route incomplete, conflicting, unavailable, or permission-restricted states to the responsible person.

04

Record the outcome

Preserve the accepted result, remaining exceptions, responsible authority, and next action.

Evidence Boundary

Treat product evidence as scoped evidence.

Migration coverage is confirmed only after the source system, export format, record quality, attachments, financial balances, and exceptions have been inspected. No vendor import or lossless outcome is assumed.

Server authority

Navigation and client input never grant access; the relevant tenant, branch, matter, record, and capability must be re-authorised.

Truthful states

Loading, empty, unavailable, permission-denied, failed, and retryable outcomes must remain distinguishable from success.

Human responsibility

Software can organise evidence and workflow, but professional, regulatory, accounting, and operational decisions remain with authorised people.

Current configuration

Confirm the deployed environment, enabled providers, configured controls, and supported data before relying on a capability.

Connected Guidance

Continue through the Lexuno platform.

Explore the product, operational controls, and connected workspaces related to this decision.

Switching from AJS FAQ

Frequently Asked Questions

Practical questions about switching from ajs, authority, evidence, and product scope.

What does Lexuno mean by switching from ajs?

Assess a potential move from AJS through source inspection, agreed mapping, non-destructive dry runs, exception review, reconciliation, and authorised acceptance.

Does this page promise that every workflow is enabled for every firm?

No. Availability and behavior depend on the current product release, plan, configuration, permissions, providers, and the firm's accepted operating model.

How should a firm evaluate this capability?

Use representative records and end-to-end scenarios, including empty, permission-denied, provider-unavailable, failed, exception, and reconciliation states.

Does Lexuno replace professional advice or accountable review?

No. Lexuno provides operational software. Legal, regulatory, accounting, security, and professional decisions remain separate responsibilities.

How should access be verified?

Test the exact tenant, branch, matter, record, role, and capability boundaries server-side. Visible navigation alone is not authorisation evidence.

Evaluate switching from ajs against your real operating model.

Use representative workflows and request current product evidence for the scope that matters to your firm.