[FR] Move pages to a different workspace

[emmggi]

Description

Move pages between workspaces. (Not spaces that exist in a single workspace, that you move between with drag and drop.)

Impact

All users.

Additional Context

We could have a small button in the options popover for each page in the panel that gives us the option to 'Move to workspace' and give us a dialog to choose a new workspace.

[szefte]

without this the notion import feature is kinda pointless. since you can only import INTO a workspace in appflowy. you end up with tons of workspaces that require consolidation, which is impossible.
moving one page at a time is not a real solution.

[annieappflowy]

@szefte , I’m just trying to get more insight into your use case. I assume your Notion setup has multiple workspaces. Since exporting from Notion is done per workspace, why do you want to combine workspaces in AppFlowy?

[szefte]

I am very impressed you are following up. the use case is just moving pages from one place to antorher. notion has it. one note has it. Evernote has it. ...so we should have it I n appflowy because we want this tool to be better than others. let me know what I can do to contribute.

…

On Mon, Oct 28, 2024, 21:40 Annie ***@***.***> wrote: @szefte <https://github.com/szefte> , I’m just trying to get more insight into your use case. I assume your Notion setup has multiple workspaces. Since exporting from Notion is done per workspace, why do you want to combine workspaces in AppFlowy? — Reply to this email directly, view it on GitHub <#5344 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2FTM5TUAB2UMXQ3IXTWYDZ537RBAVCNFSM6AAAAABH2GKMM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGEZTINZZGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[chevdor]

I would add the specific of some use case I ran into, to complement this issue.

Splitting workspaces

It is common for users to start with a single workspace and realize they should be splitting some content to share some content with others for instance.
In that case, the user creates a new workspace and needs to move some old content to the new workspace.

It sounds "easy" but that can be tricky in the case when some content reference other content. it may lead to having to reference content from another workspace. This is likely neither possible nor wanted.

Considering grids with relations:

• Gb -> Ga
• Gc -> Ga

Assuming all those Grids are in Workspace A and you want to move Gb to Workspace B. It now points to Ga in Worspace A. One could think we could propose the user to move Ga to Workspace B as well... but then Gc (in workspace A), would point to Ga now in worspace B.

Imo a good option would be to:

• warn the user and ask
• propose to duplicate the date in the new workspace (duplication is usually bad...)
• let the user deal with the duplication

Joining workspaces

On the other hand, some user may start with several workspace because... creating workspaces may sound good (ie one workspace per project) and then realize that there are limitations to spreading content ion various workspaces.
In that case, the user will likely want to get back to a single workspace and move content from the workspace to workspace.

This use case should be simpler as it sounds like we cound simply transfer ALL the content from a workspace to another one.

[szefte]

honestly I am finding a lot of the 'you own your data' claims a bit bold and over hyped. the current state of the way your data is handled is very limited. 1. you can't export your data 2. you can't import your data 3. now I find out can't even move data within the app it is not a good look.

…

On Tue, Oct 29, 2024, 03:03 Chevdor ***@***.***> wrote: I would add the specific of some use case I ran into, to complement this issue. Splitting workspaces It is common for users to start with a single workspace and realize they should be splitting some content to share some content with others for instance. In that case, the user creates a new workspace and needs to move some old content to the new workspace. It sounds "easy" but that can be tricky in the case when some content reference other content. it may lead to having to reference content from another workspace. This is likely neither possible nor wanted. Considering grids with relations: - Gb -> Ga - Gc -> Ga Assuming all those Grids are in Workspace A and you want to move Gb to Workspace B. It now points to Ga in Worspace A. One could think we could propose the user to move Ga to Workspace B as well... but then Gc (in workspace A), would point to Ga now in worspace B. Imo a good option would be to: - warn the user and ask - propose to duplicate the date in the new workspace (duplication is usually bad...) - let the user deal with the duplication Joining workspaces On the other hand, some user may start with several workspace because... creating workspaces may sound good (ie one workspace per project) and then realize that there are limitations to spreading content ion various workspaces. In that case, the user will likely want to get back to a single workspace and move content from the workspace to workspace. This use case should be simpler as it sounds like we cound simply transfer ALL the content from a workspace to another one. — Reply to this email directly, view it on GitHub <#5344 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2FTM3X74Q4ZNTW73KQTVTZ55FOPAVCNFSM6AAAAABH2GKMM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGYZTAMJVGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[annieappflowy]

@szefte , I don't think you statement is fair.

We allow you to export your documents as .md files and databases as .csv files.
You can import your AppFlowy data folder into an AppFlowy workspace.
Moving pages to a different workspace is a newly requested feature, which we will begin developing once we have the bandwidth.
In addition, self-hosting AppFlowy is supported and has been adopted by hundreds of users.

[ghanjiboy]

My main issue with this missing feature really comes from after you've imported from Notion into a new workspace - how do you combine what you've already had into this workspace or vice versa.