Skip to main content
All Collections
Checklist external migrations
Checklist external migrations

What should you pay attention to when executing an external migration of a Basecone administration?

Cees Houpt 🚀 avatar
Written by Cees Houpt 🚀
Updated over a week ago

Read this checklist before starting an external migration in Basecone:

  • External migrations are only possible for these bookkeeping systems: Exact Online (NL), Twinfield, Boekhoudgemak & Multivers, Xero, and Visma AccountView.
    You cannot migrate from Exact Online, for example, to Twinfield and the migration within the accounting package already has to be completed before starting the migration in Basecone.

  • The costs for migration are € 39,00 (exclusive of VAT) per administration, with a maximum total amount of € 300,- (exclusive of VAT) for the total migration. We charge these costs to the new Basecone environment.

  • If the administration code(s) do change, indicate this during the migration request in the new environment by selecting the new administration code from the list of available administrations. It is, therefore, necessary that the migration in the accounting system is finished.

  • If you don't have a Basecone environment yet, request an environment via the registration form. Enter all your details and subscribe to Basecone. Please know that you cannot migrate an administration to a free trial environment.
    After having subscribed, add the connection with the accounting system, but do not add the administrations. These are transferred via migration, later on.

  • Do not add the administration directly from the accounting system, otherwise, you will not be able to select the available administration during the migration. Basecone can only contain 1 unique combination administration code/administration name at a time.

  • It is not possible to complete the migration without the agreement of one of the administrators (Superusers) in the current Basecone office.

  • Do you use the authorization module in this administration? Then all documents must be rejected or authorized before the migration takes place. This also applies to documents selected in a (standard) workflow. All workflows per administration to be migrated must also be removed.

  • We transfer the documents, not the users. The users need to be recreated. Some users have their own built-up archives, such as an Authorizer or a Minimal Client user. Because the users are being recreated, these own built-up archives will be lost.

  • Note that the new administration codes can consist of a maximum of 10 characters, because this is the maximum of the local e-mail part of the administration e-mail address.

  • Make sure that you check whether the correct administration (s) have been selected during the migration assignment.

  • Make sure that if you are in the receiving (new) environment, you also check whether this concerns the correct administration(s).

  • It is not possible to migrate sub-companies, these are copies of existing administrations with a different e-mail address.

  • The administration is completely transferred, so including the payment agreement. If this is not desirable, you can have the payment agreement removed via our Support department.

Did this answer your question?