![]() ![]() Using modern ETL tools, such as Jitterbit, Informatica Cloud Data Wizard, Starfish ETL, Midas and the like, can reduce the effort, increase quality of data. ![]() Errors directly impact quality and integrity of the Data in destination system. it increases effort and plays key role in estimation.Īutomate the process – automation means less human interactions, which leads to lesser errors. If not, need to check for the alternative ways which may require format conversion or data transformation. It is always advisable to check if Salesforce supports all the field formats available in legacy system. Compatibility of Data – Compatibility of data includes the format of the fields/column.The more number of lookups/master-details fields, the more will be complexity of the data migration. Number of Lookup or Master-details fields – The most challenging part of data migration is to create/map correct parent child relationship.More number of fields in a table, more will be the effort to map and load. Mapping of Fields – The number of columns of table needs to map with Salesforce Object fields.Creating custom object is an additional development work and it may increase estimation. It is also advisable to check if Salesforce out-of-box objects can be used or custom objects needs to be created. Mapping of Objects – It signifies the number of tables need to migrate data to Salesforce. ![]() Informatica Cloud Data Wizard, Jitterbit, SQL Servers etc.)īelow are the factors which needs to be considered when migrating data to Salesforce: Estimation should also include the middleware software/tool license costing (e.g. In many scenarios team needs to perform same task multiple time due to several environment specific errors. The approach must be agreed upon and communicated to all business and technical stakeholders so that everybody is aware of when and what data will appear in the new system.Įstimation – As described earlier, Data Migration is very complex activity which need resources, planning and modern tools. This means that extracted data needs to go through a series of functions in preparation, after which it can be loaded in to a target location. In the context of the ETL (Extract, Load and Load) process, any data migration will involve at least the transform and load steps. ![]() An entity level scope and plan must be created at the project’s beginning, ensuring no surprises. It is a complex activity, deserving a separate project, approach, plan, budget and team. While this might seem pretty straightforward, it involves a change in storage and database or application. Make Migration a Separate Project – In the software deployment checklist, data migration is not an “export and import” item handled by a clever “push one button”. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |