Revise migration steps for Teamcenter Connector 2606

content/en/docs/marketplace/industry/xcelerator/platform-supported/teamcenter-connector/2606-configuration/migrate-to-2606.md

@@ -34,11 +34,10 @@ Follow these steps in this exact order to ensure a proper migration:
     1. Open your app in Studio Pro 11.12.1 or above.
     1. Make sure all changes are committed, if using version control, or backed up.
 
-2. Move the Toolkit contents to the TcConnector module.
+2. Remove the resource files.
 
-    1. Remove the old TcConnector module from your project, and ignore the errors for now.
-    1. Rename the old TeamcenterToolkit module to TcConnector module, then remove the TeamcenterToolkit module. By doing this, the old Toolkit references in the project are now pointing to the TcConnector module.
-    {{% alert color="info" %}} This step does not change the BOMapping. This is fixed in a later step. {{% /alert %}} 
+    1. In your *Resources* folder, remove the *OperationMapping*, *TeamcenterCommon*, *TeamcenterConnector* folders. The contents of these folders are now in the *TcConnector* folder
+    1. Keep the *TeamcenterExtension* folder for now. You can remove it after all the journeys are migrated to the new service document.
 
 3. Import the new connector.
 
@@ -53,11 +52,13 @@ Follow these steps in this exact order to ensure a proper migration:
         The most common issues you will encounter are:
 
         * Errors in microflows that were generated by the Teamcenter Extension can best be recreated by the new version of the extension. Refer to step 9 for details.
-        * Missing microflows/Java actions can be found in the [Deprecated Microflows and Their Replacements](#deprecated-microflows) and [Deprecated Java Actions and Their Replacements](#deprecated-java) tables.
-        * References to `TeamcenterToolkit.*` — Change these to `TcConnector.*`, because Toolkit was merged into TcConnector.
-        * References to `FileType` — Change these to `NamedReference`.
-        * Microflows that handle the Boolean return value from `Login` — Remove this handling, as `Login` now throws an exception instead.
-        * Refer to [Breaking Changes](#breaking-changes) on this page.
+        * For a list of deprecated microflows and Java actions, see [Deprecated Microflows and Their Replacements](#deprecated-microflows) and [Deprecated Java Actions and Their Replacements](#deprecated-java).
+        * Deprecated microflows and Java actions can be found in the *internal>deprecated* folder in the **TcConnector** module. These microflows are not used by the connector anymore, but you can include them and move them to your own module if required. 
+        * References to `TeamcenterToolkit.*` in BO mappings should be changed to `TcConnector.*` The Toolkit module is merged into TcConnector.
+        * References to `FileType` should be changed to `NamedReference`.
+        * The **Login** microflow does not return a Boolean value anymore. **Login** now throws an exception instead.
+        * We have deprecated microflows that use the `TcSession` entity. Do not use the `TcSession` entity in your code. If you want to know if someone is logged in, use `RULE_TeamcenterConfiguration_IsLoggedIn` instead.    
+        * For more information, refer to the [Breaking Changes](#breaking-changes) section.
 
 5. Update security.
 
@@ -90,11 +91,20 @@ Follow these steps in this exact order to ensure a proper migration:
     1. Replace the old microflows with the newly generated microflows.
     1. You can use the **Duplicate** feature on the **History** tab to create variations of an integration without reconfiguring from scratch.
 
-10. Test thoroughly.
+10. Remove the Toolkit module from your project.
+
+    1. Before removing the Toolkit module, commit your work by right-clicking on the Toolkit module and selecting **Find usages of this module**.
+    1. Since the Toolkit module is merged with the TcConnector module, all references to the Toolkit should point to the TcConnector.
+
+       If there are still many resources pointing to the Toolkit, you can rename the Toolkit to TcConnector2, remove the TcConnector2, rename the TcConnector to TcConnector2 and back to TcConnector. This trick connects the old resouces in the Toolkit to the new ones in the TcConnector.
+
+    1. Use **Ctrl+F** to search for *"Toolkit"*, to see if there are any BO mappings left that reference the Toolkit. If there are, replace them with TcConnector. 
+
+11. Test thoroughly.
 
     1. Run each generated microflow against your Teamcenter instance.
     1. Verify that search, create, update, and retrieval operations work as expected.
-    1. Test error handling by triggering error conditions, such as invalid search criteria.
+    1. Test error handling by triggering error conditions (for example, invalid search criteria).
     1. If you have automated tests, run them to ensure integration behavior is correct.
 
 ## Breaking Changes {#breaking-changes}
@@ -150,6 +160,24 @@ These Java actions still exist in the deprecated folder, but should no longer be
 | `GetItemFromId` | `GetItemAndRelatedObjects` |
 | `RetrieveCookie` | No replacement |
 
+## Deprecated Entities {#deprecated-entities}
+
+The following entities have been deprecated. To indicate this, the entities have been renamed with an underscore prefix:
+
+* `CreateBomWindowInput`
+* `CreateBomWindowInput_CreateBomWindowResponse`
+* `CreateBomWindowResponse`
+* `ExpandPSOneLevelResponse`
+* `GetItemFromIdInput`
+* `GetItemFromIdResponse`
+* `GetWorkflowTemplatesInput`
+* `ItemRevisionOutput`
+* `RevisionIDs`
+* `SessionUser`
+* `TcServerInfo`
+* `WhereUsedInput`
+* `WhereUsedResponseInfo`
+
 ## Automatically Migrated Items
 
 Not everything needs to be rebuilt from scratch. These items are automatically migrated as they are: