[ Omega to Microsoft SQL Server ]

This means Omega typically runs as desktop software within the firm's office on employee PCs, however, some firms may use an IT provider that hosts Omega on a remote server in a remote datacenter. In this scenario, firm members may RDP, TeamViewer, RemoteApp, or Screen Connect to a remote PC where they access Omega. In this scenario, some people may say that Omega runs 'in the cloud', however, it is really just a desktop application running on someone else's equipment.

General practice management systems store a wide variety of data instrumental to running many kinds of law firms.

​

​

Universal Migrator has heavily automated the process of moving data from Omega. Because of this, it is often easier and cheaper for a consultant to move all the data from Omega instead of just some of the data.

If someone came to a law firm and said "I have a simple issue. What will it cost to represent me?" most firms could provide a competitive, ball-park estimate.

However, if someone else had the same issue, but wanted two firms to each handle half the project, and wanted the two firms to coordinate with each other, and wanted everything the two firms did to perfectly align with each other, the simple issue would be way more complex and expensive.

Document Migrations are similar.

While many companies provide free data migrations (contacts, matters, notes, etc.), if you intend to migrate documents, the document migration will often be much cheaper if you have the document migrator do the data migration as well.

(Most document migrators provide free data migrations and provide a discount on the document migration if they do the free data migration.)

The Migration Specialist will need an Administrator username and password into Omega in order to extract your data.

The Migration Specialist will need the Administrator username and password into the Omega database server in order to extract your data.
This should be the Administrator account and not another account that has administrative access.

Because Omega is a desktop-based application and documents represent a majority of the data that will need to be transferred, the computer used for the migration should be near the same device that stores the documents.

A member of the firm will need to complete a small spreadsheet mapping users from Omega to users in the new system.

​

Backups from Omega include the financial transactions (money in/out) that make up trust financials for matters. This allows recreating ledger history in compatible systems.

The Migration Specialist is the person who will be performing this migration. They may be a member of Universal Migrator's own Internal Migration Team or any IT professional who has completed the Universal Consultant training program.

The Firm Administrator is a member of the law firm who can serve as a dedicated point of contact, make decisions, and answer any questions the Migration Consultant may have. This person should be readily available and is typically the managing partner or office manager of the firm.

The Firm IT Administrator is the person responsible for setting up and managing the firm's IT equipment. Sometimes this is an employee of the firm but usually this is an employee of a third-party IT services provider.

​

​

​

​

With certain vendors, submitting a Notice of Termination/Non-Renewal can prompt a shift in cooperation: some will restrict or revoke export and backup capabilities, or limit the volume of data you're able to download, making migration more difficult.
To guard against this, best practice with any vendor, including Omega, is to withhold notice until you've been fully live on your new system for at least 30 days. In practice, this means your migration should be complete approximately 45 days before your notice deadline.