With the user role Super user you can migrate & receive one or more administrations, including their archives, in Basecone. Here are the most common questions and pitfalls:
I don't have a (new) Basecone environment yet, how do I get one?
If you do not yet have a Basecone environment, request one via the registration form. Fill in all the details and start a Basecone subscription. To be able to migrate you need a paid Basecone subscription. So immediately transfer the Trial to Premium.
I don't have a link with the accounting package in Basecone yet.
This link is required to perform a migration. Add this via Settings > Office > (tab) Accounting system and use the login details of the relevant accounting package.
Which users in Basecone can initiate a migration?
Only Super Users can initiate and/or receive a migration. Another user cannot start or receive migration. If you do not have this role, please contact the Super User from your environment.
Can I migrate an administration to another accounting package via Basecone? For example from Exact Online to Twinfield?
It is not possible in Basecone to transfer an administration from, for example, Exact Online to Twinfield. It is possible is to migrate the existing administration and keep it as an archive in Basecone. You will then create a new administration in the new accounting package and link it to your Basecone environment.
Starting the migration; make sure that the migration has been completed in the accounting package.
If the administration has not been migrated completely in the accounting package yet, you cannot receive it in Basecone.
Can I migrate multiple administrations at the same time?
Yes. You can select multiple administrations at the same time and have them transferred at the same time as well.
Will the unique email address in Basecone change after the migration?
Yes! The administration code may contain a maximum of 10 characters (numbers and/or letters) after the migration. Keep this in mind when applying for the migration.
How do I indicate the new administration code during the migration?
If the administration code changes, select the administration with the new administration code from the list that is displayed from the accounting package during the migration. Don't see the new code here yet? Then a migration must be performed in the accounting package first.
Are all documents and users transferred in the current administration?
All documents with or without tag and the archive are transferred. All documents to be authorized must therefore first be rejected or approved before the migration can take place. We do not migrate users. The users must be created again.
This means that some users have their own archive, such as an authorizer. Because the users are recreated, you 'lose' this own archive in the new environment.
Check the correct information (the check-list), remove existing workflows, and approve or reject all documents.
If the workflow still exists with associated Authorizers, Authorizers will continue to be considered active in Basecone. So remove the authorizers from the workflows and deselect the workflows. Set the authorization before and after booking to none/optional.
Do I have to adjust something in the workflow of the administration?
All workflows per administration to be migrated must be deleted. The documents that are selected in the (standard) workflows must also be rejected or approved first.
What happens to a payment agreement from an administration during a migration?
The administration is completely transferred, so including payment agreement. If this is not desirable, you can have the payment agreement removed via our support department.
I am not receiving the transfer code in my email.
If you have not received a transfer code by email, please check your spam box. If there is also no mail with code there, please contact the applicant of the migration.
Why can't I see the migrated administration after the migration?
You still have to give yourself and other users access to the administration(s). You can do this via Settings > Administrations > Actions (edit) > Users tab > Set access to Yes.
During a migration, we transfer the documents and not the users. Some users have their own built-up archive, because the users are created again, you have 'lost' this own built-up archive. The users must therefore be created again in the new environment.
It is not possible to migrate sub-administrations, these are copies of existing administrations, with a different e-mail address.
Agree, after approval you can no longer make changes.
Once e-mail addresses have been chosen, you can no longer change them. If you still want to change something, cancel the migration process and start it again.
A completed migration process cannot be rolled back. Only the new Super User of the administration decides on this. Keep the copy of migration in your email, as proof of migration.
Manage migration
Once the transfer code has expired, the migration process must be restarted (cancel first so it can be started again). The transfer code is valid for 15 days.