Field help (MIG2INTIT)

Payment terms

This phase is used for the creation of the payment terms and corresponding payment methods defined in the transcoding.

In Sage Intégrale, it is possible to choose other payment terms if the amount is larger or lesser. 
In Sage X3, the replacing is only possible if the amount is lesser.

Sage Intégrale, with due dates by ten-day or two-week periods, can translate the concept of 30 into end of months. This information is not recovered in Sage X3.

Sage Intégrale can define a limit day and a carry-forward day.
This information is not recovered in Sage X3.

Example: let us consider a limit day on the 25 and a carry-forward on the 10. An entry issued on the 25th of the current month and the 9th of the next month will therefore have the 10th of the next month as a calculation base for the due date.

Sage Intégrale can define a day of due date. This information is not recovered in Sage X3 (the option is systematically combined with "End of month" or "Ten-day period").

The items generated by this migration are visible in the menu:

• Common data / BP tables / Payment terms,
• Common data / BP tables / Payment terms.

Factors

This phase is used for the creation of the factors defined in the transcoding.
The factors whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / BPs / Factors.

The management of the factors differs between the two software products:

• in Sage Intégrale, the factor may be associated with a control account / miscellaneous auxiliary account, or a general account,
• in Sage X3, the factor is associated only to a general account.

However, the accounting entries of the factors are recovered and can be viewed in these accounts (control or general accounts).

For a correct usage of the data in Sage X3, the setup of the factors must be determined by associating a general account in the factor record. The factors that were associated to a control account must be associated with a general account, and their new entries are attached to these general accounts.

Sales reps

This phase is used for the creation of the sales representatives defined in the transcoding.

The items generated by this migration are visible in the menu Common data / BPs / Sales reps.

Customers

This phase is used for the creation of the customers defined in the transcoding.
The customers whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / BPs / Customers.

 

• In Sage Intégrale, customers may have a customer code that differs from their auxiliary code.
  For example: the customer code "Dupont" is posted in the auxiliary account "CDupont".
• In Sage X3, these two codes are the same.
  For example: the customer code "Dupont" can be posted only in the auxiliary account "Dupont".

The entries in Sage Intégrale customers follow the same pattern.

In the case where the customer code and the auxiliary account differed in Sage Intégrale, the former Sage Intégrale auxiliary account is mentioned in the Notes block of the Sage X3 customer record.

Suppliers

This phase is used for the creation of the suppliers defined in the transcoding.

The suppliers whose code starts with "$$" (typical record) are not recovered in Sage X3.
Only the suppliers specified as carriers in supplier records are recovered as carriers in Sage X3. The others must be created manually.

The items generated by this migration are visible in the menu Common data / BPs / Suppliers.

 

• In Sage Intégrale, a supplier and a customer may have the same code without being the same BP.
• In Sage X3, this is no longer possible. If this situation occurs, it is necessary to go back to the transcoding, modify the suggested supplier code to specify a new one, and then relaunch the migration of the suppliers.

If the two Sage Intégrale BPs (customer and supplier) have the same postal code and site tax ID number, only one BP is created in Sage X3 with the double role of customer and supplier.

• In Sage Intégrale, suppliers may have a supplier code that differs from their auxiliary code.
• In Sage X3, these two codes are the same.

The entries in Sage Intégrale suppliers follow the same pattern.

In the case where the supplier code and the auxiliary account differed in Sage Intégrale, the former Sage Intégrale auxiliary account is mentioned in the Notes block of the Sage X3 supplier record.

Products

This phase is used for the migration of the products defined in the transcoding.

The products recovered in Sage X3 are those whose nature is:

• "Normal",
• "Cost",
• "Port", 
• "Service".

For "Normal" products, the production nature must "Component", "Finished product", or "Routing".

For "Finished products", the migration program searches for their default production site in Sage Intégrale in order to identify it as production site in Sage X3.
The products not compatible with Sage X3 are created with the status "Not to be used".
The customers whose code starts with "$$" (typical record) are not recovered in Sage X3.

The items generated by this migration are visible in the menu Common data / Products / Products.

The corresponding customers, suppliers and sites are also created.

Work centers

This phase is used for the migration of the work centers defined in the transcoding. They correspond to the Sage Intégrale products of the "OP" (operation) and "MO" (labor) types.

The items generated by this migration are visible in the menu Manufacturing / Technical data / Work centers / Work centers.



• A product record is created in Sage X3 to enable the recovery of the documents containing the "OP" and "MO" Sage Intégrale product types.
• The products and work centers are independent from one another in Sage X3.
• A work center is created for each site identified as a "production site".

 See the migration of the products.

SO pricing

This phase is used for the migration of the sales prices defined in the transcoding.

Only the following prices are recovered:

• the basic prices -tax / +tax contained in the product record, excluding promotional prices,
• the product price lists in currency,
• the product quantity prices.

The items generated by this migration are visible in the menu Purchasing / Price lists / Price list entry.

 To recover the price lists, certain data elements are mandatory. 

 See the chapters "Setup" and "Sales" in the appendices.

PO pricing

This phase is used for the migration of the purchase prices defined in the transcoding.

The supplier price lists and the discounts (from the supplier records) are recovered. The following items are created:

• The "FOU" price list code, corresponding to the supplier discount percentage or increase percentage. This setup is generated only if the corresponding supplier discount (positive or negative percentage) contains a column number in the setup phase,
• the "ART" price list code, corresponding to the product price lists per supplier,
• the "FAM" price list code, corresponding to the product group price lists per supplier,
• the "SFAM" price list code, corresponding to the product sub-group price lists per supplier.

The validity start date of the price list is initialized on the date of the first day of the first fiscal year recovered by the migration. This date is indicated in the setup of the first "Financials" tab.
The validity end date is equal to the start date plus ten years.

The items generated by this migration are visible in the menu Purchasing / Price lists / Price list entry.

 To recover the price lists, certain data elements are mandatory. 

 See the chapters "Setup" and "Sales" in the appendices.

BOMs

This phase is used for the migration of the BOMs defined in the transcoding.

The BOMs generated by this migration are visible in the menu:

• Common data / BOMs / Production BOMs, for products managed in stock,
• Common data / BOMs / Commercial BOMs, for products not managed in stock (equivalent to the assembly in Sage Intégrale).

The routings generated by this migration are visible in the menu Manufacturing / Technical data / Routings / Routing management.

Products of the "OP" (operation) or "MO" (labor) types are recovered in the routings.



Since the routings may be used in multiple Sage Intégrale BOMs, which themselves may be associated with different production sites, they are systematically created for all the sites identified as "production sites" in Sage X3.

The site code is retained in the routing code. It is therefore important to check that the length of the product code and that of the site code do not exceed the product code max length set up in Sage X3. If they are too long, this must be taken into account in the transcoding of the products and sites; shorter codes must be assigned to them.

For example: if a Sage Intégrale company has 5 warehouses, 3 of which being identified as "production sites": TO, RO, and ZZ, 3 routings are created: GA1, GA2, and GA3. In Sage X3, the following 9 routings are recovered: GA1TO, GA1RO, GA1ZZ, GA2TO, GA2RO, GA2ZZ, GA3TO, GA3RO, and GA3ZZ.

The customer and document specific BOMs are not recovered in Sage X3.

Accounts (general and miscellaneous BP)

This phase is used for the migration of the general accounts (Common data / G/L accounting tables / General / Accounts - if necessary, choose the chart of accounts using the [Plan] button) and, simultaneously, that of the miscellaneous auxiliaries (Common data / BPs / BPs), as defined in the transcoding.

• The format of the accounts depends on the chart code.
• The default class is initialized with regards to the setup of the chart code (Setup / Organizational structure / Charts of accounts) delivered in standard.
• A null currency code indicates that all the accounts are multi-currency.
• If the Sage Intégrale account is managed in analytical accounting, the account of the chart of accounts can be set up with a specified "default account". The screen will be imposed; that is, if there are analytical movements, they are posted to the default account by default.

This phase automatically creates the analytical plan for all the accounts managed analytically.
The analytical accounts are created with the same coding as the general accounts (Common data / G/L accounting tables / General - choose the analytical chart of accounts) and are automatically assigned to them.

Analytical dimensions

This phase is used for the migration of the analytical centers and dimensions defined in the transcoding. The Sage Intégrale analytical centers become dimensions in Sage X3. The Sage Intégrale dimensions are reconstituted on the fly in Sage X3 by concatenating the different centers.

 

The dimension types are created upon the migration of the company. An additional type, "Others", is added for the analytical dimensions defined in Sage Intégrale which do not correspond to the concatenation of analytical centers.

The following items are migrated:

• the Sage Intégrale analytical dimensions which do not correspond to the concatenation of analytical centers. In that case, they are associated with the "Others" type.
• the Sage Intégrale analytical centers. They become analytical dimensions in Sage X3 and are associated with their corresponding type.

The items generated by this migration are visible in the menu Common data / G/L accounting tables / Analytical / Analytical dimensions.

Analytical distribution

Before migrating the analytical distributions, it is necessary to check that the ledger and the company record are set up with the correct dimension types, so that the distributions are assigned to the correct types and dimensions.

This phase is used for migrating the distributions of the analytical models present in Sage Intégrale.

The items generated by this migration are visible in the menu Common data / G/L accounting tables / Analytical / Analytical allocation.