Are you starting an on premise to cloud data migration project? Did you ever think about how much space you might need for your online platform or how to handle data that might be related to users who no longer exist? If these questions or any other concerns have been plaguing you about your migration project you'll want to check out this presentation and the accompanying recorded webinar:
http://www.eweek.com/ebooks/188440710/96000/11280310/215687?domain=http://www.eweek.com&ft=assetform_ab1&qset=CONTEXT_STEP1&css=http://i.eindx.com/b2btechleadform/eweek/styles/style.css&mcss=http://i.eindx.com/b2btechleadform/eweek/styles/style_email.css
4. Who is PowerObjects?
• Professional Services Consulting Firm delivering Dynamics
CRM solutions from start to go-live and support following
• Microsoft Dynamics CRM Partner of the Year 2012 & 2013
• Gold Certified/ Inner Circle Microsoft Partner (Top 1%)
• Office365
• 60+ Dynamics CRM-specific consultants/ developers
• Twin Cities headquarters with regional offices
• Key CRM implementation partner for Microsoft
• Ensuring Dynamics CRM implementation success
• PowerPack enhancements
Make sure all active users have been created in CRM Online Organization. Ideal to match fullname value between systems for Scribe lookups.
Create a temporary role that is a copy of the System Administrator Role and apply to all users. This will be deleted after the migration.
Purchase enough space on the CRM Online subscription to store all of your migrated data along with room for growth.
Decide what data will be migrated
Do you need old activities?
Do you need Inactive records?
Is there a cutoff date that defines “old data” that will not be migrated?
Prepare for limitations
Items that cannot be migrated
Modified On date time values
Modified By user values
User Options
Saved Personal Views
Team Membership
Security Role Assignment
Workflow in a Waiting State
System Jobs
System Logs
If the user cannot be located in the CRM Online system, the value will be set to the user account that is running the migration or another user as defined by you.
Keep the original GUID of records from your source system, this is needed for matching related records.
While mapping each entity, use overwritecreatedondate field to keep original createdon value.
Migrate any lookup entities first (ex: States)
Migrate Accounts, Contacts, etc. Run Updates to populate fields to values for records that were not available (ex: Primary Contact)
Migrate the bulk of your data while your users work OnPrem, then migrate the delta to get records that have changed or been added since the first migration.
User Acceptance Testing
Row Counts
Seed Q:
1.Do I need to have a partner for this?
2.What are the best practices in deciding on what data to migrate? I know we hit on a cut-off date but what other factors should we look at?
3. Security in the cloud? Would a hybrid be the best choice especially for healthcare?
It’s a quick e-book that highlights some of the challenges you may face with data migration and why some organizations know they need to migrate but are apprehensive to do so and how if they don’t start now it will affect internal stakeholders.
The e-book hits on taking a careful & thoughtful approach to comprehensive
Integration - it will result in a robust solution that will earn rapid user
adoption & deliver extraordinary results