This document was created to showcase important differences between Evosus Legacy and LOU in the hopes it answers questions Evosus Legacy clients may have as you begin to consider migrating to our new cloud-based product, LOU.
This document is the eighth of eight. Each document, or section, should answer some of the most important questions about migrating from Evosus Legacy to LOU. This is a high level discussion and is not meant to be all-inclusive.
Speaking of releases and changes to come please check out the following resources:
- LOU Roadmap
- LOU Release Notes
Other Important Topics
Integrations in LOU
Multiple Legacy Databases vs LOU Databases
We have Legacy clients who have multiple databases. How does LOU handle that? Things to consider:
Departments
- Compare Pro to Enterprise (How many Departments can you set up in Pro vs Enterprise)
- What are the limitations of Departments? (hint: if a company has separate books, Departments won’t work)
- If your company has divisions/departments/businesses with individual books, you cannot use Departments in LOU. You would need an instance of LOU for each division/department/business with its own book.
- There isn’t a universal dashboard for multi-tenant owners, but you can quickly toggle between companies with the Change Company button in LOU.
- LOU doesn’t have a way to create a sandbox/test environment for the LOU company.
- What are some ways we would recommend handling that?