Skip to content

Upgrading an Existing Installation

Upgrade from version 1 or below

Database changes

Options on lead.leadstatus

  • Change key wip => qualify
  • Change key qualified => convert

Update local names according to our latest LIP package.

Renaming Fields

  • Change name wipdate => qualifydate
  • Change name qualifieddate => convertdate

Update local names according to our latest LIP package.

Lime admin

Option visualizer config

If you've haven't changed anything here just import our template.

Otherwise go through each changed option mentioned above.

Status flow config

If you've haven't changed anything here just import our template.

Otherwise go through each changed option mentioned above.

View config

If you've haven't changed anything here just import our template.

Make sure to change in all views that contains any of the properties mentioned above.

Migrating from Custom Limeobjects to Automations

The @lead_decorators.lead() decorator is deprecated and will be removed in a future major version. Follow these steps to migrate to Automations:

  1. Download the lead automation JSON files from the installation guide and add them via Lime Admin -> System -> Automations -> + automation -> switch to code editor -> paste the JSON -> save and verify it looks correct -> set the automation to active.

  2. Verify the automations work correctly. Test status changes, name/phone formatting, and any automated flow features you use.

  3. Remove the @lead_decorators.lead() decorator from your custom limeobject for lead. If the decorator was the only reason for the custom limeobject, you can remove the entire custom limeobject class. The lead limetype and all its data remain in the database. Removing the custom limeobject code only removes the Python-side business logic hooks, which are now handled by Automations instead.

Info

Both approaches can coexist temporarily. Automations run before before_update(), so if both are active, the automations will set values first and then the decorator will run in before_update. This should not cause conflicts but may result in redundant processing.