Process -- done, discussed with local community, decided that the data we collect is of public value and should be added to OSM.

Step 1.
Gain familiairty withe the basics of OSM -- done, long ago.
Revide what can go wrong with imports -- read.
Identify data you'd like to import -- done, it's trees.
Be aware of OSM licensing -- done, aware.
Review the import guidelines fully before beginning -- reviewed after I was pointed to them.
Contact the community -- done, interest was there.

Step 2.
Must obtain proper permission from the owner -- done. Users agree to make the data they collect public domain.

Step 3.
Documentation -- done after I was pointed to.
Wiki page with outline not created.  Information on converting the data, dividing the work, handling conflation, mapping GIS attributes to OSM tags -- not applicable.  I can create a page if absolutely necessary, but it would be of little actual value.

Step 4. Community buy-in.
Done.

Step 5. Import review.
Not applicable. No such thing as "data completely prepared and documented" as users are adding data on the go as they find it.

Step 6. Uploading.
Not sure how this is applicable.  "Let everyone know when you're done" -- not applicable.  Provide updates on efforts -- makes little sense, like, post daily digests? I don't understand how this should work.

Key considerations.
Discuss your proposed import -- discussed with the local community.

Document your import -- done on the organized editing activity page.

Use a dedicated account -- done, only doesn't have the "_import" suffix since it's not exactly an import, more a continuous exchange.

Use the right tags -- done, all documented.

Don't put data on top of data -- I don't understand, likely not applicable.

Take great care to avoid damaging the database -- done.  We only add/update nodes of specific types (trees), not doing anything complex, so hard to damage anything.