Migrate from Language Understanding (LUIS) to conversational language understanding (CLU)
Conversational language understanding (CLU) is a cloud-based AI offering in Azure Cognitive Services for Language. It's the newest generation of Language Understanding (LUIS) and offers backwards compatibility with previously created LUIS applications. CLU employs state-of-the-art machine learning intelligence to allow users to build a custom natural language understanding model for predicting intents and entities in conversational utterances.
CLU offers the following advantages over LUIS:
- Improved accuracy with state-of-the-art machine learning models for better intent classification and entity extraction. LUIS required more examples to generalize certain concepts in intents and entities, while CLU's more advanced machine learning reduces the burden on customers by requiring significantly less data.
- Multilingual support for model learning and training. Train projects in one language and immediately predict intents and entities across 96 languages.
- Ease of integration with different CLU and custom question answering projects using orchestration workflow.
- The ability to add testing data within the experience using Language Studio and APIs for model performance evaluation prior to deployment.
Comparison between LUIS and CLU
The following table presents a side-by-side comparison between the features of LUIS and CLU. It also highlights the changes to your LUIS application after migrating to CLU. Click on the linked concept to learn more about the changes.
|LUIS features||CLU features||Post migration|
|Machine-learned and Structured ML entities||Learned entity components||Machine-learned entities without subentities will be transferred as CLU entities. Structured ML entities will only transfer leaf nodes (lowest level subentities that do not have their own subentities) as entities in CLU. The name of the entity in CLU will be the name of the subentity concatenated with the parent. For example, Order.Size|
|List, regex, and prebuilt entities||List, regex, and prebuilt entity components||List, regex, and prebuilt entities will be transferred as entities in CLU with a populated entity component based on the entity type.|
||Not currently available||
|Single culture for each application||Multilingual models enable multiple languages for each project.||The primary language of your project will be set as your LUIS application culture. Your project can be trained to extend to different languages.|
|Entity roles||Roles are no longer needed.||Entity roles will be transferred as entities.|
|Settings for: normalize punctuation, normalize diacritics, normalize word form, use all training data||Settings are no longer needed.||Settings will not be transferred.|
|Patterns and phrase list features||Patterns and Phrase list features are no longer needed.||Patterns and phrase list features will not be transferred.|
|Entity features||Entity components||List or prebuilt entities added as features to an entity will be transferred as added components to that entity. Entity features will not be transferred for intents.|
|Intents and utterances||Intents and utterances||All intents and utterances will be transferred. Utterances will be labeled with their transferred entities.|
|Application GUIDs||Project names||A project will be created for each migrating application with the application name. Any special characters in the application names will be removed in CLU.|
|Versioning||Every time you train, a model is created and acts as a version of your project.||A project will be created for the selected application version.|
|Evaluation using batch testing||Evaluation using testing sets||Adding your testing dataset will be required.|
|Role-Based Access Control (RBAC) for LUIS resources||Role-Based Access Control (RBAC) available for Language resources||Language resource RBAC must be manually added after migration.|
|Single training mode||Standard and advanced training modes||Training will be required after application migration.|
|Two publishing slots and version publishing||Ten deployment slots with custom naming||Deployment will be required after the application’s migration and training.|
|LUIS authoring APIs and SDK support in .NET, Python, Java, and Node.js||CLU Authoring REST APIs.||For more information, see the quickstart article for information on the CLU authoring APIs. Refactoring will be necessary to use the CLU authoring APIs.|
|LUIS Runtime APIs and SDK support in .NET, Python, Java, and Node.js||CLU Runtime APIs. CLU Runtime SDK support for .NET and Python.||See how to call the API for more information. Refactoring will be necessary to use the CLU runtime API response.|
Migrate your LUIS applications
Use the following steps to migrate your LUIS application using either the LUIS portal or REST API.
Migrate your LUIS applications using the LUIS portal
Follow these steps to begin migration using the LUIS Portal:
After logging into the LUIS portal, click the button on the banner at the top of the screen to launch the migration wizard. The migration will only copy your selected LUIS applications to CLU.
The migration overview tab provides a brief explanation of conversational language understanding and its benefits. Press Next to proceed.
Determine the Language resource that you wish to migrate your LUIS application to. If you have already created your Language resource, select your Azure subscription followed by your Language resource, and then click Next. If you don't have a Language resource, click the link to create a new Language resource. Afterwards, select the resource and click Next.
Select all your LUIS applications that you want to migrate, and specify each of their versions. Click Next. After selecting your application and version, you will be prompted with a message informing you of any features that won't be carried over from your LUIS application.
Review your Language resource and LUIS applications selections. Click Finish to migrate your applications.
A popup window will let you track the migration status of your applications. Applications that have not started migrating will have a status of Not started. Applications that have begun migrating will have a status of In progress, and once they have finished migrating their status will be Succeeded. A Failed application means that you must repeat the migration process. Once the migration has completed for all applications, select Done.
After your applications have migrated, you can perform the following steps:
Frequently asked questions
Which LUIS JSON version is supported by CLU?
CLU supports the model JSON version 7.0.0. If the JSON format is older, it would need to be imported into LUIS first, then exported from LUIS with the most recent version.
How are entities different in CLU?
In CLU, a single entity can have multiple entity components, which are different methods for extraction. Those components are then combined together using rules you can define. The available components are:
- Learned: Equivalent to ML entities in LUIS, labels are used to train a machine-learned model to predict an entity based on the content and context of the provided labels.
- List: Just like list entities in LUIS, list components exact match a set of synonyms and maps them back to a normalized value called a list key.
- Prebuilt: Prebuilt components allow you to define an entity with the prebuilt extractors for common types available in both LUIS and CLU.
- Regex: Regex components use regular expressions to capture custom defined patterns, exactly like regex entities in LUIS.
Entities in LUIS will be transferred over as entities of the same name in CLU with the equivalent components transferred.
After migrating, your structured machine-learned leaf nodes and bottom-level subentities will be transferred to the new CLU model while all the parent entities and higher-level entities will be ignored. The name of the entity will be the bottom-level entity’s name concatenated with its parent entity.
- Pizza Order
Migrated LUIS entity in CLU:
- Pizza Order.Topping
- Pizza Order.Size
You also cannot label 2 different entities in CLU for the same span of characters. Learned components in CLU are mutually exclusive and do not provide overlapping predictions for learned components only. When migrating your LUIS application, entity labels that overlapped preserved the longest label and ignored any others.
For more information on entity components, see Entity components.
How are entity roles transferred to CLU?
Your roles will be transferred as distinct entities along with their labeled utterances. Each role’s entity type will determine which entity component will be populated. For example, a list entity role will be transferred as an entity with the same name as the role, with a populated list component.
How do entity features get transferred in CLU?
Entities used as features for intents will not be transferred. Entities used as features for other entities will populate the relevant component of the entity. For example, if a list entity named SizeList was used as a feature to a machine-learned entity named Size, then the Size entity will be transferred to CLU with the list values from SizeList added to its list component. The same is applied for prebuilt and regex entities.
How are entity confidence scores different in CLU?
Any extracted entity has a 100% confidence score and therefore entity confidence scores should not be used to make decisions between entities.
How is conversational language understanding multilingual?
Conversational language understanding projects accept utterances in different languages. Furthermore, you can train your model in one language and extend it to predict in other languages.
Training utterance (English): How are you?
Labeled intent: Greeting
Runtime utterance (French): Comment ça va?
Predicted intent: Greeting
How is the accuracy of CLU better than LUIS?
CLU uses state-of-the-art models to enhance machine learning performance of different models of intent classification and entity extraction.
These models are insensitive to minor variations, removing the need for the following settings: Normalize punctuation, normalize diacritics, normalize word form, and use all training data.
Additionally, the new models do not support phrase list features as they no longer require supplementary information from the user to provide semantically similar words for better accuracy. Patterns were also used to provide improved intent classification using rule-based matching techniques that are not necessary in the new model paradigm. The question below explains this in more detail.
What do I do if the features I am using in LUIS are no longer present?
There are several features that were present in LUIS that will no longer be available in CLU. This includes the ability to do feature engineering, having patterns and pattern.any entities, and structured entities. If you had dependencies on these features in LUIS, use the following guidance:
Patterns: Patterns were added in LUIS to assist the intent classification through defining regular expression template utterances. This included the ability to define Pattern only intents (without utterance examples). CLU is capable of generalizing by leveraging the state-of-the-art models. You can provide a few utterances to that matched a specific pattern to the intent in CLU, and it will likely classify the different patterns as the top intent without the need of the pattern template utterance. This simplifies the requirement to formulate these patterns, which was limited in LUIS, and provides a better intent classification experience.
Phrase list features: The ability to associate features mainly occurred to assist the classification of intents by highlighting the key elements/features to use. This is no longer required since the deep models used in CLU already possess the ability to identify the elements that are inherent in the language. In turn removing these features will have no effect on the classification ability of the model.
Structured entities: The ability to define structured entities was mainly to enable multilevel parsing of utterances. With the different possibilities of the sub-entities, LUIS needed all the different combinations of entities to be defined and presented to the model as examples. In CLU, these structured entities are no longer supported, since overlapping learned components are not supported. There are a few possible approaches to handling these structured extractions:
- Non-ambiguous extractions: In most cases the detection of the leaf entities is enough to understand the required items within a full span. For example, structured entity such as Trip that fully spanned a source and destination (London to New York or Home to work) can be identified with the individual spans predicted for source and destination. Their presence as individual predictions would inform you of the Trip entity.
- Ambiguous extractions: When the boundaries of different sub-entities are not very clear. To illustrate, take the example “I want to order a pepperoni pizza and an extra cheese vegetarian pizza”. While the different pizza types as well as the topping modifications can be extracted, having them extracted without context would have a degree of ambiguity of where the extra cheese is added. In this case the extent of the span is context based and would require ML to determine this. For ambiguous extractions you can use one of the following approaches:
- Combine sub-entities into different entity components within the same entity.
- Pizza Order (entity)
- Size (subentity)
- Quantity (subentity)
- Pizza Order (entity)
- Size (list entity component: small, medium, large)
- Quantity (prebuilt entity component: number)
In CLU, you would label the entire span for Pizza Order inclusive of the size and quantity, which would return the pizza order with a list key for size, and a number value for quantity in the same entity object.
- For more complex problems where entities contain several levels of depth, you can create a project for each level of depth in the entity structure. This gives you the option to:
- Pass the utterance to each project.
- Combine the analyses of each project in the stage proceeding CLU.
For a detailed example on this concept, check out the pizza sample projects available on GitHub.
How do I manage versions in CLU?
CLU saves the data assets used to train your model. You can export a model's assets or load them back into the project at any point. So models act as different versions of your project.
Why is CLU classification different from LUIS? How does None classification work?
CLU presents a different approach to training models by using multi-classification as opposed to binary classification. As a result, the interpretation of scores is different and also differs across training options. While you are likely to achieve better results, you have to observe the difference in scores and determine a new threshold for accepting intent predictions. You can easily add a confidence score threshold for the None intent in your project settings. This will return None as the top intent if the top intent did not exceed the confidence score threshold provided.
Do I need more data for CLU models than LUIS?
The new CLU models have better semantic understanding of language than in LUIS, and in turn help make models generalize with a significant reduction of data. While you shouldn’t aim to reduce the amount of data that you have, you should expect better performance and resilience to variations and synonyms in CLU compared to LUIS.
If I don’t migrate my LUIS apps, will they be deleted?
Your existing LUIS applications will be available until October 1, 2025. After that time you will no longer be able to use those applications, the service endpoints will no longer function, and the applications will be permanently deleted.
Are .LU files supported on CLU?
Only JSON format is supported by CLU. You can import your .LU files to LUIS and export them in JSON format, or you can follow the migration steps above for your application.
What are the service limits of CLU?
See the service limits article for more information.
Do I have to refactor my code if I migrate my applications from LUIS to CLU?
The API objects of CLU applications are different from LUIS and therefore code refactoring will be necessary.
CLU authoring APIs: Instead of LUIS's specific CRUD APIs for individual actions such as add utterance, delete entity, and rename intent, CLU offers an import API that replaces the full content of a project using the same name. If your service used LUIS programmatic APIs to provide a platform for other customers, you must consider this new design paradigm. All other APIs such as: listing projects, training, deploying, and deleting are available. APIs for actions such as importing and deploying are asynchronous operations instead of synchronous as they were in LUIS.
CLU runtime APIs: The new API request and response includes many of the same parameters such as: query, prediction, top intent, intents, entities, and their values. The CLU response object offers a more straightforward approach. Entity predictions are provided as they are within the utterance text, and any additional information such as resolution or list keys are provided in extra parameters called
resolution. See the reference documentation for more information on the API response structure.
How are the training times different in CLU? How is standard training different from advanced training?
CLU offers standard training, which trains and learns in English and is comparable to the training time of LUIS. It also offers advanced training, which takes a considerably longer duration as it extends the training to all other supported languages. The train API will continue to be an asynchronous process, and you will need to assess the change in the DevOps process you employ for your solution.
How has the experience changed in CLU compared to LUIS? How is the development lifecycle different?
In LUIS you would Build-Train-Test-Publish, whereas in CLU you Build-Train-Evaluate-Deploy-Test.
- Build: In CLU, you can define your intents, entities, and utterances before you train. CLU additionally offers you the ability to specify test data as you build your application to be used for model evaluation. Evaluation assesses how well your model is performing on your test data and provides you with precision, recall, and F1 metrics.
- Train: You create a model with a name each time you train. You can overwrite an already trained model. You can specify either standard or advanced training, and determine if you would like to use your test data for evaluation, or a percentage of your training data to be left out from training and used as testing data. After training is complete, you can evaluate how well your model is doing on the outside.
- Deploy: After training is complete and you have a model with a name, it can be deployed for predictions. A deployment is also named and has an assigned model. You could have multiple deployments for the same model. A deployment can be overwritten with a different model, or you can swap models with other deployments in the project.
- Test: Once deployment is complete, you can use it for predictions through the deployment endpoint. You can also test it in the studio in the Test deployment page.
This process is in contrast to LUIS, where the application ID was attached to everything, and you deployed a version of the application in either the staging or production slots.
This will influence the DevOps processes you use.
Does CLU have container support?
No, you cannot export CLU to containers.
How will my LUIS applications be named in CLU after migration?
Any special characters in the LUIS application name will be removed. If the cleared name length is greater than 50 characters, the extra characters will be removed. If the name after removing special characters is empty (for example, if the LUIS application name was
@@), the new name will be untitled. If there is already a conversational language understanding project with the same name, the migrated LUIS application will be appended with
_1 for the first duplicate and increase by 1 for each additional duplicate. In case the new name’s length is 50 characters and it needs to be renamed, the last 1 or 2 characters will be removed to be able to concatenate the number and still be within the 50 characters limit.
Migration from LUIS Q&A
If you have any questions that were unanswered in this article, consider leaving your questions at our Microsoft Q&A thread.
Submit and view feedback for