Skip to content

How do I migrate my data from Powergest?

The Powergest migration screen takes a ZIP with the Desktop ERP tables and imports them all in one go, in the right order, without having to prepare any template. It is the recommended route for moving a customer from Powergest to the ERP.

What do I need before I start?

A ZIP file with the .dbf tables of the Powergest company you want to move. The ZIP of the whole data folder will do: the programme takes the tables it recognises and ignores the rest. The limit is 200 MB.

In Powergest each year is a company; here each year is a financial year of the same company. The ZIP says which financial year: when you load it, the screen tells you which year it is from and which financial year the data goes into. If that financial year doesn’t exist, it is created when you migrate.

The data goes into the company you are working in. All the years of the same Powergest company go into it, each into its own financial year. Change company only to migrate a different company.

If you also want the item photos, you need one more thing: the BMP folder of the Powergest installation, compressed into a ZIP. The photos don’t go inside the data ZIP. This is explained in the next section, and it is worth reading it before migrating.

Go to Management › Powergest migration.

How do I do it?

  1. In 2 · Powergest ZIP file, select the ZIP. When it is loaded it is inspected without writing anything: the list of tables that will be imported appears, with their target and their number of rows.
  2. Above, in 1 · Target financial year (current company), read which year the ZIP is from and which financial year the data goes into: it is selected for you. If you want to try it first in a financial year for testing (adaptation period), create it there with Create new financial year and choose it. Choosing a financial year that isn’t the ZIP’s year asks you to confirm it with a box, because the documents would go into that financial year and the journal entries into their own year, and the company would be split.
  3. In Desktop ERP images, upload a ZIP with the BMP folder from Powergest if you want the item photos. It is optional; if you don’t provide anything, everything else is migrated the same.
  4. Read the warnings, if any appear. The ZIP tables not yet supported one says what is ignored. The one about another set of tables asks you to check something before continuing: it is explained further down.
  5. In 3 · Migrate, choose what you want to migrate: All or Records only (see the next question).
  6. Leave Update what was already imported ticked if you are going to repeat a migration, and click Migrate now.

The preview in step 2 doesn’t touch the database. You can load the ZIP to see what it brings and not migrate.

Can I migrate only the records, without the history?

Yes. In 3 · Migrate, under What do you want to migrate?, tick Records only. It is for those starting from scratch in the ERP who want their usual master data, but not the history.

Included: customers, suppliers, sales agents, items, item families, brands, the chart of accounts, payment methods, warehouses, currencies, cash accounts and banks, customer types, delivery routes, trades, carriers, delivery addresses, vehicles, customer price lists, item components, the catalogue and its images, the cash journal keys and the terminals.

Not included: quotes, orders, delivery notes and invoices; instalments, receipts, payments and advance payments; journal entries, VAT register and VAT returns; stock and batches. The chart of accounts does come in, because the customer and supplier records refer to their account.

When you change the option, the list of tables in step 2 and the expected time are updated. The question about how it calculates VAT disappears, because it only affects documents. Whatever is left out is named below the option and in the migration result.

The company settings are copied the same as in the full migration: code widths, series, desktop options. If later on you want the history, migrate the same ZIP with All: the records already migrated are recognised and aren’t duplicated.

The migration verification compares against the full ZIP. After a records-only migration, the document, open items and accounting checks come out with differences: that is to be expected.

How do I bring in the item photos?

The photos don’t travel inside the ZIP. In Powergest they are separate files stored in a separate folder, so you have to tell the migration where that folder is.

First load the tables ZIP. Until then it isn’t known which photos are needed, and the question about the images doesn’t appear. With the ZIP loaded, the screen says how many different photos it asks for, and there are three ways of giving them to it. The normal one is the first.

Choose the folder on this computer. Click Choose folder… and find the BMP folder of the Desktop ERP on your computer or on a network drive you can see. The browser goes through it on your computer and, when you click Migrate now, uploads only the photos that are needed, one by one. It doesn’t matter how big the folder is: from several gigabytes, usually a few megabytes are uploaded. Only in Chrome and Edge.

Upload a ZIP of images. Compress the whole BMP folder and upload it (500 MB at most). It is the way out for Firefox or Safari.

Enter a folder on the server. It only works if the photos are on the machine where the ERP runs. It is a path as seen from the server, not from your computer: a folder on your computer, such as E:\Fotos\BMP, doesn’t exist for it. If the server doesn’t find it, the screen says so in red and doesn’t let you migrate until you correct it or delete it.

In all three cases, the screen tells you straight away how many photos it has found of those that are needed. Check it before migrating.

The photos that are uploaded are kept on the server only while the migration lasts; afterwards they are deleted. What remains is the image already placed on each item’s record.

The photos are saved in the item gallery, the same one you see when you open its record. Through that same folder come the images of the catalogue categories, which go to each category’s record.

What happens if I don’t provide the images?

Everything else is migrated the same, and the photos don’t come in. It is optional on purpose: it doesn’t block the migration or leave it half done.

In the Migration result an images row appears saying that they weren’t imported, and why. They are never left out silently.

If you realise afterwards, there is nothing to redo: migrate again, this time giving the folder. Migrating again doesn’t duplicate the photos that are already there, or the records already migrated.

Why don’t all the photos appear?

Because the Desktop ERP stores, with each item, the path from which the photo was dragged the day it was set up. Those paths usually point to disks on other computers that no longer exist: C:\ifswin, D:\FOTOS CATALOGO, G:\....

Those paths are no use. What is useful is that Powergest copied each photo to its BMP folder with the same file name. That is why the migration keeps only the name and looks for it among the images you have given it, whether they come from the ZIP or from the folder.

Measured on a real installation: 248 of 286 photos are found, 87 %. The missing ones are photos the customer no longer has in that folder —they were deleted, or never got copied—. There is no way to recover them from the migration: they are uploaded again by hand on the item’s record.

In that same installation 232 images came in: 201 for items and 31 for catalogue categories.

Category images are saved on their category’s record, just as item images are saved in the item gallery.

How do I read the reasons for the images that don’t come in?

In the Migration result, the images row has its details table below it, with the same layout as the others: Row, Key and Reason. Each photo that didn’t come in says why.

ReasonWhat it meansWhat to do
The file wasn’t foundThe photo’s name isn’t among the images you have givenCheck that it is the right BMP folder. If it is, that photo no longer exists: upload it by hand
The row has no image pathThat item never had a photo in PowergestNothing. It isn’t a fault
The image doesn’t belong to any migrated recordThe photo belongs to an item family, which has no galleryNothing. It isn’t a fault

Up to 20 are listed, as in the rest of the tables. If there are more, it says below how many were left unlisted.

Is my catalogue migrated?

Yes. The whole Desktop ERP catalogue comes in: the categories, the item families that were placed in the catalogue, the products placed inside each one, the texts of each record with their translations and the category images.

The order is kept: the categories stay as they were and the products take, inside each category, the place they had.

Measured on a real installation: 38 categories —35 at the first level and 3 hanging from another— and 487 products placed.

If your catalogue is made of item families, it comes in the same way. There are installations whose catalogue isn’t categories but item families directly: each one comes in as a category with all the items of that family inside. In one real installation there are two —‘Fabrica’ with 220 items and ‘BIZCOCHO’ with 86—, and that is their whole catalogue.

The items of a family aren’t copied one by one: the catalogue looks at which family each item belongs to, just as Powergest does. That is why, if you later move an item to another family, the catalogue follows it.

Categories are first created with a provisional name and the next step, the texts one, gives them their real name. If the ZIP didn’t bring the texts, the catalogue is left with the right structure and with hard-to-read names: it is corrected by migrating again with the full file.

Are the catalogue texts and translations kept?

Yes. From each catalogue record the title, the description —with its formatting— and the search engine data come in: meta title, meta description and keywords.

Translations aren’t lost. One record is saved per object and per language, so an item with text in Spanish and in Basque arrives with both. Measured on a real installation: 392 texts imported out of 507, split into 293 in Spanish and 95 in Basque.

It is the part of the migration that saves the most work, because a translated shop-window text is the most expensive thing to redo by hand.

Why are there texts that don’t come in?

Because they belong to records that no longer exist in the Desktop ERP. Over time, categories and items are deleted, but their texts stay in the file with nobody to belong to.

There is nothing to fix: they are leftovers, not lost data. In the installation measured there were 115 of 507.

Even so, they aren’t discarded silently. Each one appears in the Migration result, in the texts details table, with its Row, its Key and the reason: it says that the text doesn’t correspond to any imported category or item.

If, when reading the details, you recognise a category that should exist, the cause is usually something else: that the ZIP didn’t bring the catalogue tree table, or that it was migrated before the items. Migrate everything again and it is sorted out.

What do I do if it warns me that the ZIP brings another set of tables?

That warning appears before migrating, in the preview, and says something like: ‘The ZIP brings another set of tables that will NOT be imported: ALMA27 (alongside ALMA)’.

It means that inside the ZIP there are two tables of the same type: the normal one and another with the same name plus a suffix. It happens with any of them: ALMA and ALMA27, FAMILIA and FAMILIA27, PROV and PROV_2, IMAGEN and IMAGEN2. Only the first one is imported, the one without a suffix.

That suffix can be another company, another financial year or a backup. The programme doesn’t decide for you, because there is no way of knowing from the outside: it shows it to you so that you can check.

What to do:

  1. Open the Desktop ERP and see which of the two has the right data. If you are unsure, compare the number of records in each one.
  2. If the right data is in the table without a suffix, carry on with the migration: it is the one that comes in.
  3. If the right data is in the table with a suffix, don’t migrate yet. Prepare a ZIP in which that table has the name of the normal one, or move it separately with the import wizard.

It is worth stopping here. In a real case, ALMA had 960 items and ALMA27 nine thousand: migrating without looking would have left almost the whole catalogue out, and the migration result would have come out correct, because the 960 records that went in went in correctly.

Which tables are migrated today?

The one-click migration moves the master data and the catalogue, in this order, which is the order of their dependencies:

Powergest tableWhat is created in the ERP
MONEDACurrencies: name, symbol, decimals and exchange rate of each currency
TERCERTreasury accounts: your cash accounts, your banks and your POS
AGENTESales agents
PROVSuppliers
CLIENCustomers
TERCER (again)Customers and suppliers that only existed in the accounts, without a record
FAMILIAItem families, with their code and their name
ALMAItems, with their item family and their sales and purchase prices
ALMA (again)Sizes and colours: each size from the desktop, as a combination of its item
GRUPOSCatalogue: categories, products placed inside them and their order
WEBGRPCatalogue texts with their translations, and the name of each category
IMAGENItem and category images. Only if you have provided the images (ZIP or folder)
COMERCCRM contacts (the telemarketing sales records)
AVISOSCRM activities: the calls and appointments for each record or customer

For items, the publish in the store flag is also kept, and the item family keeps the code it had in the Desktop ERP.

The three catalogue tables go after the items and in that order among themselves. First the tree, which creates the categories and places the products inside them. Then the texts, which give each category its real name. And finally the images, which need the item or the category they hang from to exist already.

Item families go before items on purpose. In Powergest the item only stores the code of its family; the name is in another table. By moving that table first, the family is created with its real name —BIZ is called BIZCOCHO, not ‘BIZ’— and the item finds it already made. If the ZIP doesn’t bring the families table, families are still created from the item code, but then they stay named after their code.

Currencies go first, because the customer and supplier records and the documents store the code of their currency and it is best for that currency’s record to exist already.

There is a peculiarity with them: in Powergest the currencies table isn’t in the company folder, but in the root folder of the installation, so very often it doesn’t come inside the ZIP. When it is missing, it appears in the list of tables that didn’t arrive and nothing else happens: the rest of the migration carries on the same and the programme works with the currencies it brings from the factory —euro as home currency, plus the common ones—. If you need yours, copy the MONEDA.DBF file from the Powergest root folder into the ZIP, or move it separately with the import wizard.

And another, which is worth knowing beforehand: the home currency doesn’t change when migrating. If in the Desktop ERP you kept your accounts in another currency, that currency comes in as one more and you will see a warning saying so. Changing which is the home currency is done by hand on the currencies record, because it affects all the amounts already saved.

For customers and suppliers, almost the whole record comes in: identity and address (with its second line), contact (both phones, both mobiles, fax, website, contact person), remarks, delivery route, number of copies, financial terms (payment days, discount, risk, IRPF withholding, ledger account, currency, scheme) and bank details. If the Powergest record had up to three payment days, they come in together in the payment days box (‘5 and 25’). The field-by-field details are in what can be imported.

For customers, their points also come in, in the three boxes and with the same calculations as the Desktop ERP: Sales points (the initial ones plus those from their sales), Points used (those redeemed and spent) and Available points (the difference, never below zero). Their billing address also comes in, which appears in the billing block of the Addresses tab, and their SEPA mandate —the reference, the signature date and whether they were already being charged—, which is what allows them to go into direct debit batches. A billing address without a street comes in anyway, with whatever it brings (name, phone, other details) and the street blank; it is only left out if it is empty. From the chart of accounts, the previous code of each account also comes in.

For a business partner, their payment method and their sales agent also come in, already linked to the records the migration itself creates. What doesn’t come in is their price list.

For customers, their delivery addresses also come in: the shops, warehouses and branches they are supplied at, each with its name, town / city, postcode, province, phone and email. They appear in the Addresses tab of the record. A branch without a street but with some detail —its name, a phone, a code in other details— comes in with the street blank. The only ones left out are those that in the Desktop ERP were empty —opened and never filled in—, and the migration says so: they are ‘Not imported (expected)’, not a fault.

If the company had Verifactu enabled in the Desktop ERP, the migration leaves it the same: enabled or not, the date from which it sends and whether it prints the QR. It can be changed on the Configure the service screen (**Veri*Factu / TicketBAI** family of the tax panel).

The submissions the Desktop ERP made to the Tax Agency also come in, as each invoice’s history. If Verifactu wasn’t enabled, or the invoice is earlier than the date from which it sends, they are only kept for reference: they aren’t sent again. That part is quick even if there are many years of submissions.

Do invoices and delivery notes come in?

Yes, and with their usual number and series. It is the part that matters most when recognising the history: the invoice you have printed, declared and collected has the same name in the new programme, so you find it by searching where you used to search before.

All seven types come in: sales quotes, orders, delivery notes and invoices, and purchase orders, goods receipts and purchase invoices. Each document arrives with its customer or supplier, its lines in the same order you see them in the Desktop ERP (including the ones you inserted between two others), its prices, discounts and taxes, and also with what the Desktop ERP stored and until now was lost: the payment method, the sales agent, the warehouse, the ledger account, the deferred amount, the cost, the service date, the packages and the commission. For each line, its cost, its commission, the reference with which that item appears on the supplier’s or customer’s paperwork, and the boxes are kept.

VAT comes in even if your Desktop ERP kept it in the header. Powergest allows both ways —one rate per line or a single rate for the whole document— and each installation uses its own. If yours keeps it in the header, its documents arrive with their VAT: before, they came in at zero and the totals didn’t add up.

If you mix exempt lines: an exempt line comes in at 0 % when the Desktop ERP invoice declares a tax base at 0 %. If it doesn’t declare one, the line takes the document’s rate.

IRPF withholding comes in the same way. If your invoices carried withholding (a rental, a professional), they arrive with it and with the total that is actually paid, as in the Desktop ERP.

Quotes and orders that were already invoiced stay closed. An order that the Desktop ERP considered invoiced, delivered or finished comes in as Invoiced: it doesn’t appear among what is pending and isn’t offered for conversion again. Those that were still pending come in as pending.

And whatever had already been delivered on each line stays delivered. An order for 24 units with 19 delivered comes in with 19 delivered and 5 pending, not with 24: when you make its delivery note, the ERP suggests only what is missing. If in Powergest more than was ordered had been delivered on a line, that line comes in fully delivered and the migration report says so.

Invoices for delivery notes come in with the lines of their delivery notes. In the Desktop ERP, an invoice made from delivery notes (key 04 in sales, 03 in purchases) doesn’t store lines of its own: its content is the delivery notes it invoices. When migrating, the invoice comes in with the lines of those delivery notes, in their order and with their amount, and each line is linked to the line of the delivery note it comes from. The delivery notes come in as Invoiced: they don’t appear as pending invoicing. The invoice VAT is the sum of the VAT of each delivery note, as in the Desktop ERP: it isn’t recalculated on the total tax base, which could give a difference of one cent.

Migrated documents are history: they are left out of sending to the Tax Agency, because their declaration was made at the time by the Desktop ERP and sending it again would mean declaring it twice.

If a document brings a payment method, sales agent or warehouse code that doesn’t exist in the new programme, the document comes in anyway and that field is left blank. That is better than losing the whole invoice over a stray code.

What happens to the invoices I voided in the Desktop ERP?

They come in as replaced: you see them with their number, but they don’t add to sales, they have no journal entry and they don’t generate receipts. It is the same as what the desktop did when voiding them.

Does my company work with IGIC?

If the rates in your Desktop ERP are the IGIC ones (7 %, 3 %…), the company is set to IGIC when migrating, with the account for each rate as you had it. It is decided only by the rates. You can change it in Tax › VAT definition.

Are €0 invoices posted?

It depends on your company. In Settings › Transfer there is the Post €0 invoices box. When migrating it is set as you had it in the Desktop ERP: if they weren’t posted there, it is left unticked.

Can I correct a company I migrated with an earlier version?

Yes, without migrating again. On the migration screen, in Verify the migration:

  1. Click See what would be corrected. It doesn’t change anything: it says which documents would be corrected and why.
  2. If you agree, click Correct.
  3. Click Verify the migration again to see the result.

Only technical support can click Correct. Anyone can click See what would be corrected, because it doesn’t change anything.

It corrects voided invoices that came in as live, purchases with an exempt part that came in with VAT on all their lines and the journal entries for €0 invoices that the desktop didn’t post.

It needs the same ZIP you imported and to have the financial year you migrated into open. You can run it several times: whatever has already been corrected isn’t touched.

Can I migrate several years of the Desktop ERP into the same company?

Yes. In the Desktop ERP each year is a separate company; here each year is a financial year of the same company, and the ZIP says which year it is. Years can be brought in in any order:

Each journal entry is recognised by its year and its number: entry 1 of one year and entry 1 of the next are two different entries, and both come in.

What does the migration do when it adds an earlier year?

What was already there wins. The migration:

An order, a delivery note or an invoice still pending when the year closed appears in both ZIPs. It stays as the next year left it (delivered, invoiced, collected…), which is how it really is, and it is not duplicated.

The same goes for its bank bills: the one the next year brought in is not touched. What was collected from it in the added year comes in depending on how the next year brought it in:

To bring an added year in again, undo its closing first: Accounting > Operations > Undo closing. While the financial year is closed, the migration doesn’t start and says so.

When each year is checked, its open items are compared with that year’s: receipts brought in by another year don’t count as differences, and a receipt collected in a later year is compared as it stood when its own year closed. Today’s open items (what is still pending) are compared with the accounts when the last year is checked.

If a receipt is collected in one year and pending in the next, “Update period” was not run in the Desktop ERP, the process that removes from the new year what was collected in the previous one. The migration does what that process would have done: the receipt stays collected, with its remittance and its journal entry, and no other pending receipt is created. The migration warns about each one and the next year’s check counts it as explained. The next year’s opening entry is not touched: it is redone once the previous year is right.

Can I bring in only the last few years?

Yes. Before migrating, you choose ‘Import data from year’. By default it is last year; you can also choose ‘All history’. It applies to both the CRM and the ERP.

Whatever is earlier than that year stays in the Desktop ERP: quotes, orders, delivery notes, service reports and production orders.

What always comes in, whatever year it is from:

A document without a date also comes in: there is no way of knowing when it is from.

The migration verification knows which year you chose. Documents that were left out on purpose show as explained, not as lost.

Does the telemarketing come in (sales records and alerts)?

Yes, into the CRM. If your ZIP brings the COMERC and AVISOS tables:

If another CRM contact already had a record’s code, that other one moves to the next free code, so that every record keeps the one you know from the Desktop ERP. If that other one was created by you, the migration result says so.

Can I bring only the photos into a company already migrated?

Yes. Load the same tables ZIP and, in 3 · Migrate, choose to migrate by areas and tick only Images. Then give it the photos as in any migration (the normal way, Choose the folder on this computer).

The photos of the items and of the catalogue categories come in, and nothing else: items, families and stock are not touched. Each photo goes to the item you already migrated, and the one the item already has is not uploaded again, so you can repeat it as many times as needed.

Photos of an item that wasn’t migrated don’t come in: the result says so for each one.

Can I bring only the telemarketing into a company already migrated?

Yes. In 3 · Migrate, choose to migrate by areas and tick only Telemarketing. The sales records and their alerts come in, and nothing else: your customers and your items are not touched.

It is for completing the CRM of a company you migrated with an earlier version:

Whatever you have changed in the CRM since then (status, owner, phones, people) stays as it is.

When you migrate the master data, the telemarketing comes in too: you don’t need to tick both areas.

The two Desktop ERP alert reports are in CRM › Reports › Reports: the one for a day’s alerts and the one for active alerts.

If you undo the migration, the contacts it created are also deleted.

Do my cash accounts and banks come in?

Yes, with their ledger account, their IBAN and their BIC. In Powergest cash accounts and banks don’t have their own file: they live mixed in with customers and the only thing that tells them apart is their ledger account. The migration recognises them by that —accounts starting with 570 are cash, those with 572 banks and those with 440 POS— and creates each one as a treasury account.

It is the step that makes everything else in treasury possible: without your banks set up, the open items can’t say which one each bill was collected through and the matching wouldn’t balance.

Each account is created with its accounting code as its code. It is the same one you look it up by in the chart of accounts and match with, so you recognise it just as before.

An account starting with 440 that brings a Tax ID or an address doesn’t come in. That group is used both for cards and for debtors, and a record with tax details is almost always a debtor. The migration result says which one it is: if it really was one of your accounts, you set it up by hand.

In the result you will see that this table reads thousands of rows and creates a few. That is correct: the table is mostly the customers file. In a real installation, 18 accounts from 3.197 rows.

And what customers owe me?

It comes in, and linked to its invoice. Each instalment arrives with its date, its payment method, its sales agent, its bill number, its tax base and the account it was collected through, so the open items can be put in batches and matched from day one.

Whatever was already collected comes in as collected. A bill the customer paid at the time doesn’t appear as pending again, and one they half paid comes in for what is missing, which is what they still owe. It is the difference between open items that match the bank statements and a made-up list of debt.

The receipt account is the only open-items detail that stops the row if it isn’t found. If you see bills that fail saying an account isn’t there, what is missing from the ZIP is the chart of accounts or the business partners file, which is where your banks come from. Coming in without that account would leave the matching unbalanced without anyone noticing until the reconciliation, so the migration prefers to say so.

And the advance payments customers have given me?

They come in as advance payments, not as the customer’s debt. Each one arrives with its original amount, with its treasury movement and with its journal entry, just as if you had recorded it here. And whatever has already been used of it also comes in: the advance payment appears with the balance it really has left.

This matters because in the Desktop ERP advance payments and bills live in the same place. Without telling them apart, the money a customer gave you on account would appear on their record as a debt of theirs.

In the accounts, on the other hand, they are kept as in the Desktop ERP: the migration switches on in the company the Advance payments and vouchers in the customer’s or supplier’s account box, so the advance payment goes to the customer’s account (their 430) and not to a separate advance payments account. That way each customer’s general ledger can be compared as is with the usual one. The migration report says so in ‘Target company rules’, and the box can be switched off in Settings › Transfer (it affects what is recorded afterwards). It is only switched on if the company is empty: on a company with data, whatever it had is respected.

What doesn’t come in is the return of a bill. A bill returned in Powergest arrives as one more instalment.

That is why an imported invoice doesn’t make up its instalments: its instalments are the ones it had in the Desktop ERP. If the ERP recalculated them from the payment method, theoretical due dates would come out —without bill number, without what has already been collected and without the deferrals that were agreed over the phone—, and the customer would see their debt twice.

Instalments whose invoice isn’t in the ZIP come in anyway, as the business partner’s carried-forward balance.

A partly collected bill (in Powergest, one for 1.000 € of which 800 have been collected on account) comes in as two: the pending bill for what is missing (200 €) and, hanging from it, another one already collected for what was paid (800 €). That way you can see both what is owed and what has already been collected.

And the accounts? Won’t everything be there twice?

No. Each invoice, each receipt or payment and each advance payment imported carries its journal entry, created at the same time as them, just as if you had made them here. A bill that had been paid comes in with its real receipt or its payment: the date it was paid, the bank or the cash account and the expenses.

And each receipt or payment comes in as the operation it was, not bill by bill. If in Powergest you collected three bills from three customers in a single deposit, or an invoice with two advance payments and the rest in cash, here it is a single operation, with a single movement in the bank and a single journal entry: the same as you will see on your bank statement. The operation description carries the number it had there (‘Desktop ERP receipt C60012’).

The Desktop ERP journal comes in afterwards and does two things:

The customer’s or supplier’s account, the VAT and the amounts aren’t touched: they belong to the invoice.

Journal entries keep the accounting document number they had in Powergest. The ones the ERP creates when importing are numbered after the last one.

If an invoice doesn’t get to come in, its Desktop ERP journal entry is imported. That way that accounting isn’t lost.

A journal entry that doesn’t balance in the Desktop ERP (debit and credit don’t add up to the same, something that can be saved there) comes in anyway, with one more line to account 555 (items pending application) for the difference and the description ‘Desktop ERP imbalance’. That way each account has its real balance and the imbalance is visible in a single place, to be adjusted. It happens above all with the opening: without it, all accounts would start the year at zero. The migration verification counts it as a Desktop ERP defect.

Whatever couldn’t be corrected can be seen in the migration result, on the accounting line, with the reason. For example: ‘the line for account 47200002 doesn’t change to 47200001: the business partner’s account and the tax accounts belong to the invoice’.

And the warehouse stock?

It comes in, with the stock of each item in each warehouse and its minimum warning level. What is brought in is the snapshot of the warehouse as it is on the day of the migration, not the history of goods in and out: the documents that are imported don’t move stock, so the stock is whatever the Desktop ERP brings and nothing throws it out along the way.

An item with negative stock comes in negative. It isn’t a migration error: it is what there was in the Desktop ERP, and it almost always means that something was sold whose purchase never got recorded. Setting it to zero would hide the problem and would also leave the stock not matching Powergest’s. It is adjusted with a stock count, which is what needed doing anyway.

If you migrate again, the stock is set to the value in the ZIP, it isn’t added. Repeating the migration doesn’t inflate the warehouse.

Along with the stock also come the desktop record details: initial stock, total purchases, total sales, other movements and what is pending receipt, delivery and transfer. From that moment on, whatever you sell or buy in this programme is added to those figures.

What is pending delivery or receipt is a snapshot from the day of the migration. If you deliver here an order that came from the desktop, that quantity doesn’t go down by itself: correct it on the item’s record.

Every item comes in with its warehouse. If the warehouse on its record isn’t among the migrated ones, it takes the company’s default warehouse. Items come in active; the Publish in the online store box is separate and copies the desktop’s.

What doesn’t come in with this screen yet are customer price lists, batches and the accounts. It appears in the unsupported tables warning so that there is a record that it has been ignored; it is never discarded silently. That data can be moved one by one with the import wizard, preparing one template per table.

What happens with an item that is in several warehouses?

It comes in only once, with all its records read. In the Desktop ERP, an item that exists in two warehouses is stored twice, once per warehouse. Here that doesn’t create two items: the second record with the same code updates the item that is already there.

That is why the result may show more rows read than items created, and that is correct. In a real case, the file brought 1.011 records and 960 items came out: the remaining 51 were repetitions from the second warehouse.

An important nuance: this doesn’t add up the stock of the two warehouses. Each record carries the stock of its warehouse, and that is how it comes in: separated by warehouse, not accumulated on the item.

Do sizes and colours come in?

Yes. In the Desktop ERP each size is one more record, with its own code: the ‘Juego de Sábana Iris’ is 0000003 and its size 90 is 000000301. Here they come in like this:

With that, when selling you can already use the size grid, and when scanning the barcode of a size the line comes out with its size set. Typing the size code (000000301) does the same.

Documents that come from the desktop (invoices, delivery notes, orders…) also carry the size on each line.

Items with size and colour (two levels) come in the same way, with both on each combination. In the desktop there was also a record for each size without colour, which only added up the stock. Those don’t come in: here they aren’t needed.

It can happen that a size has no name in its desktop set. Then it is taken from the record’s description: if the item is ‘Sábana Iris’ and the size ‘Sábana Iris 135’, the size is called ‘135’. The same if two sizes of an item had the same name: each one keeps its own.

And what if the Desktop ERP uses a warehouse it hasn’t set up?

It is created, with the same code it uses.

It happens more than you might think: Powergest’s warehouse file declares only 001, but then there are items with stock in 002. The warehouse really exists —it has goods inside—; what is missing is its record.

Before, that stock was left out with a warning. Now it comes in, because losing real stock is worse than having one warehouse record too many. The same applies to the lines of a document: a line always ends up in a warehouse, and if the one it refers to isn’t set up, it is created instead of sending the line to another — which was the silent way of ending up with stock spread where it doesn’t belong.

After migrating, review the warehouse master and give them the right names: they come in with the code as their name, because that is the only thing the Desktop ERP says about them.

What happens when I click Migrate now?

The tables are imported one after another, in the order of the list. Each table is independent: if one fails entirely, the failure is recorded and the migration carries on with the next ones.

When it finishes, the Migration result appears, with one row per table: created, updated, incomplete, with errors, skipped and status. Below that, the supported tables that weren’t in the ZIP and those that have been ignored.

The last three columns say different things, and it is best not to mix them up:

ColumnWhat it meansDo I need to do anything?
IncompleteThe record is there, and it is missing a field that clashed with a rule of the programmeReview them: what is missing can be completed by hand
With errorsThe row didn’t come in and something is wrongYes: look at the reason and correct it
SkippedThe row didn’t come in for an expected reason (its owner is in a table that isn’t imported)No

The records are really created and there is no undo. That is why the first pass is best done on a financial year marked as for testing.

An empty table isn’t an error: it is reported with 0 rows and the next one is started.

How long will it take?

The screen tells you before you click, below Migrate now: ‘Expected time: about 13 min for 36.018 records’. As a guide, a company with about 36.000 records takes about 4 minutes.

The estimate comes from how long the previous migrations in your programme took, table by table: what each customer record, each invoice line, each journal line… costs, multiplied by the number your ZIP brings. That is why a company with twice the data comes out at twice the time, and it gets more accurate by itself with each migration that is done. The first time, before there is any measurement, it uses some starting values and says so.

When it finishes, the message at the top says which migration of the company it is (no. 1, no. 2…) and how long it has taken in total, alongside the estimate, so you can see how far off it was. If it was interrupted and continued later, the total adds up what it worked each time —not the time it was stopped— and says in how many attempts. The upload of the photos, if there are any, is separate and comes first.

How do I know whether the migration was started and how it ended?

A message at the very top of the screen tells you:

Can I close the page while it is migrating?

Yes. The migration runs on the server, not in your browser: you can close the page, the browser or the remote desktop session, and it carries on. Go back to Management › Powergest migration whenever you like: the message at the top tells you which table it is on or, if it has already finished, how it ended, with the full result.

There is one exception: if you choose the photos from a folder on your computer, they are uploaded from your browser before starting. While the message says it is uploading the images, don’t close the page. As soon as the migration starts, you can.

In a company there can only be one migration running at a time. If someone clicks Migrate now while another is running, the programme warns them and doesn’t start anything.

And on the whole server, one migration at a time: it is what needs the most memory. If another company is migrating when you click, yours waits its turn —the message says ‘Waiting its turn’— and starts by itself as soon as the other one finishes. There is no need to click again.

Can I leave the migration for the night?

Yes. A large migration keeps the server busy for several hours. Tick Start later, at this time next to the button; it suggests 22:00 today, or tomorrow’s if that has already passed, and you can change it. The button changes to Schedule the migration: the ZIP is uploaded at that moment and the migration starts by itself at that time, even if you close the page. The message at the top says when it is scheduled for. If you change your mind, cancel it in System › Background jobs.

If you schedule several, they go one after another: only one migration runs on the server at a time.

If the migration is interrupted (for example, because the programme was updated while it was running), it carries on by itself when the server comes back, from where it left off: the tables it had already finished aren’t repeated, and the one that was half done starts again without duplicating what already came in. In documents, which go in batches, only the batch that was cut off is repeated. If it doesn’t carry on by itself, it is resumed from System › Background jobs, and this message again says which table it is on.

Why does a row fail? Where can I see it?

In the Migration result, each table that has had problems has a details table below it with three columns: Row, Key and Reason. There you have the exact row of the Powergest file, the code of the record that didn’t come in and the reason, in the same words with which the programme would have rejected it if you typed it by hand.

Up to 20 rows are listed. If there were more, it says below how many were left unlisted. Twenty examples are almost always enough, because failures tend to repeat: if all twenty say the same thing, the remaining four hundred say the same thing.

What to do with that:

When what fails is the whole table, the message says so plainly: no row was imported from that table, and below it shows which column it expected and didn’t find in the file. There are no failed rows to list there, because none was even attempted.

What are ‘incomplete’ records?

They are records that are in the new programme, but are missing a piece of data because that data clashed with an ERP rule. They aren’t an error: coming in without one field is much better than losing the whole record with its name, its address, its banking details and all its history.

The result counts them in their own column, Incomplete, and below it lists which ones they are and what they are missing. It is the list you need to review after migrating; with the rest there is nothing to do.

It almost always comes from the same thing: a company with several shops has in the Desktop ERP one record per point of sale, all with the same CIF and often with the same ledger account.

What do I do if it asks me about records with a repeated Tax ID?

It only appears if your ZIP brings them, and it tells you how many. It is normal if you have several shops of the same company —one record per shop, all with the same CIF— or if a company is both a customer and a supplier of yours.

You can choose between two things:

If you leave the recommended option you don’t have to do anything else: your forms will come out as they used to.

For the records you set up afterwards, by hand, what you had in the Desktop ERP under ‘Check repeated Tax ID when adding’ applies: if it warned you there and let you save, it does here too, and the migration ticks Allow the same Tax ID on several records in Settings → Sales and documents → Codes. If it didn’t allow it there, it doesn’t here either. You can change it whenever you like on that same screen.

Does the migration change anything in my company’s settings?

It can, and it tells you at the very top of the result, in a separate message, because it is the only thing that stays in place when the migration finishes.

There are three cases.

The first: if the Desktop ERP chart of accounts uses account codes with letters (4300135E, 4300FS00), the migration enables in your company the option to allow account codes with letters. Without it, those accounts are rejected one by one and with each one the record of the customer that uses it is lost.

It is only enabled if the file really brings codes like that; with a normal chart of accounts nothing is touched. It stays enabled after migrating and can be switched off again in the Accounting settings.

The second is the series of your documents. If in Powergest you numbered with your own series (for example C6), the migration leaves it as the company’s default series: new invoices, delivery notes, orders and quotes follow that series and its numbering, instead of the ‘A’ with which a new company starts. It is done even if your company already had another one chosen: the result tells you which one there was. The documents you already had keep theirs. It is changed whenever you like in Document series.

The price list price of customers and suppliers is also copied. If in the desktop they didn’t have one set, they come in with Price 1, which is what the desktop shows and applies in that case.

The series also keeps the shape of the number: the series goes in front and the number behind, with the same digits as in Powergest. If your last invoice was C60163, the next one you make here is C60164.

POS receipts are numbered as in the Desktop ERP: if they had their own series there, that one; if not, they follow the invoice series (receipt C60226 comes after invoice C60225). In POS settings you will see it as the Use the invoice series box.

The third is the code width, which is always made equal to the Desktop ERP’s. It is explained below.

Are the options I had in the Desktop ERP copied?

Yes. The migration reads the Desktop ERP options screen and leaves your company the same in:

The Desktop ERP’s settings win. Each option is copied even if your company already had data and even if you had changed one: that way both applications work the same while they run side by side. The migration result says what has changed on each screen and what value there was before, in case you want to set it back. Whatever you had already saved isn’t touched: the options decide how new things are done.

The code lengths (sub-accounts, customers, suppliers, sales agents, items and payment methods) are also made equal to the Desktop ERP’s, but in a different way: before importing, the codes your company already had are regenerated to the new length. This is explained below.

The two IRPF accounts are copied, each to its own: the one for withholdings made on your sales (473) and the one for withholdings you make on your purchases (4751, the one settled in Form 111). If you had changed either of them by hand in this ERP, the migration sets it as in the Desktop ERP.

Two things aren’t copied, and the result tells you:

And two are copied in a different form, because here they mean something else:

What happens if the codes ‘don’t match’?

Your company is set to the Desktop ERP’s code format, and the codes it already had are regenerated to that format before importing anything.

In the Desktop ERP a sub-account can have nine digits (430000002) and your ERP company be set to eight (43000002). If only the length were changed, the accounts you already had would keep the old format: they wouldn’t be found when typed and the same account would be duplicated on the first journal line. If it weren’t changed, the desktop ones wouldn’t fit. The same applies to customers, suppliers, sales agents, items and payment methods.

That is why, when the ZIP is loaded, the screen shows a table with what is going to happen:

ColumnWhat it says
LengthYour company’s and the Desktop ERP’s (8 → 9). free means no padding
ChangingHow many of your company’s codes are rewritten
UnchangedThose the length doesn’t affect (with letters, grouping levels)
ReferencesWhere that code was written and is also corrected: the account on the customer record, the item’s, the default accounts…
ExampleA code before and after (43000002 → 430000002)

If there are codes to regenerate, tick Regenerate this company’s codes before importing. Without that box you can’t migrate. If the company has no affected records, the length is adjusted by itself.

Journal lines, balances and documents don’t move: they are linked to the record, not to its code.

The customer width also applies to suppliers and sales agents, as in the Desktop ERP, as long as their codes are the same length.

And what if the table says ‘It can’t be migrated like this’?

There are two records in your company that would end up with the same code, or a sub-account that doesn’t fit in the new length (when shortening it, only zeros can be removed). The migration doesn’t write anything. The table names the codes: correct them on their record and load the ZIP again.

A code that was already wrong (a sub-account of another length, a customer saved without its zeros) and that when regenerated would clash with another doesn’t stop the migration: it stays as it is and the table warns you so that you review it by hand. It is usually a repeated account; the chart of accounts review in Accounting › Accounts helps you decide which one to keep.

And what if the message says the codes ‘aren’t padded’?

Then that code is left unpadded in your company, and it is migrated as it is.

The Desktop ERP can pad codes with zeros up to a fixed length, or not. When it doesn’t, the number the settings declare is a maximum, not a format: item codes can be three characters long or ten, and there can be ones like GES, 1009 or 1011A. This ERP pads with zeros the codes that start with a number, so with its factory width 1009 would come in as 001009. That is why the migration sets that code to 0 digits (no padding): it is saved and searched exactly as it is. In the lengths table you will see it as free (6 → free): the codes you already had don’t change, only new ones stop being padded.

The desktop settings maximum is saved separately, in Maximum item code length. If an item in the ZIP is longer than that maximum, the longest item’s length is saved, so that they all come in.

The programme tells them apart by looking at the actual codes the ZIP brings, not only at what the settings say, because both things coexist in the same installation: it is normal for customers to be padded to a fixed width and items not to be.

Can I repeat the migration without duplicating anything?

Yes, and it is the intended use: you migrate a first time so the customer can rehearse, carry on working in Powergest for a few days and migrate again before the real go-live.

The programme remembers which ERP record corresponds to each Powergest code, so when repeating:

In neither case is a record duplicated. Whatever you have created by hand in the ERP between one migration and the next is respected: the migration doesn’t delete anything.

The same happens with the catalogue, and it is worth saying because it is where it is most noticeable: neither the categories, nor the products placed, nor the texts, nor the images are duplicated. Migrating again updates what is already there and adds what is missing.

How do I repeat a migration that went wrong?

Migrating again on top doesn’t correct it: whatever already came in is recognised and left as it is. To really repeat it, first clear out what the previous migration brought with Clear out the imported data and start from scratch, on the same screen. The programme asks you to confirm it, because it can’t be undone. Only technical support can clear it out: if one of your migrations has gone wrong, let them know.

That is why, when you load a ZIP into a company that already has a migration in it, the screen warns you before migrating, with the date of that migration and saying whether the ZIP is the same one or another. If it is another —a more recent copy from the Desktop ERP— and you want the company to end up like that ZIP, clear it out first. If you migrate on top anyway, the result message reminds you.

What is deleted, only in the company you have open and in all its financial years:

What is kept:

If something prevents the clear-out, nothing is deleted: either everything is cleared or the company stays as it was, and the message says why.

How do I check that what was migrated is what was there?

With Verify the migration, on the same screen, below the result. It compares the open company with the Desktop ERP ZIP and doesn’t change anything, so you can click it as many times as you need, even days after migrating.

  1. At the top, choose the same ZIP you imported. If Powergest has carried on being used afterwards, its data is already different, and the comparison would come out full of differences that aren’t real. If you choose another ZIP, the report warns you in the header. If you don’t choose any, the one from the last migration is used, which is kept for a few days on the server: there is no need to upload it again.
  2. Click Verify the migration. With a large company it takes a few seconds.
  3. Read the result of each check and, if you want to keep it, Download the report (CSV), which opens with a spreadsheet.

What is checked:

CheckWhat it looks at
A · The Desktop ERP balances with itselfThat Powergest itself is correct before comparing: its balances, its journal and its open items
B · The ERP balances with itselfThat each journal entry balances, that the trial balance matches the journal and that each customer’s and supplier’s open items match their account
C · Trial balanceThe balance, debit and credit of each account, and in which month they start to differ
D · JournalEach journal entry against its counterpart, by its number; the totals for each month
E · Open itemsFor each customer and supplier, what was invoiced, what was paid, what was settled with advance payments and what is still pending
F · Advance paymentsEach advance payment and each time it was applied to an invoice
G · FieldsThat each piece of data you had filled in in Powergest has a place in this programme, or a written reason for not bringing it
H · ValuesRecord by record, that each piece of data arrived the same: the name, Tax ID and address of each customer, the prices of each item, the date, customer and total of each document…
I · BatchesThat each Desktop ERP receipt or payment is here as a single operation, with the same money, the same advance payments, the same expenses and the same bills
J · VAT registerThe taxable base, the tax amount and the surcharge for each month, in sales and in purchases, with the invoices that differ
K · Money, day by dayEach bank, cash, expense, income and tax account, day by day. If something doesn’t match, it gives the day, the account and the journal entries on each side
R · Desktop ERP data worth correctingWhat is best fixed in the Desktop ERP before migrating (see ‘How do I review the Desktop ERP before migrating?’)

Each difference comes out in a colour:

Before migrating, regenerate the accounting balances in Powergest. That way check A comes out clean and whatever appears afterwards comes from the migration.

Each unexplained difference also says whose it is and what to do: above the detail, a table groups them by case (‘Journal entry dated in another year’, ‘Bill collected without a journal entry’…), with what has to be done in each one. Those that don’t fit any known case come out as New case.

How do I review the Desktop ERP before migrating?

In Verify the migration, with the ZIP chosen at the top, click Review the Desktop ERP. It doesn’t migrate anything or look at the company: it only reads the copy and says what is worth correcting in the Desktop ERP before migrating:

Correct what it says, take another copy and migrate with it.

Can I hand over the migration now?

The traffic light tells you, when the migration finishes and in ‘Verify the migration’:

What happens to the Desktop ERP customer ‘Type’?

It comes in exactly as it is as the record’s customer type. If in your Powergest the type was a code in which each digit means something —the product they have, their maintenance, whether they asked not to receive emails…—, the migration can’t read it: each different code becomes a customer type with the number itself as its name. To make it understandable, tell it what each digit means in Decode the customer type, on the same migration screen.

Each rule puts a tag on the record, which can be seen on the Details tab and is used to filter reports and choose who a newsletter goes to. If the rule says so, it also unsubscribes or marks Do not resend for that record’s emails in the mailing.

And the customer types named after their number get their tags as their name, joined by ‘·’ (for example, ‘Product: PowerGest · Maintenance: Normal’). That way the Customer types list makes sense. A type you have already named keeps its name.

How do I write the customer type rules?

One per line: the position of the digit (the first from the left is 1), a colon, the values separated by commas, ‘=’ and the tag. If it affects email, after ‘|’, baja (unsubscribe) or no reenviar (do not resend):

# Customer type
1:1,2 = Type: Wholesaler
1:3   = Type: Retailer
# Area
2:5   = Area: North
2:A   = Area: South
3:9   = Wrong email | no reenviar
3:0   = Doesn’t want advertising | baja

How do I apply it?

  1. Write the rules and click See what changes. It doesn’t change anything yet: it says how many records change, how many will get each tag, how many emails will be unsubscribed and how each code is read.
  2. If the rules have any error, each one appears with its line. Correct them and click again.
  3. If it is going to unsubscribe any email, tick Understood: an unsubscribe is permanent.
  4. Click Apply. The rules are saved for next time.

If you change a rule after seeing what changes, click See what changes again before applying.

You need full access to the migration from the Desktop ERP.

Can I repeat it?

Yes, and it is best to do it after each migration, because migrating again brings the type back exactly as it was. The tags the rules set are calculated again. The ones you set by hand on the record (‘VIP’, ‘Regular’…) aren’t touched. Whatever is already done isn’t repeated.

An unsubscribe can’t be undone. If you remove an unsubscribe rule, the tags change, but the emails that were already unsubscribed stay unsubscribed: only the person themselves can come back, by asking from an email. A Do not resend can be removed by hand, from the address in Mailing › Addresses.

Which of the record’s emails are unsubscribed?

All the ones it has: email 1, email 2 and those of its contact persons. A mistyped email isn’t touched, and the preview says how many there are. The unsubscribe is from commercial email: invoices and other documents still reach them. A Do not resend also leaves documents out.

If something goes wrong

What you seeWhat has happenedWhat to do
‘Could not read the ZIP’The file isn’t a valid ZIP or is larger than 200 MBCompress the folder again; split it if it is huge
The ZIP is read but To import comes out at 0The ZIP doesn’t bring any of the recognised tablesCheck that CLIEN.DBF, ALMA.DBF… are inside
A table comes out with Invalid templateThe Powergest file is missing an essential column, such as the code or the name. No row came in from that tableThe message says which column is missing. Import it with the wizard, adjusting the mapping by hand
A table brings rows ‘with errors’Each one has its reasonLook at it in the result details, which give the row, the code and the reason for each one
There are customer records without a Tax ID after migratingSeveral shops of the same company share the CIF, and the programme only accepts one record per documentIt appears in Incomplete, with the document and the record. Decide which one should carry it and set it by hand
There are customer records without a ledger account after migratingSeveral records brought the same Desktop ERP sub-accountIt isn’t a fault: the empty account is worked out by itself from the code. You only need to touch it if you want a specific number
The programme warns that it has changed a rule of my companyThe Powergest chart of accounts uses account codes with letters and they have had to be allowedIt is correct and necessary. It stays enabled; it is switched off in the Accounting settings if it is ever no longer needed
Almost all items are missing and there is no errorThe ZIP brought two sets of tables and the right data was in the one with a suffixGo back to the preview and read the warning about another set of tables
The records come in, but a field arrives empty in all of themThat version of the Desktop ERP doesn’t bring that column. The field is left out and the rest is imported the sameIt isn’t a fault. If the data exists under another column name, import it with the wizard adjusting the mapping
Many rows ‘with errors’ in the catalogue textsThey are texts of records already deleted in Powergest, or the ZIP didn’t bring the catalogue treeLook at it in the details. If you recognise categories that do exist, migrate everything again
Categories are named with a code instead of their nameThe ZIP didn’t bring the catalogue textsMigrate again with the texts file. It corrects the names, it doesn’t duplicate categories
Accents come out wrongThe .dbf isn’t from Powergest and has been read with another encodingImport it with the wizard choosing the standalone file
No photo came inYou didn’t provide the images, or you gave a folder the server can’t reachMigrate again uploading the Images ZIP. It doesn’t duplicate anything
Some photos came in and others didn’tThose photos are no longer in the BMP folderLook at it in the details: it says which ones. Upload them by hand on the item’s record
The images ZIP says it doesn’t bring anyYou have compressed a folder that isn’t the BMP one, or it only has files that aren’t imagesCompress the whole BMP folder and upload it again
The long texts of the records are missingThe Desktop ERP notes files aren’t readThey are moved by hand
The verification report says the ZIP isn’t the one that was importedYou have chosen another copy of the Powergest dataChoose the ZIP you migrated with. If you no longer have it, clear out the imported data, migrate with a new one and verify with that one
The report says the company has no record of which ZIP was importedThe company was migrated before that was recordedMake sure yourself that it is the same ZIP; the verification works the same
Check A comes out in amberPowergest already didn’t balance with itselfRegenerate the balances in Powergest, make a new ZIP and repeat the migration
The verification comes out full of reds after migrating a newer ZIPIt was migrated on top of an earlier migration: whatever was already there wasn’t redone and the company still has the data from the old ZIPClear out the imported data, migrate the new ZIP cleanly and verify with that same ZIP
I don’t know whether the migration got startedThe screen was closed or reloaded while it was migratingGo back in: the message at the top says whether it is still running, or when the company’s last migration was and how it ended
‘There is already a migration running in this company’Another person, or you from another tab, started one firstWait for it to finish: the message at the top says how far it has got
When setting up an item it says the code is longer than the maximumThe Desktop ERP didn’t pad item codes and had a maximum length; the migration has copied itUse a shorter code, just as in the Desktop ERP. The maximum is in Settings › Codes

See also: What can be imported · Import customers from an Excel file · Open a new financial year

More about Bring in your data