A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
10

The issue you have is that one or more of your profiles are corrupt. Either by renaming or deleting. Everything internal to Sitecore profiling works off of names, not profile keys item or pattern card item IDs. The way to solve this is to clean up the names/items in the database. To do this navigate to https://[YOUR_SITE]/sitecore/admin/DbCleanup.aspx, ...


7

This is a known issue : https://kb.sitecore.net/articles/583017 As a workaround for the issue, please consider deleting the {Express Migration Root folder}/Migration.db file before running the migration for another source instance of the same version.


5

The Sitecore Express Migration Tool helps you to migrate between different Sitecore versions. As soon as you have migrated to the version you need locally you deploy your solution to Azure. If you would like to use Azure as an Infrastructure (IaaS) you can deploy your solution as you would do with any other Virtual Machine. If you would like to use Azure ...


3

Express migration tool does not migrate your old archived items, So your option here is to manually move these data in SQL tables, You can check this answer here where they used SQL queries to migrate the archived items, You use the same approach, There are no breaking changes in the tables schema, but make sure you try this first in a non-production ...


2

The solution to the answer as in the Sitecore event handler pipeline. Our project had a custom event that initialized a constructor that threw and exception. This made the entire event pipeline fail, and thus require it to be rebuild. Rebuilding the event pipeline during login made WFFM throw an error. The code in question was this: <sitecore> &...


2

The tool is not compatible with version newer than Sitecore 8.2 Update 1. You should install install upgrade package using the UpdateInstallationWizard to upgrade from 8.2.1 to to 8.2.4


2

@codeandfootball I ran into the same issue while running the Sitecore Express Migration Tool 3.1 and realised that the error is misleading and not actually referring to the path\connection strings in the instance parameters but rather the path that the Migration Tool is running from. In my case I had the Migration Tool extracted onto my desktop within a ...


2

On newer versions like 8.1 and 8.2 you do not need the migration tool. The upgrade package can take you directly there in one step. This is a change from earlier versions of Sitecore where you would have to do step by step for each version using update packages.


1

Before you run the Express Migration Tool 3.1, you must decide whether you want to run it on the same computer as your source and target instances or on a different computer. If you run the tool on a different computer, you must ensure that it has Server Message Block (SMB) access to the source, target, and comparison instance's database servers and file ...


1

Assuming that you are using Express Migration Tool 3.1, From Express migration tool installation guide, https://dev.sitecore.net/~/media/4B49AAB1EBE94F55ADF07A7740AABBC8.ashx When referring this KB https://kb.sitecore.net/articles/400952 looks like none of the version supports to migrate directly to 9.1 from 7.2. The Sitecore Express Migration Tool 3.1 is ...


1

Since you are already on Sitecore 9.0 Initial Update, I don't think you need to create packages and install on Update 2. And obviously since Express Migration Tool 3.1 doesn't support any targeted version greater than 9.0 Initial Version, you can't use that. I would rather Upgrade the same SC 9.0 Initial Version instance to Update 2. From this stage onward ...


1

Sitecore Migration Tool supports migration just to initial release of 9. You can find the compatibility table of the module here: https://kb.sitecore.net/articles/400952 To upgrade from 9.0 to 9.0.2 you need to follow Upgrade guide from 9.0.2 release. For the second point is difficult to give your the right answer. You need to verify all modules and ...


1

Before deleting this folder you need to verify two things Is this folder contain only "MediaCache" folder. If yes then you can go and delete this folder because this folder will automatically created once you run the website and visit some pages If "App Data" folder contains "MediaCache" as well as "MediaFiles" folder then you can't delete the "MediaFiles" ...


1

The Express Migration Tool 2.0 migrates Web Forms For Marketers 2.4 items and data.


1

FWIW - it looks like everything is stored in a SQLite db called migration.db which is in the directory where the Migration Tool was run from. I renamed this, had to re-specify all my paths & connection strings and it migrated the users.


Only top voted, non community-wiki answers of a minimum length are eligible