add csv parsing and begin proper import

devdocs/todo.txt

@@ -4,6 +4,18 @@
 
 Import feature
 	currently imports in the format as exporting, 
+	It works but it will bomb if there are linked records with wrong id's as it creates an exact copy of the json so not sure what use this would be as is
+	A proper feature for this would likely need to work with a more limited subset of records and it needs to be targetted to a specific task only like in v7
+	in v7 you don't import head office with client, just client alone as it limits the fields and collections to be imported
+	I'm thinking rather than throwing a generic solution at this it needs to be targetted to work direclty with the types in question
+	Almost need to ditch JSON export entirely?
+		actually, json export is ok, it's the json import that is sketchy, perhaps if it stripped fields?  Or created a head office from the viz field if found and ignored ID's?
+		do we want data transfer this way ayanova to ayanova supporting everything?? That sounds more like some kind of other synch tool or something
+
+	CSV should be the roundtrip format for ayanvoa and
+	Import should be all about onboarding and nothing else.
+	Lots of people use the update feature to update part prices etc so that should be a part of it
+
 
 	test recent code change for "importable" attribute back and front then test the items to see if they work
 	hasn't been tested in a while, confirm what works and what doesn't, remove anything that doesn't work, look at an import path for inventory