Emphasize Re-Implementation

When deciding whether to undertake a migration or a system re-implementation, our advice is to go for re-implementation.

5 reasons why re-implementation is a better choice:

• A new system runs a lower risk of corruption from potentially inaccurate data than an older system.
• A new system is usually more flexible and runs faster.
• New versions of LS Central may include functionality in the standard version that replaces old customizations. The advantages are better integration, stability, performance and so on.
• If the customer’s current system is some version behind the current one, migration will require several upgrade steps and involve significant re-engineering of the business and relevant customizations.
• Migrating data from one database to another is a huge and complex task, even if the data structures are the same. Do not underestimate the complexity of data migration. 

We recommend you focus mostly on bringing over master records, opening balances and quantities.

Leave behind the legacy of old redundant code, data and so on. Bringing old data into the new solution is a bad idea. It makes management more confusing and maintenance more burdensome. Unless everything is well documented, it often gets to the point where no one is sure what does what.

When to consider migration?

If the customer’s current system is an older version of LS Nav or LS Central on-premises, you should only consider migration if:

• Data is more important than cost (in the SaaS version, you can have 80 GB of data).
• Time is not an issue. Keep in mind that upgrading might take substantially longer.

In the case of migration, we strongly advise you to review the data before migration.

Which elements might be left behind?

The value of old data? 

Now is the time to make the decision.