Import Tool Overview

SiteStacker supports bulk importing to make data management and migration easy. All imports will need to be in comma-separated value (CSV), most applications will allow you to export to this option. 

All import templates can be found in the Imports component under the Documentation tab. Once you identify the type of template you need, you can review the field formats and examples. However, the required items will be in bold. Each CSV file must possess a heading row with column names. If you select the desired file, the template will be provided for you with the correct column headers and file name mapping. Since a large number of templates are available, the system identifies the type of data in the file name with a leading number (EG 12. Person). Users can adjust the file name after the "." for the organization (EG "12. banquet attendees"). The number can be found

Steps

1. In SiteStacker Admin open the Import component.
2. Identify the correct import template for the data needed in the Documentation tab.
3. Fill in the spreadsheet with the data in the columns and format needed.
4. In the Import component Imports tab upload the completed file.
5. Once uploaded right-click the file and click Run Import In the Background.
6. Confirm the file imported successfully if not work through the import errors.
   
   

Import Errors 

Should an error be made while importing, the entire import will fail as a safety protocol. Specific errors can be identified by right-clicking and selecting show errors. This will allow specific rows and the error to be flagged. Should the import pass, but need to be adjusted you can right-click and select rollback which will delete the data in that import. 

Best Practices

• Only include the column you will be importing data to.
• Keep files at a reasonable size not more than 25,000 lines in the event there are errors or a rollback is required.
• For importing the first time keep the initial file to a sample for easy correction.
• The template mapping ID can be found quickly by revealing the ID in the template column.
• Excel oftentimes removes leading 0s when opening files like zip codes (e.g. 02108).
• System messages will not be sent based on import like address update but Spark automation will be triggered and could have emails triggered on both import and rollback.
• If a content item is missing from the import templates a Data Map needs to be set up in Architect > Data Maps.
• Image imports will need the file path once the image is imported into the file manager.