Moving polices, apps, etc. to new client

[Billy Welsh]

We need a "fresh start" with a particular account, so we have set up a duplicate and now we need to move the current policies and apps to the new TAM account.

It has been years since I've done this.  I seem to recall the only way is to move them to Prospects, then back to Clients.  Is this true, or is there a better way?

Thanks as always!

[Lance Bateman]

That's the generally accepted way - just remember, you won't get any claims or accounting info in the move.

Why not just "rename" the old file to the new one, or is it a totally different customer and the old one was just on the wrong one, or you're only looking to "move" the one policy, not others?

[Billy Welsh]

Correct - we are looking only to move some of the policies.  Otherwise it would be easy.

[Jan Regnier]

Why don't you move the policies you DON'T want on the file to prospects and then delete them from the client?

That way you don't lose any other details that don't move (not sure of things that don't move) if you move the "keeper" policies to prospects and then back to clients.

[Orlando Alonzo]

I like Jan's suggestion. I think you could also try conglomerating and only default the selected policies you want to keep.

[Jeff Zylstra]

Why don't you move the policies you DON'T want on the file to prospects and then delete them from the client?

That way you don't lose any other details that don't move (not sure of things that don't move) if you move the "keeper" policies to prospects and then back to clients.

OK, this raises a question for me.  When you move policies and other data to prospects, you don't actually "lose" that data, correct?  I just thought that there was no mechanism to view that data in prospects, but if you moved it back to a customer file, it would still be there.  Can anyone confirm or refute this?

[Jan Regnier]

Why don't you move the policies you DON'T want on the file to prospects and then delete them from the client?

That way you don't lose any other details that don't move (not sure of things that don't move) if you move the "keeper" policies to prospects and then back to clients.

OK, this raises a question for me.  When you move policies and other data to prospects, you don't actually "lose" that data, correct?  I just thought that there was no mechanism to view that data in prospects, but if you moved it back to a customer file, it would still be there.  Can anyone confirm or refute this?

I don't think you lose it....just no access like you said.

[Lance Bateman]

Accounting, claims info don't go to Prospect, so won't move to your new customer when you move back.

Unless you delete things when you move, they'll still be there - but attached to the wrong place.  No way around that.

[Billy Welsh]

Without getting in to all the gory details, the desire is to keep the policies that are there, expired & all, while setting up a new account for the current year policies.

(Yes, I know, clean-up would make more sense, but it is not my call.  All I can do is offer advice and deal with the decision made).

[Lance Bateman]

Okay - just a suggestion - be sure to "conglomerate" the two files.

[GeorgeW]

If you just want to copy the billing screens and applications, you can do what oalonzo said. Conglomerate the customers and when you add a billing screen (to the child, I think) it will ask if you want to copy policies. Works great and no moving back and forth to prospects.  You only get billing screens/policies but that sounds like all you want anyway.

I like Jan's suggestion. I think you could also try conglomerating and only default the selected policies you want to keep.

[Billy Welsh]

I never cease to be amazed at what you guys can teach me.  Thanks so much!!! 

I had no idea that little gem was there.  SO much better than the Prospects route.