Lifecycle Manager keeps your data current by syncing it from your connected integrations. Data updates in two stages: syncing, which pulls the data in, and processing, which prepares it to display in the app. This article explains how each stage works, so you know what to expect and how to get the most current data when you need it.
How syncing works
Lifecycle Manager syncs all your data types together in a single sync. This includes, for example, hardware, software, contacts, contracts, tickets, time entries, and Microsoft 365 (M365) and other SaaS usage data.
| Note: Lifecycle Manager pulls Security Awareness Training (SAT) deliverable data in real time, whenever you create or refresh a deliverable. It isn't subject to the sync and processing timing described elsewhere in this article. The exception is the very first SAT sync for a client, which also pulls in your client list. That initial sync can take 40 minutes to process. |
How Lifecycle Manager creates a client
Lifecycle Manager creates a client when it syncs at least one of the following from a connected integration:
Hardware assets
Software assets
Contacts
Security Awareness Training (SAT) data
Endpoint Detection and Response (EDR) data
Customer Satisfaction (CSAT) data
Lifecycle Manager recognizes clients as the same entity across your integrations only when their names match exactly.
If a client's name differs between your PSA and RMM, for example, Lifecycle Manager identifies each one as a separate client and creates a record for each unique name.
You can merge clients manually in Lifecycle Manager.
See: Merging and renaming Clients
How often syncs run
Syncs run automatically every 24 hours. This works through a queue. The queue typically starts overnight, though it can extend into the morning or afternoon depending on various factors.We don't commit to an exact daily sync time.
How long syncs take
Sync speed varies and depends on a few factors:
- Rate limits: Each integration partner sets limits to protect their own systems, which can affect how quickly we can pull your data.
- Data volume: How much data we pull depends on the integration. PSAs typically have the largest data volume, followed by RMMs and then documentation tools. Other integrations tend to sync relatively quickly.
- Incremental syncing: Integrations that support incremental syncing only pull data that's changed since the last sync. This makes later syncs much faster than the first one. Integrations that don't support incremental syncing pull your full data set every time, which takes longer.
| Note: If your environment is very large and your integration doesn't support incremental syncing, you might see a new sync start again almost as soon as the previous one finishes, or syncing at unusual times for your time zone. This is expected. |
Checking your sync status
To check your sync status, click Integrations in the top navigation bar of ScalePad Hub. The integration center shows a high-level sync status for each of your integrated tools, and integrations with errors appear under Failing Integrations.
For more detail, click the overflow menu (three dots) beside an integration to see its sync logs.
Triggering a manual sync
If something changes in your integration and you want the latest data sooner, you can trigger a manual sync:
- Click Integrations in the top navigation bar of the ScalePad Hub.
- Click the name of the integration you want to sync.
- Scroll down and click Save and sync now.
You can trigger up to three manual syncs per rolling 24-hour period for each integration. Manual syncs are prioritized in the sync queue, so they run faster than automatic syncs.
How processing works
Once a sync completes, your data still needs to process before it appears in Lifecycle Manager. How long that takes depends on the data type.
Hardware, software, and contacts
This data appears in Lifecycle Manager immediately once a sync shows complete on the Integrations page.
All other data types
For contracts, tickets, time entries, and M365/SaaS usage data, processing time depends on whether the sync was manual or automatic:
- Manual or initial syncs: Processing can take up to 40 minutes after a sync completes.
- Automatic syncs: Processing runs once a day, so it can take up to 24 hours after a successful automatic sync.
There's no visible processing status in the app for either case, so allow for the full processing window before checking again.
If you rely only on automatic syncs, this data can be up to 24 hours behind what you see in your integration. If you need more current data, we recommend running a manual sync. The sync is prioritized for the fastest possible turnaround.
| Any questions? Reach out to our Lifecycle Manager support team by submitting a support ticket. |
 NEW Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot. |
Related to
