Data migration from vtiger to dolibarr 8.0.4

hello every one please i need help for migrating my vtgier data to dolibarr , help for tools please
thanks waiting your respond

  1. Install Dolibarr 8.0.4 (Latest stable release)
  2. Enable all required modules and set them up correctly.
  3. Open Top Menu ‘Tools’ -> Import
  4. For each and every Third Party

download the sample CSV files which represent the Dolibarr expected input structure.

  1. Create a spreadsheet from the respective CSV
    6. Study the just added info patiently and decide what options to default too!
  2. Import your vtiger CSV (exported earlier) into a second spreadsheet
  3. Link the vtiger data from this spreadsheet to the respective columns of the Dolibarr input structure in the first spreadsheet
  4. Save the Dolibarr spreadsheet as a CSV again and start the Dolibar import process

thank you sir but it,s not working till now this is the screen shot of the error it show up

Pièces jointes :

New ImportStep 1 Step 2 Step 3 Step 4 Step 5
Module/Application Services
Import file into dataset Services

Information on source file
Source file format Csv
CSV format options Field Separator : , String Delimiter : "
Source file to import 20190220094958-20190219135514-Book3.csv
Number of lines in source file 34
Limit range (from - to) eg. to omit header line
1
-
34
Modify
Key (column) to use for updating existing data No update attempt was performed, only insert - Modify

Information on target fields
Targeted tables llx_product
Targeted fields Field 1->p.ref, Field 2->p.label, Field 3->p.description, Field 4->p.url, Field 5->p.accountancy_code_sell, Field 6->p.accountancy_code_buy, Field 7->p.note, Field 8->p.length, Field 9->p.surface, Field 10->p.volume, Field 11->p.weight, Field 12->p.duration, Field 13->p.customcode, Field 14->p.price, Field 15->p.price_ttc, Field 16->p.tva_tx, Field 17->p.tosell, Field 18->p.tobuy, Field 19->p.fk_product_type, Field 20->p.finished, Field 21->p.datec
Number of lines with no errors and no warnings: 0.

Errors on 34 source record(s)
* Line 1
> Wrong value for field number 17 (value ‘For sale* (p.tosell)’ does not match regex rule ^[0|1]$)
> Wrong value for field number 18 (value ‘For purchase* (p.tobuy)’ does not match regex rule ^[0|1]$)
> Wrong value for field number 19 (value ‘Type* (p.fk_product_type)’ does not match regex rule ^[0|1]$)
> Wrong value for field number 21 (value ‘Creation date (p.datec);;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;’ does not match regex rule ^[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]$)
* Line 2
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 3
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 4
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 5
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 6
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 7
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 8
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 9
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 10
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 11
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 12
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 13
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 14
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 15
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 16
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 17
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 18
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 19
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 20
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 21
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 22
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 23
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 24
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 25
> Mandatory data is empty in the source file for field 2.
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 26
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 27
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 28
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 29
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 30
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 31
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 32
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 33
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.
* Line 34
> Mandatory data is empty in the source file for field 17.
> Mandatory data is empty in the source file for field 18.
> Mandatory data is empty in the source file for field 19.

Check the results of the import simulation. Correct any errors and re-test.
When the simulation reports no errors you may proceed to import the data into the database.

IMPORT DATA

Correct the errors, then repeat.

Example: > Wrong value for field number 17 (value ‘For sale* (p.tosell)’ does not match regex rule ^[0|1]$)

Then the vtiger source field should contain either ‘0’ or ‘1’ to fit the requirements of the dolibarr target field.

I found the import process to be a world of pain, so I made many changes to the import code which are now in the development version 10.

I suggest you read this thread and get those changed files.
www.dolibarr.org/t/mass-import-export-8-0-3/17116/1

As far as I can tell: manso’s problem stems mostly from the mixed structure of his vtiger source data (see his earlier posts on vtiger export). THIS has to be solved first!

Then it becomes a multi-step import process - for vtiger organizations, vtiger vendors, vtiger contacts etc.

At all times he should supply the foreign keys in the respective CSV file which connect (say) contacts to organizations on a many to one way.

AFAIK no programming required. Only logically constant procedures.