We are struggling to get our corporate and corporate contact records in a useable format now that we are on V11.
We are currently in the process of moving the alias for the company name that was created during migration to Salutation 2, so that we can print mailing labels for these folks.
I want to make sure as we enter new corporate contacts we do it in a way that makes sense. I'm just wondering wheteher anyone has gotten around to documenting any data entry standards for new corporate or corporate contacts that they would be willing to share with us.
We haven't converted to V11 yet, and are stil in the mapping stages so consider what I say below with a grain of salt:
The way that we're mapping it right now is creating a Pri Org Contact & Alt Org Contact as new types for Address, Email, & Phone then keeping it on the company record. Some of our constituents are at multiple companies, and it wouldn't be possible to pull just one (or have a preference of which of the two to pull) if there were two Business Address' in one person's account. It also ensures we don't mistakenly market or contact them at their business in case the address types in phone, mail, or addresses weren't flagged correctly in their home/personal account. We're then also adding the Primary & Alternate contacts as affiliates, under the "Employee" type. For us we need to ensure there'll only be 1 primary & 1 alt contact per business and not being able to create duplicates of these types for affiliations was the decision behind only using the "Employee" type.
In the end look, our record for the Doe Foundation will look like this:
Address Type: Default
Doe Foundation123 B StreetNew York, New York 51263
Dear Sir/Madam----------------------------------------------------------------
Address Type: Org Prim. Contact
Jane DoeCEODoe Foundation123 B StreetNew York, New York 51263
Dear Jane
Affiliation: Jane Doe (Employee)
And if you forsee some reason to want to contact the personal record of the primary contact on that organization then you'll want to add "Primary" & "Alternate" types as well for affiliations. Runs the risk of duplicates however (which was a big enough problem for us to not consider creating separate types for), so you may get more than you bargained for by implementing this additional method.