Many of our current firms previously used other case management systems like A1Law or Tritek before they switched to MerusCase. Their reasons for switching to Merus can vary (lower costs/overhead, better reliability, web access), but one common element across these legacy systems is migration: we can import case and contact data from most major systems to ours.

The way data are entered and stored in MerusCase is more structured compared to that of many of our competitors because fields in MerusCase need to be used in multiple places. Date of Injury in a case, for example, needs to be explicitly defined so it can also be referenced by auto-filled forms and templates. In contrast, other systems might allow adding/changing fields or leaving fields empty because they don't have or don't need this kind of cross-module information sharing.

When a firm with one of these legacy systems decides to switch to MerusCase, we make a lot of effort to faithfully import fields from their old system to ours. Depending on how rigidly or how loosely these legacy systems' data are structured, this can take a lot of difficult data translation: we might have to, for example, split up a Full Name field from a legacy system in to separate First and Last Name fields in Merus to support automatic merging of "Dear Mr/Mrs LastName" in our templates.

                                                  A case with no parties can return this error