XperiDo Migration Processes

The XperiDo migration processes are divided in automated and manual processes. For an in-depth overview of each process please review the table below.

Automated migration processes

The system performs the following functions automatically when importing the XperiDo project into Smart Flows, using the Smart Flows import functionality:

Component	Description
Data sets	All XperiDo data sets are imported and converted to standard data sets. Samples are not imported. For XperiDo Nucleus: data sets are converted to schema data sets. ZIP data sets are not imported.
Dynamic fields	All XperiDo dynamic fields are converted to custom data sets. For every template that has at least 1 dynamic field, a custom data set is created. This custom data set will contain all of that template's dynamic fields and will be attached to that template.
Templates	Standard templates become standard templates. Body, header, footer, and insert segments become standard templates. E-mail templates become standard templates. Composition masters, multipart templates, and body segment groups become compositions. The conditions in multipart templates (XperiDo Nucleus) are not imported. Template history is not imported.
Languages	All XperiDo languages are imported.
Assets	All XperiDo assets are imported.
Markers	All XperiDo markers (XperiDo Nucleus) are imported and converted to tags.
Flow	For every standard template and composition in the imported project, a flow is created. This flow does two things retrieves the data from CRM generates a document from the retrieved data

Manual migration processes

The following functions must be performed manually by an administrator.

Field name	Description
Connector	When setting up a new project, you will be asked to make a connector to Microsoft Dynamics 365 CE. All the data sets will be linked to this connector. This is not necessary if you are importing from XperiDo Nucleus.
Import	You have to manually import the file containing your XperiDo project. The import triggers the the automated processes.
Dynamic fields / Custom data set fields	Dynamic fields are converted to custom data set fields, but you will need to re-map these again in every template where they are used.
Samples	You will need to recreate all samples you want to use.
Template settings / Flows	Flows are the new way of working with template settings. You can still do everything you could in XperiDo 3.4 (bar some deprecated features), but you will have to configure this manually (although you get one basic flow per template, so you can still generate documents immediately). The new flows concept is powerful, but you'll probably want to understand it before trying to recreate what you had in XperiDo 3.4. There is a lot of Step 5 Creating Flows and Producing Documents you can read through to assist you with this, or you can support@experlogix or you use the support widget at the end of this page.
Conditions on compositions	If you're coming from XperiDo Nucleus, all conditions on multipart templates will be lost and thus need to be recreated.
Tags	Smart Flows has tags and tag groups, whereas XperiDo 3.4 only had tags. You will need to add tag groups and tags yourself if you're coming from XperiDo for Microsoft Dynamics 365 CE.
Assets	If you reference an asset in an expression in the Template Design add-in in XperiDo, it will look something like this: It is now better, as you can just use the name of the asset as it appears in the Project Console: It means you should use assets so that the expressions contain only the asset's name.
Workflows	If you're using XperiDo for Microsoft Dynamics 365 CE, you must recreate all of your workflows. This cannot be automated due to the changes in how we approach workflows. In Smart Flows, workflows are more straightforward since they execute a flow. It's the flow that contains all of the steps. We have documentation about Smart Flows workflow steps, see how Smart Flows does it.

While Smart Flows is a direct continuation of XperiDo, there are some noticeable differences in some areas. Some things are expanded, done differently, or just completely overhauled. However, most features are the same, just done in a better way.