Jump to content
  • 0

Whmcs Migration


SimplyDigitalHosting

Question

Hello, I have a few questions for supported things. Do you currently have modules for the following system/services?

 

  • Virtualmin
  • Enom Domains

I am also interested to know if you have any recommended live chat software as we are using the WHMCS chat addon via their stardevelop partnership.

 

Also curious to know what features compared to WHMCS you don't currently have. We are open to internal development but would like not to have to invest extra time to make up for present shortcomings.

 

I also believe you have a WHMCS data importer correct? We have built systems around WHMCS so its vital to have a table conversion so we can work on compatibility for the system with our systems.

 

Thanks.

Link to comment
Share on other sites

Recommended Posts

  • 0

Hello, I have a few questions for supported things. Do you currently have modules for the following system/services?

 

  • Virtualmin
  • Enom Domains

 

We have a beta Enom module that is scheduled to ship with 3.1. If you have an installation of 3.0 (paid or trial is fine) I can send you the beta module for testing. We do not currently have a Virtualmin module.

 

I am also interested to know if you have any recommended live chat software as we are using the WHMCS chat addon via their stardevelop partnership.

 

I don't have one in particular I can recommend, but there are several really good options available. I would probably recommend some feedback from the community on this.

 

Also curious to know what features compared to WHMCS you don't currently have. We are open to internal development but would like not to have to invest extra time to make up for present shortcomings.

 

There are quite a few things that are different, largely a lack of extensions at the moment.. that's the biggest issue, and one we're working on. In terms of core features, probably configurable options (scheduled for 3.1) and proforma invoices (scheduled for 3.2 I believe) Blesta does a lot of things better, like better accounting of transactions and invoices.

 

I also believe you have a WHMCS data importer correct? We have built systems around WHMCS so its vital to have a table conversion so we can work on compatibility for the system with our systems.

 

Thanks.

 

We have an importer that imports virtually everything except packages and services. We should be making an updated importer available with support for packages and services this week. It will be available on the forums when it's ready.

 

I suggest downloading Blesta from the home page, installing and selecting the "start a 30 day free trial" option. Play around with it, let us know what you think and if you aren't sure if a particular feature that you need exists or not. Our development is prioritized by what people need most going forward.

 

Thanks!

Link to comment
Share on other sites

  • 0

Is there any ETA on 3.1 as the two biggest deal-breakers currently are pro-rated invoicing/upgrades and configurable options as we MUST be able to give the user the option to pick some settings. Its the core of many of our products.

 

I also read on twitter that someone supposedly donated code for Virtualmin support. Was there any work done on that.

 

I am extremely interested in Blesta due to being open source (mostly), but there are just several things that we require to function and I prefer not to go with another closed source system if possible. Whatever we pick will cause a significant time investment for compatibility.

 

In the end we are just plain fed up with WHMC's PHP4 style code hacks and need a real solution where we don't need to update every week due to a public disclosure on SQLi.

 

[/end rant] :)

 

 

I like Livechatinc and baseactive (I think the name is) a forum member owns it, really nice.

 

We picked the WHMCS "live chat" as it allowed unlimited operators/departments. The per-seat stuff gets expensive VERY quickly. Thanks for your input though.

 

Also I think it would be in Blesta's interest to form a partnership like WHMCS did to get am affordable integrated live chat system.

Link to comment
Share on other sites

  • 0

Is there any ETA on 3.1 as the two biggest deal-breakers currently are pro-rated invoicing/upgrades and configurable options as we MUST be able to give the user the option to pick some settings. Its the core of many of our products.

 

I also read on twitter that someone supposedly donated code for Virtualmin support. Was there any work done on that.

 

I am extremely interested in Blesta due to being open source (mostly), but there are just several things that we require to function and I prefer not to go with another closed source system if possible. Whatever we pick will cause a significant time investment for compatibility.

 

In the end we are just plain fed up with WHMC's PHP4 style code hacks and need a real solution where we don't need to update every week due to a public disclosure on SQLi.

 

[/end rant] :)

 

 

 

We picked the WHMCS "live chat" as it allowed unlimited operators/departments. The per-seat stuff gets expensive VERY quickly. Thanks for your input though.

 

Also I think it would be in Blesta's interest to form a partnership like WHMCS did to get am affordable integrated live chat system.

 

I'm not sure it depends on the contract between starlight and whm** like with Modulesgarden their agreement to only do their modules. Also I believe there was talks about a Blesta Livechat in the future :). So you may be in luck but it's just talks.

Link to comment
Share on other sites

  • 0

Is there any ETA on 3.1

 

It's in active development, and is very likely that it will be in beta sometime next month.

 

I also read on twitter that someone supposedly donated code for Virtualmin support. Was there any work done on that.

 

I haven't seen that, do you know who said that?

 

I am extremely interested in Blesta due to being open source (mostly), but there are just several things that we require to function and I prefer not to go with another closed source system if possible. Whatever we pick will cause a significant time investment for compatibility.

 

In the end we are just plain fed up with WHMC's PHP4 style code hacks and need a real solution where we don't need to update every week due to a public disclosure on SQLi.

 

[/end rant] :)

 

All very good reasons!

 

We picked the WHMCS "live chat" as it allowed unlimited operators/departments. The per-seat stuff gets expensive VERY quickly. Thanks for your input though.

 

Also I think it would be in Blesta's interest to form a partnership like WHMCS did to get am affordable integrated live chat system.

 

Thanks for the suggestion, we are certainly open to the idea of partnering with a live chat company.

Link to comment
Share on other sites

  • 0

Got the virtualmin info off twitter: https://twitter.com/blesta/status/19014157684

 

And I am looking forward to possibly beta-testing 3.1. I figured it would be a longer period but don't mind waiting a month to plan migration. I read though that one of the features we require is set on 3.2? If we can't get everything we have stated so far we will likely have to keep looking as we don't want to write core-code un-needly..

 

Thanks.

Link to comment
Share on other sites

  • 0

What modules are you waiting for?

 

Laundry list: :)

 

-I'm in Spain, so I need a payment module for Sermepa, used by 100% of the Spanish banks. That one should be easy to do.

 

-I would need to test the LogicBoxes module thoroughly, especially for .es domains, that have some extra requirements/quirks. It took us years (literally) to solve this in WHMCS.

 

-I also need a module for Spanish registrar Virtualname.

 

Those are the basics. Then there's the 10-12 modules we had to add to WHMCS just to get it working properly and issuing invoices that are legal in the EU, etc. Nothing fancy. We just sell domains and three different hosting plans, and have a few thousand customers.

 

If you guys are for it, I would love to privately send you a (very) long list of everything we had to do to our WHMCS, with the explanations behind it.

Link to comment
Share on other sites

  • 0

Laundry list: :)

 

-I'm in Spain, so I need a payment module for Sermepa, used by 100% of the Spanish banks. That one should be easy to do.

 

-I would need to test the LogicBoxes module thoroughly, especially for .es domains, that have some extra requirements/quirks. It took us years (literally) to solve this in WHMCS.

 

-I also need a module for Spanish registrar Virtualname.

 

Those are the basics. Then there's the 10-12 modules we had to add to WHMCS just to get it working properly and issuing invoices that are legal in the EU, etc. Nothing fancy. We just sell domains and three different hosting plans, and have a few thousand customers.

 

If you guys are for it, I would love to privately send you a (very) long list of everything we had to do to our WHMCS, with the explanations behind it.

 

 

They have everything you need for a .es domain mate:

// .ES
Configure::set("Logicboxes.contact_fields.es", array(
	'attr_es_form_juridica' => array(
		'type' => "hidden",
		'options' => "1"
		/*
		'label' => Language::_("Logicboxes.contact.es_form_juridica", true),
		'type' => "select",
		'options' => array(
			'1' => Language::_("Logicboxes.contact.es_form_juridica.1", true),
			'39' => Language::_("Logicboxes.contact.es_form_juridica.39", true),
			'47' => Language::_("Logicboxes.contact.es_form_juridica.47", true),
			'59' => Language::_("Logicboxes.contact.es_form_juridica.59", true),
			'68' => Language::_("Logicboxes.contact.es_form_juridica.68", true),
			'124' => Language::_("Logicboxes.contact.es_form_juridica.124", true),
			'150' => Language::_("Logicboxes.contact.es_form_juridica.150", true),
			'152' => Language::_("Logicboxes.contact.es_form_juridica.152", true),
			'164' => Language::_("Logicboxes.contact.es_form_juridica.164", true),
			'181' => Language::_("Logicboxes.contact.es_form_juridica.181", true),
			'197' => Language::_("Logicboxes.contact.es_form_juridica.197", true),
			'203' => Language::_("Logicboxes.contact.es_form_juridica.203", true),
			'229' => Language::_("Logicboxes.contact.es_form_juridica.229", true),
			'269' => Language::_("Logicboxes.contact.es_form_juridica.269", true),
			'286' => Language::_("Logicboxes.contact.es_form_juridica.286", true),
			'365' => Language::_("Logicboxes.contact.es_form_juridica.365", true),
			'434' => Language::_("Logicboxes.contact.es_form_juridica.434", true),
			'436' => Language::_("Logicboxes.contact.es_form_juridica.436", true),
			'439' => Language::_("Logicboxes.contact.es_form_juridica.439", true),
			'476' => Language::_("Logicboxes.contact.es_form_juridica.476", true),
			'510' => Language::_("Logicboxes.contact.es_form_juridica.510", true),
			'524' => Language::_("Logicboxes.contact.es_form_juridica.524", true),
			'525' => Language::_("Logicboxes.contact.es_form_juridica.525", true),
			'554' => Language::_("Logicboxes.contact.es_form_juridica.554", true),
			'560' => Language::_("Logicboxes.contact.es_form_juridica.560", true),
			'562' => Language::_("Logicboxes.contact.es_form_juridica.562", true),
			'566' => Language::_("Logicboxes.contact.es_form_juridica.566", true),
			'608' => Language::_("Logicboxes.contact.es_form_juridica.608", true),
			'612' => Language::_("Logicboxes.contact.es_form_juridica.612", true),
			'713' => Language::_("Logicboxes.contact.es_form_juridica.713", true),
			'717' => Language::_("Logicboxes.contact.es_form_juridica.717", true),
			'744' => Language::_("Logicboxes.contact.es_form_juridica.744", true),
			'745' => Language::_("Logicboxes.contact.es_form_juridica.745", true),
			'746' => Language::_("Logicboxes.contact.es_form_juridica.746", true),
			'747' => Language::_("Logicboxes.contact.es_form_juridica.747", true),
			'877' => Language::_("Logicboxes.contact.es_form_juridica.877", true),
			'878' => Language::_("Logicboxes.contact.es_form_juridica.878", true),
			'879' => Language::_("Logicboxes.contact.es_form_juridica.879", true)
		)
		*/
	),
	'attr_es_tipo_identificacion' => array(
		'label' => Language::_("Logicboxes.contact.es_tipo_identificacion", true),
		'type' => "select",
		'options' => array(
			'1' => Language::_("Logicboxes.contact.es_tipo_identificacion.1", true),
			'3' => Language::_("Logicboxes.contact.es_tipo_identificacion.3", true),
			'0' => Language::_("Logicboxes.contact.es_tipo_identificacion.0", true)
		)
	),
	'attr_es_identificacion' => array(
		'label' => Language::_("Logicboxes.contact.es_identificacion", true),
		'type' => "text"
	)
));
Link to comment
Share on other sites

  • 0

They have everything you need for a .es domain mate:

 

Almost, but not there yet. We need to ask for 5 additional domain fields:

 

1. Registrant type

2. Registrant document type

3. Registrant document number

4. Domain contact document type

5. Domain contact document number

 

This is needed for domain transfers too, something WHMCS hasn't been able to fix. We have a third party module because of this.

Link to comment
Share on other sites

  • 0

Almost, but not there yet. We need to ask for 5 additional domain fields:

 

1. Registrant type

2. Registrant document type

3. Registrant document number

4. Domain contact document type

5. Domain contact document number

 

This is needed for domain transfers too, something WHMCS hasn't been able to fix. We have a third party module because of this.

 

The only fields available for ES contacts (according to the logicboxes API docs) are:

 

es_form_juridica

es_tipo_identificacion

es_identificacion

 

If you can provide documentation outside of that we'll take a look, but from what I can tell the module fully implements the capabilities of the logicboxes API with respects to .es domains.

Link to comment
Share on other sites

  • 0

Yes, the documentation is not clear about this. We've had to work closely with LB for quite some time to solve this conundrum. Here's the key:

 

The Registrant Contact of a .ES domain name may either be a natural person/individual or a company. However, the Admin, Technical and Billing Contacts must be natural persons/individuals only.

 

-If the Registrant is a person, then the Registrant and the Contact are the same and they have the same es_form_juridicaes_tipo_identificacion and es_identificacion

-If the Registrant is a Company, then it gets more complicated, because the Company can't be a contact, the contact needs to be a person. So you have to supply two sets of fields, one for the Registrant (Company) and one for the domain Contact (person).

 

Am I making sense?

Link to comment
Share on other sites

  • 0

The logicboxes module simplifies this by forcing all contacts to be natural persons/individuals only. That is, "es_form_juridica" is always "1".

Yes, that doesn't work anymore, or it shouldn't. If it does, it creates wrong contacts that can be cause for termination of the domain.

 

I manage a few thousand .es domains through a LB registrar, my company is established in Spain and while not accredited myself, I helped a registrar get accredited a few years back. If you want me to help, I'm happy to.

 

Anyway, I'm don't want to hijack the thread. Contact me privately if you need me.

Link to comment
Share on other sites

  • 0

The logicboxes module simplifies this by forcing all contacts to be natural persons/individuals only. That is, "es_form_juridica" is always "1".

 

So if your customer is a company, they can't own the domain. How does Blesta solve this? 

 

To this problem, add this one: the domain Registrant can't be changed or modified without a domain transfer.

Link to comment
Share on other sites

  • 0

I am also interested to know if you have any recommended live chat software as we are using the WHMCS chat addon via their stardevelop partnership.

 

I've been really happy with OCC (OnlineChatCenters). Goofy name, but it just plain works. Took me a while to get used to hosted (though we migrated to hosted for a reason, and away from LiveZilla that we used for years), but it works well, very quick response and light resource usage, and is very reasonably priced.

 

In WHMCS it was relatively easy to set up a connection between the LiveChat transcripts (a new support department) and WHMCS. I'm assuming it will be the same with Blesta. You don't get the full intergration as with Stardevelop, but you get a much better Chat system IMO.

Link to comment
Share on other sites

  • 0

How is the whmcs import module at this time. I have been working for years with whmcs , and I have a huge amount of data I cannot lost. 

 

Is there a full import ?

 

Depends on your modules, you can install a trial and use the import module without any crons to see if it works fine for you. In Blesta 3.3 a lot is improving for you guys to help you import over. Like price overrides, etc.

Link to comment
Share on other sites

Join the conversation

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

Guest
Answer this question...

×   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.

Loading...
×
×
  • Create New...