Knowledgebase

Avoiding Vendor Lock-In Print

  • businesssystems, business, migration, guide, howto, solution, zillionkinghost, hosting
  • 0

Preserving the ability to leave.

WHAT LOCK-IN MEANS

Switching being prohibitively difficult or expensive.

WHAT CREATES IT

Data in proprietary formats Customisation that cannot be reproduced Integration built to one vendor's interfaces Process designed entirely around the product Contractual terms

WHAT TO ESTABLISH BEFORE COMMITTING

That you can export all your data In what format Whether historical detail is included Whether it costs anything

WHY HISTORICAL DETAIL SPECIFICALLY

Exports frequently provide current balances rather than transaction history.

WHAT TO TEST

An export, during the trial period.

WHAT TO REDUCE DEPENDENCE THROUGH

Standard interfaces rather than proprietary ones Integration through an intermediate layer Documentation of every customisation

WHAT TO ACCEPT

That some lock-in is unavoidable, and is the cost of integration.

WHAT TO DECIDE

How much is acceptable for the benefit.

WHAT CONTRACTUAL PROTECTION TO SEEK

Data export rights Reasonable notice on termination Assistance with transition Continuation if the vendor is acquired

WHY ACQUISITION MATTERS

Products are discontinued after acquisition regularly.

WHAT TO MAINTAIN

Your own record of configuration and customisation.

WHY

It is what makes migration possible later.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot