23

When I did an upgrade from 7.2 to 8.1 earlier this year, I followed these steps: Setup a new instance of Sitecore 8.1 and configure it according to the documentation. Get my settings/layouts into some sort of source control (using Unicorn or TDS) Apply those settings/layouts to my new instance Compile the existing code against the new version of Sitecore, ...


19

I normally try to split DB upgrading from code upgrading. This allows me to run the DB upgrade process of vanilla Sitecore instances where any customisations won't interfere with the db upgrade process. I then upgrade the code as per the SC upgrade guides (and yes this means going through each one). This can take some time because the config changes a lot, ...


19

The answer to this depends on the context of your project. Sitecore's recommendations are to make incremental upgrades for every version and updates as well since your current to the latest you are trying to get upgraded to. This does require a lot of work specially when it's a big jump from 6.5 to 8.2. As already answered here if you are making manual ...


17

This is quite amusing :-) Here's a summary from one of the developers of the module: The "Etalon" instance is a synonym of "comparison" instance. It's a clean Sitecore instance with the same version as the source instance. The source is compared with the Etalon. The delta is extracted and moved to the target instance. Etalon is described by him as "...


11

etalon does indeed refer to the comparison instance, but it should not have made it into public-facing documentation. 'Comparison instance' is the official term (not as fun, but there you go) and the release notes have been updated accordingly. If you find the word 'etalon' in any public-facing API or interface, let me know. :) It can stay in the source code ...


9

Sitecore (along with DMS Data) should be upgraded together. While the Express Migration Tool looks appetizing, it does not upgrade DMS data. The important guide for Sitecore Analytics is the xDB Upgrade Guide found for each version. The prerequisites of each guide highlight the upgrade Path. From Sitecore 7.2, there are a few hoops you have to go through to ...


9

I would like to think that it is based on the race car from Sleeping Dogs: http://sleepingdogs.wikia.com/wiki/Etalon A high-speed vehicle based on a Danish supercar? Sounds about right for the express migration :) In the Express Migration tool itself the Etalon instance seems to be the piece which stores the data about the comparison instance. It seems to ...


9

This is the script I've used in the past: # specify your path here. It is most likely be page templates and page content $startPath = "/sitecore/content" Get-ChildItem -Path $startPath -Recurse | ForEach-Object { $item = $_; Get-Rendering -Item $_ | ForEach-Object { $rendering = $_; $matches = [regex]::Matches($_.Placeholder,'(...


8

Here is a prototype for you to test with in your non-production instance. Sitecore PowerShell Extensions $items = @(Get-Item -Path "master:\content\home") + @(Get-ChildItem -Path "master:\content\home") $expression = "\d{8}[T]\d{6}" foreach($item in $items) { $item.BeginEdit() | Out-Null if($item.Fields["__Created"].HasValue -and ($item.Fields["...


8

This might be an opinionated question/answer, but I don't think there are real disadvantages. Assuming you have xDB enabled (otherwise the answer is simple and you have to use sql) you should choose between analyticsFormsDataProvider (all in Mongo) or the combinedFormsDataProvider (analytics in Mongo, data in sql). Don't take the sqlFormsDataProvider as ...


8

There are a number of approaches people have taken to accomplish such a task. One of my preferences is to use the Sitecore PowerShell Extensions (SPE) module. With some knowledge of PowerShell, you can just about do anything with the content. Option 1 : Sitecore Item Web API Use whatever method available to you, such as the Item Web API. With SPE or ...


7

Sitecore Forms and WFFM are 2 different modules that happen to handle the same functionality (forms). There is no migration path available and at the moment there is no mention of anything like that either (on the contrary - when asked the Forms team said this was nowhere on the roadmap because the modules are too different). I have a website running on 9 ...


7

Here is a modified version of @vzaverugo's script to account for when you have multiple placeholders with the same name in a single rendering. Fortis will append an incremental seed suffix. Sitecore 9 also has a concept of an incremental seed suffix. This modified script can account for that, as long as you setup your Sitecore 9 seeds to match the same ...


6

The tool currently only supports upgrading from 7.2. You'll have 2 options when it comes to upgrading: Follow the standard upgrade process from Sitecore. You'll need to upgrade in order, so you'll need to follow the upgrade process to go from 8.0 update 2 to 8.1, then from 8.1 to 8.2 Stand up a new 8.2 instance, then migrate you current code and content ...


6

Etalon means "standard" or "reference" in many languages: https://translate.google.com/#auto/en/etalon If you decompile the Express Migration Tool, you'll see that this is all over the place. There's even a InitializeComparisonInstanceArgs! I'm fairly certain this refers to the "standard" item (i.e. untouched from original Sitecore installation). So you ...


5

I'm not sure if this would even work, or if the data would even make sense. The analytics data model from DMS in 7.2 is nothing like what xDB is now in 9.0. Even if you could somehow run tools to go through versions, I'm not sure you would be able to get value out of the resulting process. The xDB data migration tool for 9.0 is intended for 8.x where there ...


5

The issue may be related to your other question where it appears that you have some invalid date formats. From the StackTrace it looks like the issue is related to one of the Media facets. I would try disabling the 'Date uploaded' facet under /sitecore/client/Applications/Dialogs/SelectMediaDialog/PageSettings/Facets from the Core database to see if that ...


5

To inform item 7 in your preparation plan, look at the Sitecore Modules Compatibility Table for Sitecore XP: https://kb.sitecore.net/articles/541788 Ensure the modules you are using are compatible with 8.2. In my case, Active Directory isn't supported in 8.2, so we opted to upgrade to 8.1.


5

No - this is not possible. An SXA Page requires the SXA layout and the predefined structure for an SXA site. Either the site must be all SXA or it is just not SXA. The only way to convert your existing web-forms site into SXA is a complete re-write. You can have SXA and non SXA sites in the same instance, that will work fine. But you can't mix the page ...


5

I think that this is probably going to result in opinionated answers. But the question does have merit. tl/dr; Use both. Don't silo yourself into just one platform. The more data you have, the better/more accurate your data and reporting is. Then you can make informed marketing decisions based on that. Why Both I forget where, but I heard it said: ...


4

There is a quite elegant solution proposed in the sitecore community. Basically, what you have to do is that you need to attach your "old" master database to the "new" sitecore instance as another db, e.g. "master2" and then write a simple code to create items/copy the blobs over to the "new" sitecore master database. There is a good POC/instruction ...


4

I don't know if we can get this confirmed. But I'm almost certain, in this context, etalon refers to ETL - Extract, Transform, Load. https://en.wikipedia.org/wiki/Extract,_transform,_load Data extraction is where data is extracted from homogeneous or heterogeneous data sources; data transformation where the data is transformed for storing in the ...


4

I do not know if my answer will be full however it may help. If you are going to migrate a huge number of contacts and its interactions via xDB Data Migration Tool you need to know how to configure migration properly before run it. There are several things that can speed up migration. Max Thread Count (default: 1) Minimum Batch Size (default: 100) Page ...


4

http://integrationsdn.sitecore.net/xDBDataMigrationTool/v2.0.1/adding-custom-data/facets/index.html This will explain how to determine the data to migrate, how to write the components to store your data, how to map the data from MongoDB to xConnect Contact facets and how to use the needed pipelines.


4

I don't think you will be able to do that. Firstly, the views (.cshmlt) used by SXA won't be reachable by your pages if they are not part of an SXA website. You are going to have a lot of these: Secondly, you said your old pages are webform based. SXA is MVC only, so again you will need to rework this part of your instance if you want to use the ...


3

Sitecore support has filed a feature request to have the Express Migration Tool move data from the archives. In the meantime running a SQL query to get the data over works. You will need to get to Sitecore 6.6 Initial before executing the query as a new table was added to support the Archives. The lack of the data from this fourth table was the issue with ...


3

ItemManager.AddFromTemplate method uses your current language. You can wrap your code into Language lang = Language.Parse("your-lang-name"); using (new LanguageSwitcher(lang)) { ItemManager.AddFromTemplate... } if you want to change the new item language.


3

Also know that you will need to upgrade the .NET version to 4.5.2 for all projects. Are you using solr? Then consider upgrading that too. Here is the solr compatibility table and instructions for Solr configuration - https://kb.sitecore.net/articles/227897#note2


3

You have to migrate 6.5 to 7.2 through every revision with manual update. You may have a lot of issues to fix, especially if you are using indexes extensively. We did have a lot of issues as we were using indexes at a lot of places. Use Express tool to migrate from 7.2 to 8.2. Upgrade the rest of the customization/code through a manual process. Fix ...


2

For the record: The Express Migration Tool now Supports 6.6, so it's an manual Upgrade to 6.6 and than straight to up-to-date for you. https://dev.sitecore.net/Downloads/Express_Migration_Tool.aspx It also supports 7.5 now (which the old one didn't), however only if you go to 9.0.


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