Practice manager - XPM to Xero contact fields
Have logged this support query, which I also raised a number of years ago and cannot believe how this has not been fixed. Answer from support below:
In XPM there is no first and last name field for contacts, rather it is just one box for the Name field. While in Xero there are two fields to put a contacts first and last name separately.
So when a contact on a client syncs from XPM into Xero it is placed into the Last Name field as it recognises the name as one field. Currently, the only way to resolve this would be to go ahead and edit the fields in Xero manually.
It doesn’t look like this idea has been raised to Xero Product Ideas yet. Xero Product Ideas is a Xero website where our customers can share and support ideas for change.
I’ve included a link to the website where you can view and support current ideas or create a new idea to share your thoughts.

-
Rob Allen commented
The ability to input contact details in XPM and have it sync correctly to Xero and vice versa is a significant time saver, very logical and should be fixed asap.
Accepting the setting in XPM causes unnecessary additional work and should either be removed or fixed, not left for customers to tick thinking that it will be the time saver intended.
This is another issue due to the bolt on (after thought purchase) of XPM, where the integration of XPM was not written in to the existing Xero software but bolted on creating unnecessary duplications between Xero and XPM.
This bolt on is the major issue holding Xero software back. -
Alastair Abbott commented
Can't understand why this hasn't been fixed yet after so many years.
-
Isa Taylor commented
Xero can you please sort the contact field between XPM and Xero so we can use the system efficiently for invoicing?
It's creating a lot of extra time to update the contact details for every invoice... -
Evelyn Santos commented
I can't believe it either.
It's unacceptable that the same system can't correctly pull the data from XPM to the blue Xero.
We have been fixing this issue manually for months, yet support cannot look into it further.