A migration technique to Carbonio CE allows you to import configurations and data from an existing Carbonio CE-based mail server infrastructure that is ready to be retired or dismissed.
This section does not go into how configuration and data are exported from the source infrastructure since the procedures necessary to extract them might vary greatly.
This section provides a high-level overview of the second step in such a procedure: importing an existing mail server architecture into Carbonio CE. Indeed, we feel it is vital to focus on several crucial aspects of the import operation, as well as not underestimate the work required to properly complete an entire export/import cycle.
We divide the import method into two major areas:
The import technique is based on Open Source technologies, therefore there should be no issues with the numerous activities that are necessary. More on it later; first, we need to establish certain ideas.
Before we begin the conversation, let us clarify certain words to avoid confusion.
The Source infrastructure (Source) is the mail server from which to depart and, at the start of the method, contains everything. It is critical to emphasise that we make no assumptions about the Source (which might be any programme), and that the Source is simply required to extract data and is not affected by the technique.
The Destination infrastructure refers to the Carbonio CE installation to which you wish to relocate your existing mail server.
The Procedure is a group of tasks that will lead you through the import of all your data to the Destination. It requires access to both the Source and Destination CLIs, however it is expected that all data has already been exported before you start the Procedure.
Provisioning is the collection of all data and information about the Domains, accounts, COSes, and mailing lists that exist on the Source prior to the commencement of the Procedure.
Data is the set of e-mails on the Source prior to the commencement of the procedure.
The procedure is broken into two sections. step one is a preparatory step that ensures you have all of the essential materials to begin the import, whereas phase two is when all imports to the Destination are carried out.
Phase One: Requirements Checklist
The following is the list of conditions that must be met:
Phase 2: Import to Destination.
Domain and Account Provisioning
On the LDAP Node, domain files are assumed to be saved in files /opt/zextras/backup/example.com.ldif (domain and account structure for example.com) and /opt/zextras/backup/acme.corp.ldif (domain and account structure for acme.corp). They may be imported using the slapadd command.
Import of Emails
The most functional and standard technique to read from the Source and publish into the Destination is the utilise the IMAP protocol. For this reason, we recommend imapsync as the tool for IMAP conversion.
We presume you have previously gotten credentials for an account with access to all accounts on the Source, and you have established a Global Administrator to be used just for the import.
Replace all of the values written in ALL_CAPS with values appropriate for your infrastructure in the following command, which must be performed on the Node hosting Carbonio Mails and Calendar.
Import of ICS calendars
We presume that all users’ Calendar files have been exported and saved in ICS format to the Carbonio Mails & Calendar Node’s /opt/zextras/backup/ directory, for example, /email@example.com, /firstname.lastname@example.org, and so on.
To import them into Carbonio CE, use the following command:
Import of CSV Contacts
We presume that all users’ Calendar files have been exported and saved in CSV format to the Carbonio Mails & Calendar Node’s /opt/zextras/backup/ directory, for example, /email@example.com, /firstname.lastname@example.org, and so on.
To import them into Carbonio, use the following command:
Limitations of the Procedure
The procedure does move.
- Email Messages (sent and received)
- Personal folders
- Shared folders.
- Mailing and distribution lists
Other aspects not related to a Carbonio installation will not be moved.