Skip to main content

Experience profile is empty after converting old DMS data

Hi,

I wrote a post a few weeks ago with regard to Sitecore upgrading from 7.2 to 8.1. Everything went well, except  I couldn't get Experience Profiles from historical data.

I contacted with Sitecore support and after a few weeks I received the script for xDB's Contacts collection. I ran that script, performed the report db rebuild process (which is described here) and the result was more than 3 million document in sitecore_analytics_index. So everything is working well after the upgrade process.

Here is the mongo script:
db.getCollection('Contacts').update({}, {$unset: {"System" : "", "Identifiers" : "", "ConversionInfo" : "", "Lease" : ""}}, {multi:true})
view raw experiencefix hosted with ❤ by GitHub
Labels:

Comments

Post a Comment

Popular posts from this blog

Sitecore 8.1 upgrade from 7.2

In the following post, I would like to share my experiences with regard to Sitecore upgrading and highlight some points. We have a project which is running on Sitecore 7.2 update 4. (This project was originally developed on Sitecore 6.5, but we upgraded it a few months ago) We have decided to upgrade that project to 8.1.  Probably you know there are more ways to move a project to Sitecore 8. e.g: You can create a new Sitecore 8 instance and transfer your content into the new instance. But we wanted to try the in-place upgrade process when the process modifies the existing instance. Moreover, we were curious how we can move old DMS data to xDB.  Step 1: Upgrade to 7.5 (Initial release) If you are already on Sitecore 7.2 you can move your solution to 7.5. Probably this is the hardest and slowest part of the path. Note: Always read and follow the upgrade notes from Sitecore before you start.  Before you start 7.5 upgrade, you will need: 7.5 update package (in...
7 comments
Read more

Create custom Sitecore Search Crawler

Hello, I would like to show an implementation of a custom crawler which prevents indexing items under specific paths. This is useful when you want to exclude a whole subtree from your index configurations. e.g: You have a multi-site structure which contains 3 sites. You want to implement search funcationlity on one of the sites (call site A) and visitors should be able to search in site B content, but content from site C should not be visible, and you dont want to break relevancy of the search result. The first step is create a class, call CustomCrawler.cs. This class should be derived from SitecoreItemCrawler class. Now, you can overwrite IsExcludedFromIndex method. If you are ready, you should change crawler in the search config. Add paths to ExcludeRoot node and seperate them by pipes. That's all. Now items are not indexed from the excluded paths, and you don't break the relevancy.
2 comments
Read more

Sitecore SPEAK3 Starter Template

Hi, I've created a starter application for SPEAK3 development. Source is available on GitHub . This starter application is based on offical SPEAK3 reference application which is available on the Sitecore's page . Starter template has the following features app.module.ts contains several Sitecore SPEAK component import You can check what different components look like in this repository Sample service page which has a sample service Sample service consumes mock service in disconnected  mode A sample datacontract Sample mock service which produces mock data in disconnected mode How to use Starter template Clone Github repository run npm install  command in the project directory run npm run start  to run project in disconnected mode Open http://localhost:4123 in your browser How to build starter application and add to your Sitecore Run npm build  command in project directory Copy < projectroot>\dist  folders content to <sit...
2 comments
Read more