Skip to main content
Warranty writeback copies eligible MSPortal device warranty dates into Hudu assets or IT Glue flexible assets. It is an optional MSP integration management task that changes the connected provider.

​
Before enabling it

Confirm the documentation connection is active, companies are mapped correctly, and its key can update the intended assets. You need synchronized asset layouts or flexible asset types with usable serial and warranty fields, plus MSPortal device types and devices with successful warranty checks and an expiration date. Matching uses a unique serial number within the mapped company and selected asset type. It does not fall back to hostname. Missing, placeholder or ambiguous serials are skipped. These checks reduce bad matches; correct company and field mappings are still essential.

​
Configure and save

1

Open Warranty Writeback

Open Settings > Integrations > Configure for Hudu or IT Glue. In Hudu use Documentation; in IT Glue use Sync & Sharing. Find Warranty Writeback.
2

Choose device and asset types

In Device and warranty field mappings, map each intended MSPortal device type to a Hudu asset layout or IT Glue flexible asset type. Not mapped excludes that device type. This is not an IT Glue Configuration mapping.
3

Review each field

Choose a Serial number field and Warranty expiration field. Warranty start field is optional and must differ from expiration. Hudu can offer Primary serial. Review suggested fields; their names are suggestions, not proof that they contain the intended values.
4

Enable and save deliberately

Turn on Enable warranty writeback, then select Save warranty mappings. The switch and mapping selectors are drafts until this button succeeds. At least one complete mapping is required to enable writeback.
Saving with writeback enabled requests an immediate background asset sync and provider writeback. It does not wait until the next daily run. This save also enables synchronization for mapped asset types; review those content choices and client visibility separately.
If multiple device types share an asset type, they must use the same serial and warranty fields. Changing those fields for one row updates the other rows using that asset type in the draft. Review all affected rows before saving.

​
Verify the result

Wait for the background outcome, then inspect a known matching asset in Hudu or IT Glue. Confirm the company, serial, selected fields and resulting dates. A settings-save message confirms configuration storage; it does not establish that every external update succeeded. Writeback uses devices with successful warranty checks and a known expiration date. An optional start date is written only when the source device has one. An unchanged date may need no external update. Missing source dates are not a request to erase the provider’s values. Recurring writeback can run while enabled. A run may skip an asset or fail for a subset, so keep the source dates and provider result under review rather than treating enablement as a guarantee that all assets are current.

​
Disable or change the scope

Turn off Enable warranty writeback and select Save warranty mappings to stop future enabled runs. Previously written provider values remain; disabling is not a rollback of dates or a recall of an already-running update. Use Not mapped to remove a device type from the draft, then save. Saving mappings can enable their asset-type sync even when writeback is off; removing a mapping or disabling writeback does not automatically restore earlier sync choices. Review the surrounding content-sync settings if that is your intention.

​
Troubleshooting

​
Frequently asked questions

No. The enable switch and mappings are a draft until Save warranty mappings succeeds.
Saving with writeback enabled requests an immediate asset sync and writeback, in addition to recurring runs.
No. It uses a unique usable serial within the mapped company and selected asset type. Ambiguous, missing and placeholder serials are skipped.
This workflow targets IT Glue flexible assets, or Hudu assets. Choose the corresponding asset type and fields.
Device types mapped to the same asset type must share serial and warranty fields. The draft applies those field changes to all rows using that type.
It enables sync for mapped asset types, and enabling writeback also enables the relevant asset dataset. Review content sync and visibility separately.
No. Save the disabled setting to stop future enabled runs. It does not undo provider writes or recall work already running.
No. Check the background result and an actual mapped provider asset. Missing source dates, unmatched serials or provider failures can prevent updates.
The device needs a successful warranty check and an expiration date, plus the configured device type, company mapping and unique serial match.

Hudu setup

Review Hudu content and optional outbound features.

IT Glue setup

Review IT Glue setup and sharing.

Devices

Inspect device inventory and warranty data.