A Carbonio migration technique enables the import of configurations and data from an existing infrastructure that is going to be retired or decommissioned into a Carbonio-based mail server architecture.

Because the procedures needed to extract configuration and data from the Source infrastructure might differ greatly, this section does not go into detail on how to do so.

The second step of such a process—importing an existing mail server architecture into Carbonio—is briefly discussed in this section. In fact, we think it’s important to concentrate on a few important aspects of the import process and that it’s important to recognise the work it takes to successfully complete a whole export/import cycle.

We categorise the import process into two categories:

The numerous processes involved in the import process should go without a hitch because Open Source technologies are used. We must first clarify a few terms before moving on to this.

Definitions

To prevent misconceptions, let’s define a few terminology before we start the debate.

Source

The mail server to depart from is the Source infrastructure (Source), which at the start of the process comprises everything. It is vital to emphasise that the Source (which may be any programme) is not taken into consideration in any way by the method and that it is just required to extract data from it.

Destination

You wish to relocate your current mail server to the Carbonio installation known as the Destination infrastructure (Destination).

Procedure

A series of steps known as the Procedure will direct you as you import all of your data to the Destination. Although it is believed that all of the data has already been exported before you start the Procedure, access to the CLI of both the Source and Destination is still required.

Provisioning

The set of all information and metadata about the Domains, accounts, COSes, and mailing lists that exist on the Source before to the beginning of the Procedure is referred to as provisioning.

Data is the collection of every email that was stored on the Source before to the commencement of the Procedure.

The collection of all emails that are existing on the Source prior to the commencement of the Procedure is referred to as the Data.

Import Methodology

Two steps make up the Procedure. Phase one is the preparation phase, with the goal of making sure you have all the components needed to begin the import. Phase two is the actual import process on the destination.

Initial Phase: Checklist of Requirements

The list of conditions that must be fulfilled is as follows:

Depending on the Source, different tools may be required to get these files.

Import to Destination in Phase Two

The actual execution of the Procedure takes place in this step. The necessary orders are being refined, and the best instruments to do the tasks are being selected.

The instructions in the following sections serve just as samples of how to complete the import on a Carbonio infrastructure. You are free to select any alternative strategy or device.

As soon as more details and instructions are available, they will be published and linked here.

Accounts and Domains Provisioning

The domain and account structures for example.com and acme.corp are kept in the files /opt/zextras/backup/example.com.ldif and /opt/zextras/backup/acme.corp.ldif, respectively, on the LDAP Node. Use the slapadd command to import them:

Bringing in emails

Using the IMAP protocol is the most practical and accepted method of reading from the Source and writing to the Destination. For this reason, we advise using imapsync as the IMAP conversion tool.

We’ll presume that you’ve previously acquired the login information for an account that has access to every account on the Source, and that you’ve already set up a Global Administrator account that will only be used for imports.

Replace all values written in ALL_CAPS in the following command, which must be run on the Node hosting Carbonio Mails and Calendar, with matching values appropriate for your infrastructure.

ICS Calendars Import

We presume that all users’ calendar files have been exported and stored in the /opt/zextras/backup/ directory of the Carbonio Mails & Calendar Node in ICS Format, for example, /opt/zextras/backup/user1@example.com.ics, /opt/zextras/backup/user1@acme.corp.ics, and so on.

The next command can be used to import them into Carbonio:

CSV Contacts Import

We presume that all users’ calendar files have been exported and stored in the /opt/zextras/backup/ directory of the Carbonio Mails & Calendar Node in CSV Format, for example, /opt/zextras/backup/user1@example.com.csv, /opt/zextras/backup/user1@acme.corp.csv, and so on.

The command listed below may be used to import them into Carbonio:

Restrictions on the Process

In fact, the procedure migrates:

• Domains
• COSes
• Accounts
• Messages sent and received by email
• private file cabinets
• Public folders
• Distribution and mailing lists
• Signatures
• Calendars
• Contacts

Additional components that are not a part of a Carbonio installation won’t be moved.