Changes

For a successful migration, you will need the appropriate resources in order to first decide and plan which data you need migrated, and then to extract and transform this data from your existing system. It should be noted that migration of your historical information is not necessary for a successful implementation of SmartSimple, and is not recommended for clients without the appropriate resources. 

Exceptions to these requirements '''Note:''' The migration of your historical information is not necessary for a successful implementation of SmartSimple, and responsibilities is not recommended for clients without the appropriate resources. There are listed belowexceptions to this however, where SmartSimple will assist or take on the full responsibility of the data migration for you. These exceptions are listed below.

===Review of Previous Current System===

* ''Entity Integrity '' - every record set must possess a unique identifier for each record. This can be comprised of multiple columns. For example, for contacts, emails must be unique and contain no duplicates.* ''Referential Integrity '' - every related record set must be linked by their respective unique identifiers. For example, a contact associated to an organization should be indicated by the contact record containing the unique identifier for the organization.* ''Standard Data Type Formatting '' - standard data types should be formatted appropriately. For example, date values should be formatted to 'YYYY-MM-DD', and date/time values to 'YYYY-MM-DD hh:mm:ss'. Number values should be formatted to decimals '######.####' without currency, comma, or other formatting.

* ''Other Field Formatting '' - if you wish to validate and enforce formatting conventions beyond the strict data types above, you will need to ensure that your data is similarly formatted. For example, if you wish to format phone numbers to '(###) ###-####', or zip codes to '#####-####' your data must be similarly formatted first.* ''Picklist Integrity '' - for any fields that should be restricted to a pre-defined picklist of values, you should ensure the integrity of these field values. For example, address states should all be the full name, e.g. 'New York', or all be the abbreviation, e.g. 'NY', but not a mix of both, and not contain spelling errors or typos.* ''Duplicate Checking '' - while you may satisfy that every record possesses a unique identifier, your data may still contain duplicate records. These should be resolved with duplicates being merged or deleted. For example, consider records that may have misspelled information e.g. organizations named 'Oranges Inc.' and 'Oranges Incorporated'.

'''Example:''' The below is an example of a correctly formatted 3-column CSV that accounts for line breaks and escapes embedded quotes. <pre>"Organization Name","Organization ID","Description""Oranges Inc","4321","Peel.Eat.Repeat.""Bananas Ltd","8756","You're going to go ""bananas"" over our product!"</pre> ===Data TransformTransformation===

As the project team designs your SmartSimple instance system and architecture, we will work closely with you to design the final data translation to migrate your data into SmartSimple. SmartSimple will create a transform mapping and review this with you.

During the course of a project implementation there will be two data loads conducted. One at the beginning of the project to allow you to verify the information that is input into SmartSimple. A summary report will be provided to you to review. [[File:DataImportSummaryReport.jpg|thumb|none|middle|500px|Data import summary report.]] The second data load will be at the end of the project for the final migration from your current system to SmartSimple. For the this final data load, you can expect between a 3-5 day maintenance window where we ask you to freeze any updates to your current system in order to cut over and transition to SmartSimple.