Skip to content

Commit 1a7b12d

Browse files
authored
Update migrate-from-umarketingsuite.md
Added some changes to the guide after going through it
1 parent 8aed0d3 commit 1a7b12d

File tree

1 file changed

+14
-6
lines changed

1 file changed

+14
-6
lines changed

13/umbraco-engage/upgrading/migrate-from-umarketingsuite.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,10 @@ The result should look like this:
6363

6464
If any of these checks return a failure, please resolve the issue before proceeding with the migration.
6565

66+
{% hint style="info" %}
67+
If you do not use Umbraco Commerce or Umbraco Forms, the list of results will be shorter.
68+
{% endhint %}
69+
6670
## Step 3: Replace NuGet packages and dependencies
6771

6872
In this second step, you will replace all existing uMarketingSuite dependencies with Umbraco Engage dependencies.
@@ -123,11 +127,11 @@ Based on the [Key Changes](migrate-from-umarketingsuite.md#key-changes) below up
123127

124128
Please find below an overview of the changes to the default scripts in a uMarketingSuite installation:
125129

126-
* All scripts & Asset Paths containing the `uMarketingSuite` keyword are renamed to:
130+
* All scripts & Asset Paths containing the `uMarketingSuite` keyword will need to be renamed to:
127131
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.analytics.js`
128132
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.ga4-bridge.js`
129133
* `Assets/Umbraco.Engage/Scripts/umbracoEngage.blockerdetection.js`
130-
* The Cockpit Partial View has been moved to:
134+
* The Cockpit Partial View has been moved, and needs to be changed to:
131135
*  `Partials/Umbraco.Engage/Cockpit`
132136
* If you are tracking custom events please make sure to update the calls to the send event method:
133137
* `ums("send", "event", "<Category name>", "<Action>", "<Label>")`
@@ -253,12 +257,12 @@ Run this script to migrate all the Umbraco data.
253257

254258
## Step 6: Finalize the migration
255259

256-
1. Delete any `obj`/`bin` folders in your projects to ensure a clean build.
257-
2. Recompile all projects and ensure all dependencies are restored correctly.
258-
3. Contact Umbraco Support for a license key.
260+
1. Delete any `obj`/`bin` folders in your projects to ensure a clean build.
261+
3. Recompile all projects and ensure all dependencies are restored correctly.
262+
4. Contact Umbraco Support for a license key.
259263
1. Look for the speech bubble in the bottom right corner of your screen at [umbraco.com](https://umbraco.com).
260264
2. Click it, and you can open a new support request.
261-
4. Add your new Umbraco Engage [license](../installation/licensing.md) key to the `appSettings.json` file:
265+
5. Add your new Umbraco Engage [license](../installation/licensing.md) key to the `appSettings.json` file:
262266

263267
```json
264268
"Umbraco": {
@@ -330,6 +334,10 @@ Repeat the steps below for each environment that needs to be migrated.
330334
* Go to Engage -> Settings -> Configuration in the backoffice and click the Regenerate button. Depending on the number of page views in the database this could take a while.
331335
9. Use the [Troubleshooting Installs](../installation/troubleshooting-installs.md) guide to verify that everything works as expected.
332336

337+
{% hint style="info" %}
338+
If you are on Umbraco Cloud, stopping and starting the site is not necessary.
339+
{% endhint %}
340+
333341
### **Custom firewall changes**
334342

335343
If the `/umbraco/umarketingsuite/` path was previously allowed, this needs to change to `/umbraco/engage/`.

0 commit comments

Comments
 (0)