Laserfiche WebLink
OPEHGOV <br /> • Location information (Records will only be linked to locations if <br /> an ID, MBL,or other logical link is provided to match up to the <br /> Customer's address integration) <br /> • Fees and payments(will be migrated as form data) <br /> • Inspections (will be migrated as form data) <br /> • Contractors,work description and other Form Data <br /> • Other multi-entry form data <br /> Data Migration and File Requirements: <br /> • OpenGov will accept: <br /> o Text Delimited File(i.e. CSV) <br /> o Excel (.xlxs file) <br /> • OpenGov will not accept: <br /> o Non-relational database <br /> All other databases require additional scoping and may not work <br /> Data migration does not include: <br /> • Cleaning of any corrupted data <br /> • Creation and linking of applicant accounts <br /> • Integration of historical fees and payments into workflow or <br /> financial reports. <br /> • Logs of permit changes <br /> • Migration of any data into the workflow(i.e. pending or <br /> completed sign-offs,fee steps,document issuance,inspections). <br /> • Permit attachments <br /> • Import of contractor database <br /> • Creation of projects or other relationships between permits <br /> Document OpenGov will import documents attached to either migrated permits or <br /> Migrations locations provided through a Master Address Table(MAT) integration. <br /> • Requirement: <br /> o Dependent on having a Historical Migration and/or MAT <br /> Integration <br /> o Customer must provide a single file(Excel,CSV,etc)with <br /> one row per document,with a unique identifier for the <br /> related permit or location,and the file's physical location <br /> (a file path or URL). <br /> o Customer will need to either provide a copy of the files or <br /> grant PLC access to the file locations in order to migrate <br /> them. <br /> o The folder structure of the documents provided must <br /> reflect the paths provided in the file. <br /> o Data cleanup/correction is not included <br /> 18 <br />