# Migration Guide
### Important Dates & Timeline
| Date | Milestone |
| ------------------ | ---------------------------------------------------------- |
| **April 16, 2025** | Data export functionality available |
| **April 23, 2025** | Dashworks API discontinued |
| **July 16, 2025** | Logins disabled for Dashworks web application and Slackbot |
### What's Happening
As announced in our [blog post](https://www.dashworks.ai/blog/dashworks-is-joining-forces-with-hubspot), Dashworks has been acquired by HubSpot. As our team focuses on integrating our technology into the HubSpot platform, the standalone Dashworks service will be sunset according to the timeline above.
* No new sign-ups will be accepted for Dashworks web application or Slackbot as of April 16, 2025
* Existing customers will maintain full access until July 16, 2025
* All customers will receive prorated refunds based on the last date their workspace is active
### Exporting Your Data
We've created straightforward processes to help you export your valuable data from Dashworks. You can request exports anytime between April 16 and July 16, 2025.
#### For Workspace Administrators
As a Workspace Admin, you can export all workspace-level data by following these steps:
1. Go to [Dashworks > Settings > Workspace > General](https://web.dashworks.ai/admin/appearance)
2. Click Request under **Workspace data export**. The data export will typically be available within 30 minutes.
3. You'll receive an email with download instructions when your export is ready.
**What's included in the user data export:**
Workspace Bookmarks
| Field Name | Data Type | Description |
| ---------- | --------- | --------------------------------- |
| title | `string` | The display name of the bookmark. |
| link | `string` | The URL the bookmark points to. |
App connections
| Field Name | Data Type | Description |
| -------------- | --------- | -------------------------------------------------------------------------------------------------------- |
| app\_name | `string` | The name of the connected application (e.g., Google Drive, Slack). |
| user\_email | `string` | The email address of the user within the Dashworks system. |
| type | `string` | Indicates if the connection is for the entire organization ('org') or an individual user ('individual'). |
| account\_email | `string` | The email address used to log in to the connected application. |
Files
| Field Name | Data Type | Description |
| ------------- | ----------------- | ---------------------------------------------------- |
| author\_email | `string` | The email address of the user who uploaded the file. |
| link | `string` | A direct link or URL to access the file. |
| title | `string` | The name or title of the file. |
| created\_at | `ISO 8601 string` | The date and time when the file was created. |
Answers
| Field Name | Data Type | Description |
| ------------- | ----------------- | ------------------------------------------------------ |
| title | `string` | The title or question associated with the Answer. |
| content | `string` | The body or text content of the Answer. |
| created\_at | `ISO 8601 string` | The date and time when the Answer was first created. |
| modified\_at | `ISO 8601 string` | The date and time when the Answer was last updated. |
| author\_email | `string` | The email address of the user who authored the Answer. |
Workspace Bots
| Field Name | Data Type | Description |
| ----------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| bot\_id | `string` | A unique identifier for the bot within Dashworks. |
| bot\_name | `string` | The display name of the bot. |
| icon | `string` | URL or identifier for the bot's avatar/icon image. |
| description | `string` | A brief summary of the bot's purpose or capabilities. |
| model | `string` | The specific Large Language Model (LLM) powering the bot (e.g., 'gpt-4', 'claude-3'). |
| sources | `list[dict]` | A list of data sources the bot can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. |
| is\_managed | `boolean` | Indicates if the bot is managed by Dashworks administrators (`true`) or potentially user-created (`false`). |
| admin\_emails | `list[string]` | A list of email addresses of users who have administrative control over this bot. |
| instructions | `string` | Custom instructions or guidelines provided to the bot to influence its behavior and responses. |
| creator\_email | `string` | The email address of the user who originally created the bot. |
| created\_at | `ISO 8601 string` | The date and time when the bot was created. |
| learned\_feedback | `list[string]` | Instructions learned from feedback provided to the bot. |
Slack Channels
| Field Name | Data Type | Description |
| ------------------------- | --------- | --------------------------------------------------------------------------------------------------------- |
| channel\_name | `string` | The name of the Slack channel where the bot integration is active (e.g., `#general`, `#support`). |
| bot\_id | `string` | The unique identifier (`bot_id`) of the Dashworks Bot assigned to this Slack channel integration. |
| reply\_only\_when\_tagged | `boolean` | If `true`, the bot will only respond in the channel when explicitly tagged (e.g., `@DashworksBot`). |
| acknowledge\_question | `boolean` | If `true`, the bot may send an initial message acknowledging it received the question before answering. |
| confidence\_threshold | `integer` | A percentage (0-100) representing the minimum confidence level required for the bot to attempt an answer. |
| fallback\_message | `string` | The message displayed by the bot when it cannot answer or its confidence is below the threshold. |
| create\_draft | `boolean` | If `true`, the bot's response will be generated as a draft in Slack for review before sending. |
Org-wide Workflows
| Field Name | Data Type | Description |
| -------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| name | `string` | The display name of the workflow. |
| description | `string` | A brief summary of what the workflow does. |
| prompt | `string` | The core instructions or prompt text that defines the workflow's task for the LLM. |
| sources | `list[dict]` | A list of data sources the workflow can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. |
| model | `string` | The specific Large Language Model (LLM) used by the workflow (e.g., 'gpt-4', 'claude-3'). |
| creator\_email | `string` | The email address of the user who created the workflow. |
| created\_at | `ISO 8601 string` | The date and time when the workflow was created. |
Workspace General Settings
| Field Name | Data Type | Description |
| ----------------- | --------- | ----------------------------------------------------------------------- |
| company\_name | `string` | The name of the organization using Dashworks. |
| logo | `string` | A URL pointing to the company's logo image file. |
| background\_image | `string` | A URL pointing to the custom background image for the workspace. |
| background\_color | `string` | The HEX color code used for the workspace background (e.g., `#FFFFFF`). |
Workspace AI Controls
| Field Name | Data Type | Description |
| ------------- | --------- | -------------------------------------------------------------------------------------------------------------- |
| instructions | `string` | Global instructions applied to all AI interactions within the workspace, guiding overall AI behavior. |
| text\_filters | `string` | A comma-separated list of keywords or phrases that the AI should avoid or filter out in its responses. |
| disclaimer | `string` | A standard disclaimer message that may be appended to AI-generated content within the workspace. |
| model | `string` | The default Large Language Model (LLM) used across the workspace unless overridden by specific bots/workflows. |
Workspace Members
| Field Name | Data Type | Description |
| ---------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| name | `string` | The full name of the user. |
| email | `string` | The user's primary email address used for login and identification within Dashworks. |
| role | `string` | The user's permission level within the workspace. Typically 'admin' (full access) or 'member' (standard access). |
| status | `string` | The current state of the user's account: 'signed\_up' (active), 'provisioned' (invited but not yet active), 'blocked' (access revoked). |
**Need to delete your workspace?** You can request this by going to [Dashworks > Settings > Workspace > General](https://web.dashworks.ai/admin/appearance) as well. Once deleted, the workspace and all associated data will be permanently removed from our systems.
#### For Individual Users
Individual users can export their personal data directly from the Dashworks interface:
1. Go to [Dashworks > Settings > Personal > General](https://web.dashworks.ai/my-settings)
2. Click Request under **Personal data export**. The data export will typically be available within 30 minutes.
3. You'll receive an email with download instructions when your export is ready.
**What's included in the user data export:**
Private Bots
| Field Name | Data Type | Description |
| -------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| bot\_id | `string` | A unique identifier for the bot within Dashworks. |
| bot\_name | `string` | The display name of the bot. |
| icon | `string` | URL or identifier for the bot's avatar/icon image. |
| description | `string` | A brief summary of the bot's purpose or capabilities. |
| model | `string` | The specific Large Language Model (LLM) powering the bot (e.g., 'gpt-4', 'claude-3'). |
| sources | `list[dict]` | A list of data sources the bot can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. |
| is\_managed | `boolean` | Indicates if the bot is managed by Dashworks administrators (`true`) or potentially user-created (`false`). |
| admin\_emails | `list[string]` | A list of email addresses of users who have administrative control over this bot. |
| instructions | `string` | Custom instructions or guidelines provided to the bot to influence its behavior and responses. |
| creator\_email | `string` | The email address of the user who originally created the bot. |
| created\_at | `ISO 8601 string` | The date and time when the bot was created. |
Private Workflows
| Field Name | Data Type | Description |
| -------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| name | `string` | The display name of the workflow. |
| description | `string` | A brief summary of what the workflow does. |
| prompt | `string` | The core instructions or prompt text that defines the workflow's task for the LLM. |
| sources | `list[dict]` | A list of data sources the workflow can access. Each source object follows the "App connections" schema. An empty list means "AI only". A source with `app_name: "web"` indicates web search capability. |
| model | `string` | The specific Large Language Model (LLM) used by the workflow (e.g., 'gpt-4', 'claude-3'). |
| creator\_email | `string` | The email address of the user who created the workflow. |
| created\_at | `ISO 8601 string` | The date and time when the workflow was created. |
App connections
| Field Name | Data Type | Description |
| -------------- | --------- | -------------------------------------------------------------------------------------------------------- |
| app\_name | `string` | The name of the connected application (e.g., Google Drive, Slack). |
| user\_email | `string` | The email address of the user within the Dashworks system. |
| type | `string` | Indicates if the connection is for the entire organization ('org') or an individual user ('individual'). |
| account\_email | `string` | The email address used to log in to the connected application. |
Topics
| Field Name | Data Type | Description |
| ----------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
| title | `string` | The title or name assigned to this Dashworks Topic. |
| created\_at | `ISO 8601 string` | The date and time when the Topic was initially created. |
| messages | `list[Message]` | An ordered list of messages exchanged within the Topic. See the "Messages" table below for details. |
| visibility | `string` | Controls who can view the Topic: 'private' (only creator), 'workspace' (all members), 'anyone\_with\_link'. |
### Messages (within a Topic)
| Field Name | Data Type | Description |
| -------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| role | `string` | Indicates who sent the message: 'User' or 'Dashworks'. |
| content | `string` | The textual content of the message. |
| attachments | `list[string]` | A list of the titles of any files attached to this specific message. These files are linked from the main "Files" data structure. |
| sources | `list[dict]` | A list of data sources cited or used to generate Dashworks’ response. Each dictionary contains: `app_name` (string), `title` (string), `url` (string), `modified_at` (ISO 8601 string). |
| bot\_id | `string` | The unique identifier (`bot_id`) of the Org-wide Bot that was tagged or generated this message, if applicable. Null or absent otherwise. |
| deep\_research | `boolean` | Indicates whether the "deep research" mode was used by Dashworks to generate this specific message (`true` or `false`). |
**Important notes:**
* You may only request one data export per user account
* Exports will be available for download for 7 days after processing
* If you request account deletion, you'll no longer be able to log into Dashworks
### Enterprise Customer Support
Our enterprise customers will receive dedicated migration support:
* Schedule a personalized migration consultation using our [Calendly link](https://calendly.com/prasad-kawthekar/30m)
* Get tailored recommendations for alternative solutions based on your specific use case
* Receive priority support for data export and transition questions
We understand this transition represents a significant change for your team. We're committed to making it as smooth as possible.
### Frequently Asked Questions
**Q: Will I receive a refund for my subscription?**
A: Yes, all customers will receive prorated refunds for any prepaid amounts based on the on the last date their workspace is active.
**Q: What happens to my data after July 16?**
A: All customer data will be securely deleted from Dashworks systems within 30 days after the sunset date, in accordance with our data retention policies.
**Q: How large will my export files be?**
A: This depends on your usage. Most exports will be under 10GB, but high-usage accounts may have larger exports.
**Q: Can I still access support during the transition?**
A: Absolutely! Our support team will be available through the entire transition period. For questions, please contact .
Thank you for being part of the Dashworks journey. We're excited to bring even more powerful capabilities to you through our integration with HubSpot.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://support.dashworks.ai/migration-guide.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.