1e41f4b71Sopenharmony_ci# Model Switching Overview 2e41f4b71Sopenharmony_ci 3e41f4b71Sopenharmony_ci 4e41f4b71Sopenharmony_ciPerform the following operations to switch a declarative paradigm-based application developed based on the FA model to the stage model. 5e41f4b71Sopenharmony_ci 6e41f4b71Sopenharmony_ci 7e41f4b71Sopenharmony_ci- Project switch: Create an application project of the stage model. 8e41f4b71Sopenharmony_ci 9e41f4b71Sopenharmony_ci  10e41f4b71Sopenharmony_ci 11e41f4b71Sopenharmony_ci- [Configuration file switch](configuration-file-diff.md): Switch **config.json** to **app.json5** and **module.json5**. 12e41f4b71Sopenharmony_ci 13e41f4b71Sopenharmony_ci  14e41f4b71Sopenharmony_ci 15e41f4b71Sopenharmony_ci- [Component switch](pageability-switch.md): Switch the PageAbility, ServiceAbility, and DataAbility components of the FA model to the UIAbility and ExtensionAbility components of the stage model. The figure below shows only the switching from PageAbility to UIAbility. The left part is the FA model, and **app.ets** is the PageAbility component. The right part is the stage model, and **EntryAbility.ets** is the UIAbility component. 16e41f4b71Sopenharmony_ci 17e41f4b71Sopenharmony_ci  18e41f4b71Sopenharmony_ci 19e41f4b71Sopenharmony_ci- [Widget switch](widget-switch.md): Switch the FormAbility component of the FA model to the FormExtensionAbility component of the stage model. In the figure below, **Service Widget** is FormAbility in the FA model and FormExtensionAbility in the stage model. 20e41f4b71Sopenharmony_ci 21e41f4b71Sopenharmony_ci  22e41f4b71Sopenharmony_ci 23e41f4b71Sopenharmony_ci  24e41f4b71Sopenharmony_ci 25e41f4b71Sopenharmony_ci- [API switch](api-switch-overview.md): Switch the APIs with the **FAModelOnly** tag used in the FA model to the recommended APIs in the stage model. 26e41f4b71Sopenharmony_ci 27e41f4b71Sopenharmony_ci  28
