Skip to main content

Hey everyone,

I wanted to see if anyone else has run into this problem with ScalePad Lifecycle Manager.

We recently had a client rename in ConnectWise, and noticed that Lifecycle Manager essentially treated it like a brand-new client. I reached out to ScalePad support, and their response was that the product is working as designed and we should just rename the client back.

Yeah… that ain’t gonna work.

Here’s why:

  • The Client ID in ConnectWise doesn’t change when a company is renamed. That’s the persistent identifier that tools like Lifecycle Manager should be keying off of, not the display name.

  • Telling us to “rename it back” completely breaks operational workflows. Clients rebrand, get acquired, merge, or simply change names — and reverting back is not an option in the real world.

  • This creates unnecessary data fragmentation and additional manual cleanup in Lifecycle Manager.

I’m curious — has anyone else run into this issue? How are you handling it?

In my opinion, ScalePad should fix this feature in Lifecycle Manager so it properly recognizes client renames based on Client ID, not just the display name. This would save a lot of headaches for MSPs and keep data consistent across platforms.

Would love to hear others’ experiences and if you’ve found a better workaround. Thanks everyone!

Just wanted to share the resolution I got from Gurpreet from ScalePad Support - Thank you Gunpreet for working with me and answering my question.

 

TL;DR - Client renaming isn’t fully supported in LCM yet. Renames in your source integration don’t sync directly because data is tied to the original client record. A feature request has been submitted. For now, use Lifecycle Manager’s Linking and Renaming feature to update the client name internally while keeping the new name in your source system so all data stays connected. 

 

Thanks everyone!

 

---

 

Hello Adam,
 
I’ve just checked with our product development team regarding your concern about client renaming. At present, Lifecycle Manager syncs data via the ConnectWise Manage ID, but this isn’t directly linked to client records. That’s why when a client is renamed in your source integration, the data appears to disappear, it’s still tied to the original client record name.
 
We completely understand how important client renaming is for your workflow. To address this in the long term, we've submitted a feature request on your behalf.
 
In the meantime, the current workaround is to use Lifecycle Manager’s Linking and Renaming feature to update the client name within Lifecycle Manager itself, while keeping the new name in your source integration. This ensures that all of your existing data remains tied to the correct client record.

 

 

Reply


Terms & ConditionsCookie settings