Jump to content

ClientExec Import Script Released


Recommended Posts

The passwords won't import - it's mentioned in the readme you'll have to notify users to reset their passwords afterwards.

 

hrrmm i missed that in the notes...

 

pity that it cant be moved i assume its using a different encryption process?

Link to comment
Share on other sites

Im just wondering if there is a description anywhere of the various table fields for the ticket related tables:

 


-- --------------------------------------------------------

--
-- Table structure for table `tblticketbreaklines`
--

CREATE TABLE IF NOT EXISTS `tblticketbreaklines` (
 `id` int(10) NOT NULL auto_increment,
 `breakline` text NOT NULL,
 PRIMARY KEY  (`id`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=7 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketdepartments`
--

CREATE TABLE IF NOT EXISTS `tblticketdepartments` (
 `id` int(10) NOT NULL auto_increment,
 `name` text NOT NULL,
 `description` text NOT NULL,
 `email` text NOT NULL,
 `clientsonly` text NOT NULL,
 `noautoresponder` text NOT NULL,
 `hidden` text NOT NULL,
 `order` int(1) NOT NULL,
 `host` text NOT NULL,
 `port` text NOT NULL,
 `login` text NOT NULL,
 `password` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `name` (`name`(64))
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=9 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketlog`
--

CREATE TABLE IF NOT EXISTS `tblticketlog` (
 `id` int(10) NOT NULL auto_increment,
 `date` datetime NOT NULL,
 `tid` int(10) NOT NULL,
 `action` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `tid` (`tid`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=4 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketmaillog`
--

CREATE TABLE IF NOT EXISTS `tblticketmaillog` (
 `id` int(10) NOT NULL auto_increment,
 `date` datetime NOT NULL,
 `to` text NOT NULL,
 `name` text NOT NULL,
 `email` text NOT NULL,
 `subject` text NOT NULL,
 `message` text NOT NULL,
 `status` text NOT NULL,
 PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketnotes`
--

CREATE TABLE IF NOT EXISTS `tblticketnotes` (
 `id` int(10) NOT NULL auto_increment,
 `ticketid` int(10) NOT NULL,
 `admin` text NOT NULL,
 `date` datetime NOT NULL default '0000-00-00 00:00:00',
 `message` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `ticketid_date` (`ticketid`,`date`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketpredefinedcats`
--

CREATE TABLE IF NOT EXISTS `tblticketpredefinedcats` (
 `id` int(10) NOT NULL auto_increment,
 `parentid` int(10) NOT NULL default '0',
 `name` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `parentid_name` (`parentid`,`name`(64))
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketpredefinedreplies`
--

CREATE TABLE IF NOT EXISTS `tblticketpredefinedreplies` (
 `id` int(10) NOT NULL auto_increment,
 `catid` int(10) NOT NULL,
 `name` text NOT NULL,
 `reply` text NOT NULL,
 PRIMARY KEY  (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketreplies`
--

CREATE TABLE IF NOT EXISTS `tblticketreplies` (
 `id` int(10) NOT NULL auto_increment,
 `tid` int(10) NOT NULL,
 `userid` int(10) NOT NULL,
 `name` text NOT NULL,
 `email` text NOT NULL,
 `date` datetime NOT NULL,
 `message` text NOT NULL,
 `admin` text NOT NULL,
 `attachment` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `tid_date` (`tid`,`date`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;

-- --------------------------------------------------------

--
-- Table structure for table `tbltickets`
--

CREATE TABLE IF NOT EXISTS `tbltickets` (
 `id` int(10) NOT NULL auto_increment,
 `tid` int(6) NOT NULL default '0',
 `did` int(10) NOT NULL,
 `userid` int(10) NOT NULL,
 `name` text NOT NULL,
 `email` text NOT NULL,
 `c` text NOT NULL,
 `date` datetime NOT NULL default '0000-00-00 00:00:00',
 `title` text NOT NULL,
 `message` text NOT NULL,
 `status` text NOT NULL,
 `urgency` text NOT NULL,
 `admin` text NOT NULL,
 `attachment` text NOT NULL,
 `lastreply` datetime NOT NULL,
 `flag` int(1) NOT NULL,
 `clientunread` int(1) NOT NULL,
 `adminunread` int(1) NOT NULL,
 `replyingadmin` int(1) NOT NULL,
 `replyingtime` datetime NOT NULL,
 `service` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `tid_c` (`tid`,`c`(64)),
 KEY `userid` (`userid`),
 KEY `status` (`status`(10)),
 KEY `date` (`date`)
) ENGINE=MyISAM  DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblticketspamfilters`
--

CREATE TABLE IF NOT EXISTS `tblticketspamfilters` (
 `id` int(10) NOT NULL auto_increment,
 `type` enum('sender','subject','phrase') NOT NULL,
 `content` text NOT NULL,
 PRIMARY KEY  (`id`),
 KEY `type` (`type`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

 

most of its self explanatory but theres a few fields in these tables im unsure of their function

 

for example the c and service fields in tbltickets

 

what im planning to do is to simply create a ticket category called historical and will move all tickets from CE into this department under the users ID and just assign them to one admin user

Link to comment
Share on other sites

I upgraded from Clientexec Version 3.1.4 to WHMCS 3.7.1 with no issues at all..

 

how old was your CE setup and how many clients?

 

Older CE installs had a lot of legacy tables and fields left laying around due to constant changes between 2,x 3.0 and 3.1

Link to comment
Share on other sites

how old was your CE setup and how many clients?

 

Older CE installs had a lot of legacy tables and fields left laying around due to constant changes between 2,x 3.0 and 3.1

 

Around 400 Clients, and have been using ClientExec for a year and a bit..

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

I just used it on CE 3.14 it added all the customers, it added all the invoices (but left them all unpaid) but it did not add all the domains, had to do those by hand, and it added people who had email the support desk with questions who were not customers. But it was fairly easy to delete those people because under services it said 0.

 

Once we started marking old invoices paid we realized it was sending out emails of the payment, so we stopped that and used PhpMyAdmin to mark the old invoices as paid so it would not send out invoices. It took about 3 hours to clean it all up including manually adding KB articles, but that is a lot faster than doing it all by hand and adding orders for everything.

 

Hopes that helps you.

 

Randy

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...
  • 3 months later...
  • 4 weeks later...

Just to add some input I have recently moved from CE 3.2.1 to WHMCS and the only problem I had was from where I had written a custom module in clientexec for Payflow payments and it did not create any invoices for them once they were inported.

 

However the standard parts of CE moved without any problems.

Link to comment
Share on other sites

  • 7 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated