About Moving Local Customers

Use the Move Local Customers utility to change an existing customer number at the local site to match a different customer number that exists (for the same customer) in another database site.

Suppose Sites A and B share customer data through replication. Site A contains Cust1, and Site B contains Cust2; but Cust1 and Cust2 are actually the same customer, with different numbers in the different sites. Since the number should match in both sites, you can change Cust1 to Cust2 in Site A. Using this utility, select Cust1 in the Current Customer list. Select Cust2 (of Site B) in the New Customer list. This moves the existing local customer record to a new local customer record. After processing, all records related to Cust1, such as customer orders, invoices, accounts receivable, and jobs are updated to specify Cust2 instead.

To move a record, these conditions must be met:

The current customer and sequence (Ship To) combination exists in Site A (where the utility is being run).
The new customer and sequence combination does not exist in Site A.
The new customer and sequence combination exists in Site B.
Currency codes of the current customer and the new customer are identical.
The Corporate Customer on both the current customer and new customer must match.
If the current customer sequence is 0, the new customer sequence must be 0.

The current customer's Bill To cannot be changed to the new customer's Ship To.

Note:

The posted balance and order balance of the customers involved in the move are not updated by this utility. You must run the Rebalance Customer Balances Utility to rebalance these values for all affected customers.

Example 1: The current customer has only sequence 0 (Bill To) and no Ship Tos. The new customer has sequence 0. In this case, the current customer is replaced by the new customer.

Example 2: The current customer has sequence 0 and sequences greater than 0 (Ship Tos). The new customer has sequence 0. In this case, the new customer is inserted in the database, but the current customer remains, as there are Ship Tos present for the current customer.

Example 3: The current customer has sequence 3. The new customer has sequence 5. The new customer sequence 0 must exist in the current site before the move is performed and all information for the new customer sequence 0 remains unchanged in the current site after the move. Sequence 5 for the new customer gets added to the current customer site. Sequence 3 for the current customer is removed from the current customer site. The Bill To area of the Customers form for the new customer is the same as it was before the move. The Ship To information such as that on the Codes tab on the Ship To form for the new customer sequence is copied from Site B.