Moving custom fields between two Vicidial servers.

[edooze]

Hi all,

Let me start by saying what an amazing piece of software this is. Infinite kudos to the dev team, I'm continually astounded by what it is able to do (and how good I end up looking to stakeholders as a result). Thank you all concerned.

Now, onto the question: earlier today, I was forced to rebuild my VICIdial infrastructure due to an initial installation error. Live and learn!

My question is this: I would like to export all the custom fields from the old server and import into the new server. How do I do this, please? I have seen a couple of posts that alluded to moving them somehow in MySQL with a custom table. Unfortunately, while I'm lead to believe there is a way to do it, none of the threads I have seen have gone so far as to explain how. The fields took me hours to put together, so I'd really rather not have to build them all again.

My build details:
Vicibox 6 from .iso
VERSION: 2.12-485a BUILD: 150512-2225
Asterisk 1.8.32.2-vici
Single Server with additional dialer
No Digium/Sangoma Hardware
No Extra Software After Installation
All phones & carriers are SIP-based.
Currently only 2 agents live, but this re-build is in order to double that number.

Thanks in advance.

(post reference: http://www.vicidial.org/VICIDIALforum/v ... =4&t=33514 - no information that I am able to follow contained within.)

[edooze]

Well, I gave up on this. My attempts to get this done ended up breaking the server altogether (which I suspected they might) so I've just built them again. Tomorrow is set aside to re-create the custom fields and campaigns etc from scratch. Not a bad idea to clean everything up, anyway.

[Vince-0]

Did you not want to just dump and copy your asterisk database from the old server to the new?
You could then just delete the info from the front-end that wasn't required on the new server.

Vin.

[williamconley]

Interesting: Same answer as my previous post, so here's a link:

viewtopic.php?f=4&t=34488&p=117546&sid=06573ef3292032b8c530708c0dc984f7#p117546

[Vince-0]

Oh! The double posting.

Interesting: Same answer as my previous post, so here's a link:

viewtopic.php?f=4&t=34488&p=117546&sid=06573ef3292032b8c530708c0dc984f7#p117546

[paolo]

Hi,

I would also suggest the same thing, why not move the whole database from the old server to the new.

[edooze]

Okay, so even though this post is 4 or 5 years old, it's mine and I'm doing it again so I wanted to update it.
Refer sig for current build (build from SVN this time, ver 3088 currently)

I didn't want to import the whole database (then or now) because I am trying to get 'round a configuration issue. I am concerned that some of the old settings are incorrect, and as with a computer I think it's healthy to rebuild things every so often. Currently I am running the original (that this post refers to) the current, and the new servers alongside each other in parallel. The original servers don't get used, but they are there in case we need anything from them.

So, if I use a database backup I have from last week, is there a way to just import the custom leads, lists and fields - without the users and server config and so on?
Maybe it's easy enough (says the man with no knowledge whatsoever) to select the tables that are relevant and cut the rest out of the backup file?

Your thoughts appreciated.

[williamconley]

restore the backup into a fake/temp database.

mysqldump JUST the vicidial_list table and the custom_* tables and the table that contains the custom field definitions (whose name escapes me at the moment).

note that you'll probably want to back up those tables in the new system before you begin on the off chance this turns out to have a flaw in it.

it is possible to mysqldump without including the "drop/create" sequences if you need to merge. will work fine as long as the lead_id's and list_id's don't overlap.

* Verify table structure is identical before you begin or you will need to DEFINITELY avoid the drop/create
* Don't forget log tables if you may need them.