![Untitled design (1)-Aug-01-2022-12-37-27-80-PM.png]](https://help.syscloud.com/hs-fs/hubfs/Untitled%20design%20(1)-Aug-01-2022-12-37-27-80-PM.png?height=40&name=Untitled%20design%20(1)-Aug-01-2022-12-37-27-80-PM.png){kind=small}
HubSpot Backup: Permanent Limitations
This article explains the permanent backup limitations you may see for HubSpot in SysCloud. It covers HubSpot CRM, marketing and CMS data. For each limitation you'll find what it means and what, if anything, you need to do.
What is a permanent limitation?
A permanent limitation means SysCloud could not back up some of your data in this backup because of a condition in HubSpot that retrying straight away would not fix, for example the item was deleted or its type is not supported.
- The backup status shows Completed. Everything else in the backup is backed up as normal; only the affected object or record is skipped.
- Each section below says whether you need to do anything, and whether the data is backed up again later.
- A permanent limitation does not remove anything SysCloud has already backed up.
How to use this article
- In SysCloud, open the backup details and note the message shown for the affected object or record, and its backup status.
- Find that message in the quick reference table below.
- Read the matching section for what it means and what to do.
Quick reference
| Limitation | Message shown in SysCloud | Backup status | Action |
|---|---|---|---|
| 1. Form submissions not supported for this form type | Form submissions unsupported | Completed | No action needed |
| 2. HubDB table deleted | HubDB table deleted | Completed | No action needed |
| 3. Item no longer available | Item inaccessible | Completed | No action needed |
Limitations in detail
1. Form submissions not supported for this form type
Message shown in SysCloud:
- Form submissions unsupported
Backup status: Completed
What happened
Backup completed, but submissions for the affected form could not be backed up because HubSpot does not support exporting submissions for this form type.
What you can do
No action is needed. Submissions for this form type are skipped in every backup.
2. HubDB table deleted
Message shown in SysCloud:
- HubDB table deleted
Backup status: Completed
What happened
Backup completed, but the affected HubDB table could not be backed up because it was deleted from the HubSpot account connected to SysCloud.
What you can do
No action is needed. The deleted table is no longer available, so there is nothing left to back up.
3. Item no longer available
Message shown in SysCloud:
- Item inaccessible
Backup status: Completed
What happened
Backup completed, but the affected item could not be backed up because it is no longer available in HubSpot. Usually the item was deleted after the backup started, before SysCloud could copy it.
What you can do
No action is needed. The item no longer exists, so there is nothing left to back up. If it is restored later, it is backed up in the next backup like any new item.
Frequently asked questions
Will SysCloud try to back up the data again?
Not while the cause remains. Once the cause is fixed, for example a deleted item is restored, the data is backed up in the next scheduled backup.
Does this mean my whole backup failed?
No. Only the affected object or record was skipped. Everything else in the backup was backed up as normal.
Is data I backed up earlier affected?
No. A permanent limitation does not remove anything SysCloud has already backed up. Earlier backups remain available in SysCloud.
Need more help?
Contact SysCloud Support and include:
- A screenshot of the message shown in SysCloud, or the exact message text
- The affected object or record
- The date and time of the backup
Related article: HubSpot Backup: Temporary Limitations