BOHEUS
e5ac9f5b8b
Follow-up based on comments from https://github.com/twentyhq/twenty/pull/23266 <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/twentyhq/twenty/pull/23429?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> --------- Co-authored-by: Félix Malfait <felix@twenty.com> Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
33 lines
2.4 KiB
Plaintext
33 lines
2.4 KiB
Plaintext
---
|
|
title: Export FAQ
|
|
description: Frequently asked questions about exporting data.
|
|
---
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="Can we export all workspace data before cancellation, including custom objects, custom fields, relationships, notes, tasks, opportunities, attachments, workflows, permissions, and audit history?">
|
|
Workspace data can be exported before cancellation with some exceptions: dashboards, workflows and permissions must be transferred manually; audit logs cannot be transferred.
|
|
</Accordion>
|
|
<Accordion title="Which elements cannot currently be exported or migrated?">
|
|
Most elements can be exported or migrated with some exceptions:
|
|
- workflows, dashboards and all settings (API keys, webhooks, audit logs, user settings, etc.) must be migrated manually
|
|
- app-created objects and fields can be migrated by installing said app in a different workspace. They shouldn't be migrated manually
|
|
- some records, like workflow versions and workflow runs, are not transferable at all and are expected to be lost
|
|
- some objects like message and calendar related objects shouldn't be exported as they're created when an account is connected and synced periodically. They'll be synchronized again once you connect your account (as long as you have access to said account, if it's an account of a team member who left your company, then those messages must be exported, otherwise they'll be lost)
|
|
</Accordion>
|
|
<Accordion title="Is there an official cloud to self-hosted migration procedure or an assisted migration service?">
|
|
As of now, there is no official cloud-to-self-hosted migration procedure. The general idea is to:
|
|
- first, install apps to introduce app-owned objects and fields
|
|
- replicate custom objects and fields added by users
|
|
- use a script with API keys or AI tools to migrate all data from one workspace to another
|
|
- all non-transferrable objects must be migrated manually
|
|
|
|
Please be aware of a few things:
|
|
- you can send up to 50 requests per minute on the Pro plan or 100 requests per minute on the Organization plan before hitting a request/min limit
|
|
- each API request can have up to 200 records
|
|
- some data in fields like Created by, Timeline activities and Updated by will be lost during import and overwritten by the system
|
|
</Accordion>
|
|
<Accordion title="Are exported files provided in open and documented formats?">
|
|
Exported files in the UI are in Excel format, and all API requests can be saved in JSON format.
|
|
</Accordion>
|
|
</AccordionGroup>
|