iyibir
SolutionsAIProductsCloudServicesCompanyResourcesContactGet Consulting
All resources
Logo ERP7 min read

When does support for Logo Tiger and GO end? The timeline and what to do

Logo's migration timeline is now clear: new sales of the Tiger and GO families closed on 3 September 2026, and the deadline is 3 September 2027. In between, your product keeps running and LEM can be renewed — but only patch updates are released. This post lays out the timeline as it stands and proposes a plan for the time that is left.

The short answer: new sales of the Tiger and GO families closed on 3 September 2026, and the deadline for existing users is 3 September 2027. Between those two dates your product keeps running and your LEM membership can be renewed; however, no new versions or features are released — only patch updates. After 3 September 2027, moving to a Logo Edge series becomes mandatory.

The point of this post is not to turn a timeline into a pressure tactic. It is to state the dates as they are, separate what changes from what does not, and propose a concrete plan for the time that remains.

What the timeline says

  • 3 September 2026 — new licence sales for the Tiger 3, Tiger Wings, GO 3 and GO Wings families ended. The date closes new sales only; existing installations were not affected.
  • 3 September 2026 – 3 September 2027 — the products stay in use and LEM can be renewed. No new versions or features are released during this period; only patch updates.
  • 3 September 2027 — the deadline. After this date the current product is no longer carried forward and moving to a Logo Edge series becomes mandatory.

What does not happen on these dates

Let us clear the first worries out of the way. Nothing stopped on 3 September 2026: no installation halted, no data was lost, nobody's screen went dark. A business running Tiger or GO today works exactly as it did yesterday. What changed is the product's commercial life cycle: new sales closed, and the family entered a maintenance period in which it no longer receives new features.

By the same token, the timeline does not mean everyone should migrate tomorrow. There is a planning window — and how that window is used is what decides whether the migration is calm or rushed.

What really changes: the patch-only period

The practical meaning of the period between the two dates is easy to miss. Patch-only updates mean the product line's roadmap has stopped: a feature you may have been waiting for, a screen improvement, a module extension — none of those will arrive on this line any more. Patches fix defects; they do not move the product forward.

The sharpest consequence is on the e-transformation side. When Turkish legislation changes, Logo usually delivers the change through a version update. So if a legislative change in the coming period requires a new version, how that is covered for your product and your version needs to be established in advance. If you use e-Invoice, e-Archive or e-Waybill, this is a check to run before the migration plan — not something to leave to assumption, but something to look at against your licence and version status.

Should I renew LEM?

LEM can be renewed up to 3 September 2027, and renewing keeps your access to the patches released until then. But the decision is no longer made on its own: LEM's core promise — the right to use new versions without paying a further licence fee — is in practice limited to patches on a product family that no longer publishes new versions.

So “should I renew LEM” is now answered at the same table as “where in the timeline do I place the migration”. The right answer differs for a business planning to move soon and one that prefers to stay on its current setup until the deadline.

Less than a year to the deadline — why that is not “plenty of time”

At first glance the remaining time looks comfortable, but a migration is not a single installation day. Each of the steps in between wants its own slot in the calendar:

  • Current installation analysis — which product, which modules, how many users; customisations and integrations are mapped
  • Series and package decision — the analysis establishes which package corresponds to your setup
  • Data and customisation transfer — account, inventory and accounting data move, and so do parameters, permissions and document layouts
  • Testing — custom reports, e-transformation submissions and critical screens are verified one by one in the new structure
  • Training and go-live — users start working with the new interface, and support continues after the switch

On top of that sits the business's own calendar: year-end closing, stocktaking, peak season and the eve of an expected legislative change are not good windows for a migration. Once those are removed, less than a year comes down in practice to a handful of workable windows. The right approach is not to aim at the deadline but to pick one of those windows.

Which product corresponds to what

Migrating does not mean moving to an entirely different ERP. The counterpart of the Tiger product family is Logo Edge T-Series, and the counterpart of the j-Platform family is J-Series — the same ERP operation, continued on a next-generation infrastructure and package structure. Choosing between the T-Series Basic, Standard and Enterprise packages is a separate decision: what separates them is user capacity and the modules included in the main package, so the choice is made by looking at how you use the system today.

We have collected the scope of the series, the differences between the packages and the migration timeline on a single page: Explore the Logo Edge page

Where to start

There is low-cost preparation you can do before deciding on a migration, and it pays off either way. With these four items in hand, both the migration plan and the LEM decision become far clearer:

  • Licence inventory — which product, which version, how many users, which modules, and your LEM status
  • Customisation and integration list — custom reports, forms, external system connections, and who built them
  • e-Transformation check — which e-transformation processes you use and the current state of your integration settings
  • Calendar window — the two or three quietest periods for the business over the coming year

At iyibir Yazılım we compile this inventory on your behalf and establish together which window and which package are right for your migration. We are equally clear about the cases where postponing the decision is the better call — the timeline is data to plan against, not an argument for urgency.

You can see the scope of our analysis, implementation, data transfer, training and go-live services here: Explore our services

Let's explore this topic together for your business.

Schedule a meeting