RC_Migration_Guide #246

Merged
fede merged 16 commits from RC_Migration_Guide into master 2022-07-15 18:01:10 +02:00
Owner

Howto backup cloud and current webmail contacts and importing them into Roundcube.

Howto backup cloud and current webmail contacts and importing them into Roundcube.
fede added this to the Get Roundcube in Prod. milestone 2022-07-01 06:20:09 +02:00
fede added the
HOWTO
CONTACTS
ROUNDCUBE
EMAIL
labels 2022-07-01 06:20:09 +02:00
muppeth was assigned by fede 2022-07-01 06:20:09 +02:00
meaz was assigned by fede 2022-07-01 06:20:09 +02:00
antilopa was assigned by fede 2022-07-01 06:20:09 +02:00
avg_joe was assigned by fede 2022-07-01 06:20:09 +02:00
fede added 12 commits 2022-07-01 06:20:11 +02:00
fede added 1 commit 2022-07-01 06:20:50 +02:00
meaz requested changes 2022-07-01 15:42:26 +02:00
@ -0,0 +28,4 @@
In the same way that you usually access webmail.
## What will happen to my emails and contacts?
All your emails and contacts will be automatically transferred into **Roundcube**. Anyway, we strongly suggest you to backup your contacts. In this guide you can find how to do it.
Owner

Need to check with muppeth if contacts will be transfered. Those already synced with NC, for sure. Otherwise, I'm not sure.

Need to check with muppeth if contacts will be transfered. Those already synced with NC, for sure. Otherwise, I'm not sure.
fede marked this conversation as resolved
@ -0,0 +35,4 @@
## My contacts and emails did not migrate, what should I do?
First of all, don't panic. If your contacts and emails did not migrate, please contact us and we fix it.
Owner

we will try to fix it.

we will try to fix it.
fede marked this conversation as resolved
@ -0,0 +62,4 @@
![](en/snappy.sync.mp4?resize=1024,576&loop)
## Exporting contacts from SnappyMail
Owner

It is the secondt time you use "Exporting contacts from SnappyMail" as title. It seems like users have to do both process. To me, you're offering here two possibilities: syncing to NC, and exporting a file.

It is the secondt time you use "Exporting contacts from SnappyMail" as title. It seems like users have to do both process. To me, you're offering here two possibilities: syncing to NC, and exporting a file.
Author
Owner

It seems like users have to do both process. To me, you're offering here two possibilities: syncing to NC, and exporting a file.

They have to if they want to export the contacts in the cloud. So far, all of the accounts I've tested shown an empty addressbook by default. In RC the addressbooks of the same accounts were displayed OK.

I personally would only mention the first method, but then you never know if someone, for some reason, wants to sync and backup their contacts. So, yes, we can remove that part. I still think that since the option exists we should mention/document it.

> It seems like users have to do both process. To me, you're offering here two possibilities: syncing to NC, and exporting a file. They have to if they want to export the contacts in the cloud. So far, all of the accounts I've tested shown an empty addressbook by default. In RC the addressbooks of the same accounts were displayed OK. I personally would only mention the first method, but then you never know if someone, for some reason, wants to sync and backup their contacts. So, yes, we can remove that part. I still think that since the option exists we should mention/document it.
Owner

I'm not sure I understand. You can export then import in NC, you don't have to sync if you don't want.

I'm not sure I understand. You can export then import in NC, you don't have to sync if you don't want.
Author
Owner

At the moment, you can just simply go the Contacts cloud app and download your addressbook to then import them into RC. That's covered and there's this line

"The easiest and quickest way is to export your contacts from the Contacts app in the cloud."

in which we could add it's the suggested way.

Another option would be to do the backup from the webmail, which is also nice and works. But since contacts sync between the client and the cloud is not enable by default, you need to enable it yourself otherwise you have an empty addressbook when login to the webmail. That's the reason why the SnappyMail sync part it's on this guide.

As I understand, your suggestion is that the "guide" should only cover how to download the addressbook from the cloud and how to import it into RC, right?

At the moment, you can just simply go the Contacts cloud app and download your addressbook to then import them into RC. That's covered and there's this line >"The easiest and quickest way is to export your contacts from the Contacts app in the cloud." in which we could add it's the suggested way. Another option would be to do the backup from the webmail, which is also nice and works. But since contacts sync between the client and the cloud is not enable by default, you need to enable it yourself otherwise you have an empty addressbook when login to the webmail. That's the reason why the SnappyMail sync part it's on this guide. As I understand, your suggestion is that the "guide" should only cover how to download the addressbook from the cloud and how to import it into RC, right?
Owner

That is not what I'm saying.

This guide should be to help people moving from Snappymail to Roundcube (the contact part). If their contacts are already synced with NC, then they don't have to do anything. The problem is if their contacts are on snappymail only.

So, in your guide, you're starting with "Exporting contacts from the cloud". I'm not too sure why it is need in the guide. As I said, if contacts are already in the cloud, they will be synced with RC on first log, and this, automatically. They don't have to do anything.

Then, you're writing about "Exporting contacts from SnappyMail" and you write:

Now, the first time you access SnappyMail you will most likely find your addressbook empty. If this is the case, just follow the steps below to enable synchronization between your webmail and cloud contacts.

If the addressbook is empty, then I don't understand why they should sync anything! That is actually pretty simple: they just go to Roundcube, and don't care about loosing contacts as they have none.

So, to me, only the last part "Exporting contacts from SnappyMail" is really useful: that will help those that have contacts in Snappymail and that haven't synced them with NC.

That is not what I'm saying. This guide should be to help people moving from Snappymail to Roundcube (the contact part). If their contacts are already synced with NC, then they don't have to do anything. The problem is if their contacts are on snappymail only. So, in your guide, you're starting with "Exporting contacts from the cloud". I'm not too sure why it is need in the guide. As I said, if contacts are already in the cloud, they will be synced with RC on first log, and this, automatically. They don't have to do anything. Then, you're writing about "Exporting contacts from SnappyMail" and you write: > Now, the first time you access SnappyMail you will most likely find your addressbook empty. If this is the case, just follow the steps below to enable synchronization between your webmail and cloud contacts. If the addressbook is empty, then I don't understand why they should sync anything! That is actually pretty simple: they just go to Roundcube, and don't care about loosing contacts as they have none. So, to me, only the last part "Exporting contacts from SnappyMail" is really useful: that will help those that have contacts in Snappymail and that haven't synced them with NC.
fede marked this conversation as resolved
fede added 1 commit 2022-07-03 18:34:13 +02:00
fede added 1 commit 2022-07-03 18:42:54 +02:00
meaz approved these changes 2022-07-04 08:14:37 +02:00
fede added 1 commit 2022-07-15 18:00:24 +02:00
fede merged commit 42f5aa936b into master 2022-07-15 18:01:10 +02:00
Sign in to join this conversation.
No reviewers
No project
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Howto#246
No description provided.