Loosely they can be classified into three categories: Data loadersĭata loaders are basic import/export tools that works for very simple data migrations and can source data from CSV files as well as databases: Record types are again based on ids that varying from instance to instanceĭespite the pitfalls described above there are many tools that can help with the migration.
Salesforce relations are based on user ids (that are auto-generated) and importing relations based on external ids requires careful planning Mapping foreign keys to Salesforce relations Salesforce supports external ids that enable object identification/uniqueness checking but extra work is usually required to make sure that it works production) and are always auto-generated by Salesforce. These are unique from Salesforce instance to instance (e.g. Regardless of what types of data are being migrated, the following Salesforce specific challenges are usually the same: Object ids One of the most important questions to ask while building a scorecard is what constitutes a data migration success? Is it 100% accuracy, or maybe 99%? Do identical rules apply for all objects? What’s the cost of having perfect data vs. counting how many field values have been migrated and/or finding fields that contain error.
measurements on particular object properties (e.g.per-load snapshots (so trends in data quality/accuracy can be observed over time).Of course things usually get much more complicated than presented above with:
In essence what is does is by-type compare of row/object counts of source data (either directly or in staging database vs. The tool that we’ve been successfully using at Nextian is simple data migration scorecard. Oftentimes cleaning and consolidating your data may take significant amount of time and benefits of using new functionality may outweigh losses related to using data that is not perfect The same applies when consolidating data from multiple systems – rather than use a complicated logic in a staging database, it might be actually easier to clean and consolidate within Salesforce Depending on your source system(s) it may be easier to do data cleanup in Salesforce after the migration There are numerous, excellent Salesforce cleanup and de-duplication tools (such as DemandTools). The following factors are definitely worthwhile considering: Ease of cleanup While we believe that that’s the right approach, under some circumstances is may be easier to clean the data up after moving it to Salesforce.
The first instinct is to answer that question is to say ‘garbage-in, garbage out’ and attempt to clean the data up before migration. It is not a good sign if your implementation partner does not have a solid plan for data migration and/or tools up front - in that case push for answers ASAP.
0 kommentar(er)
