Migrating GL Segments and Sub-accounts (Optional)

This topic describes how to migrate General Ledger segments and sub-accounts in Sage Intacct. DataSync migrations do not map GL segments and sub-accounts out of the box. However, the fields are available and can be mapped as follows:

  1. Configure a custom dimension in Sage Intacct under Platform Services:

    1. Create Custom Fields or a Platform Application.

    2. Populate these objects with the appropriate values.

  2. Under Company, select Import Data.

  3. Scroll to the General Ledger Transactions section and click Template.

  4. Open the file and make sure your new custom dimensions are there. Take note of the Field names.

    Note:  Custom dimensions or fields should be in the rightmost columns.

  5. In DataSync, segments are already included in the extraction but they are not mapped to any fields.

    Note:  In Sage 200 UK these segments are the AccountCostCentre and Account Department fields. In all other ERPs, they are named Segment01, Segment02, etc.

    In order to map custom fields, you need to add the new dimensions to all related tables in table GLENTRY:

    1. In SEI, right-click Info Pages to Control Work Flow and select View Info Pages.

    2. Enter the parameters and click Add.

  6. (Optional) If you want these dimensions to be available for data entry in SEI, the field must be included in the GL Entries data model:

    1. Under General Ledger, right-click GL Entries and select Design Data Model.

    2. Select the field in the Fact Table.

    3. Extend Edit and change the Editable Level to 10.

    4. Click Save Data Model.

    5. Add the field in the GL Entries worksheet.

  7. In DataSync, open Extraction 1 (INTACCTMIGRA1) and navigate to STG GLENTRY > Fields. The new dimension is now available as a mapping source. Select the dimension from the list.

  8. Open Extraction 3 in DataSync. Select the Sync option to expose the field in the CSV export.

    Note:  For the final CSV, the column order can be re-organized and it does not have to match the template completely, as long as header fields are to the left of line fields.

What's Next

Proceed with the migration