I have a client whos software contains lists of companies.
A company can have users, locations and other attributes associated with it.
Users have complained that they cannot merge two companies together.
When a company is merged the user must be able to pick:
a)which company is going to inherit the data of the other b)which data of each company to exclude
Here is an example wireframe of the kind of thing I have in mind:
User has clicked Company A from a table. 'Merge-able' companies are provided in a list. The user has selected Company B. The user can view (and edit) details of each company by following the View details link under the drop down menu. When the user clicks Next a list of Company locations of Company B is provided. The user selects which ones to merge and clicks Merge. The companies details are merged.
(There might be an intermediary step where the user selects which users to merge but that's not important for the purposes of illustrating the scenario.)
My question: I'm not sure this is the best approach as it fragments the process into steps. Would it be better to display data about each company side by side? Have you any precedent patterns?
I am aware that similar questions have been asked for merging contact data but I feel this question is different enough to warrant its own thread.
Edit updated wireframe
BTW both non merged companies are held on the system so the merging process is never irreversible.
The user can specify which profile details to use as default via radio control (looking at it again, these aren't needed as the drop downs define this!)
The choose users/locations brings up easy to check list of all users/locations from both companies, default 'all' is checked but user can deselect certain users/locations if s/he wants.
Ignore the post it