Advanced migration scenarios for export and import features

You can export and import for these migration tasks:
  • Copy companies from Determination environments to ONESOURCE Determination
  • Copy companies from 1 ONESOURCE Determination environment to another
  • Copy tax configuration data types from Determination companies to ONESOURCE Determination companies
  • Copy tax configuration data types from ONESOURCE Determination company to another in the same or a different environment

General migration considerations

Consider these warnings and limitations before you begin:
  • The External ID's required for Indirect Tax cloud and must be unique in the system. 2 companies can't use the same External ID even if they're managed under different tenants.
  • You can only perform 1 import at a time.
  • The top-level company in your import's set as a parent company on the destination environment. You can change it to a child company and assign a parent after the import's complete.
  • You can't delete items with an import, only add new items or modify existing items.
  • If you import a company that inherits configuration groups from an ancestor, and that ancestor isn't included in the import, the configuration groups are set to NONE. You must set the configuration groups after the import.

Prepare your source system

You can use export and import to migrate to Indirect Tax from various Determination environment types, including on-premises, private cloud, and hosted cloud.
Configuration data exports must come from an environment with content version G.2 for compatibility with Indirect Tax. If your environment's on a different content version, you must upgrade your content, which may also require upgrading Determination.
Any company you plan to import into Indirect Tax must have a unique External Company ID. This maps to the field External ID in Indirect Tax and must be unique across the entire environment.

Export from your source system

Indirect Tax accepts single companies, companies with descendents, and individual configurations from Determination. You can export companies and configuration data from
Properties
for a particular configuration.

Avoid duplicate records

To create a unique record there's a combination of fields that together provide a unique ID. For example, in TB_FILTER_GROUPS the Start_Date, Merchant_ID, and Name get combined for a unique key. The record may have many other fields such as location, position, office number, etc. and some may be required fields, but these aren't required as part of the unique key in this example.
When importing records from 1 database to another (source to target), the system updates the existing record in the target when the unique key matches (present and identical). If there's any variation within the unique key, such as numbers or letters transposed, or for example, if name was a part of a unique key, the middle initial entered in one record and omitted in another, the system will not recognize these records as the same and will create another record in the target. This is normal and expected behavior.
If you determine that the 2 separate records should be one record, the solution is to delete one of the records. Verify within you company's process who has authority to perform this action. Be sure to check all the fields to make sure you are not losing data. For example, the first record may contain the employee phone number but not the address. The second record may contain the address but is missing other information. In this case you may want to combine the data of both records to retain a complete record before deleting the other.
This table gives you the combined fields used to create unique keys for each table.
Table / entity
Natural key columns
Authority - TB_AUTHORITIES
Primary - UUID, Secondary - MERCHANT_ID, NAME
Authority Logic Group - TB_AUTHORITY_LOGIC_GROUPS
Name, MerchantID
Authority Types - TB_AUTHORITY_TYPES
Name, MerchantID
Merchants - TB_MERCHANTS
Name
Product Category - TB_PRODUCT_CATEGORIES
PARENT_PRODUCT_CATEGORY_ID, PRODUCT_GROUP_ID, MERCHANT_ID, NAME
Product Groups - TB_PRODUCT_GROUPS
PRODUCT_GROUP_ID
Zones - TB_ZONES
ZONE_LEVEL_ID, NAME, MERCHANT_ID, PARENT_ZONE_ID
Allocation Groups - TB_ALLOC_GROUPS
MERCHANT_ID, NAME
Authority Logic Group Reference - TB_AUTHORITY_LOGIC_GROUP_XREF
START_DATE, AUTHORITY_ID, AUTHORITY_LOGIC_GROUP_ID, PROCESS_ORDER
Authority Requirements - TB_AUTHORITY_REQUIREMENTS
START_DATE, AUTHORITY_ID, MERCHANT_ID, NAME
Customers - TB_CUSTOMERS
CUSTOMER_GROUP_ID, CUST_NUMBER, CUST_NAME
Customer Groups - TB_CUSTOMER_GROUPS
MERCHANT_ID, NAME
Established Authorities - TB_ESTABLISHED_AUTHORITIES
START_DATE, ESTABLISHED_AUTHORITY_TYPE_ID, AUTHORITY_ID, MERCHANT_ID
Established Authority Types - TB_ESTABLISHED_AUTHORITY_TYPES
START_DATE, ESTABLISHED_ZONE_ID, AUTHORITY_TYPE_ID, MERCHANT_ID
Established Zones - TB_ESTABLISHED_ZONES
START_DATE, ZONE_ID, MERCHANT_ID
Exempt Reasons - TB_EXEMPT_REASONS
CUSTOMER_GROUP_ID, SHORT_CODE
Filter Groups - TB_FILTER_GROUPS
START_DATE, MERCHANT_ID, NAME
Locations - TB_LOCATIONS
MERCHANT_ID, NAME
Merchant Options - TB_MERCHANT_OPTIONS
OPTION_LOOKUP_ID, MERCHANT_ID
Merchant XML Elements - TB_MERCHANT_XML_ELEMENTS
XML_GROUP_ID, XML_ELEMENT_ID
Registrations - TB_MERCH_REGISTRATIONS
REGISTRATION_GROUP_ID, START_DATE, AUTHORITY_ID
Registration Groups - TB_MERCH_REG_GROUPS
MERCHANT_ID, NAME
Product Cross Reference - TB_PRODUCT_CROSS_REF
MERCHANT_ID, NAME
Product Cross Reference Groups - TB_PRODUCT_CROSS_REF_GROUPS
MERCHANT_ID, NAME
Product Qualifier Groups - TB_PRODUCT_QUALIFIER_GROUPS
MERCHANT_ID, NAME
Rates - TB_RATES
RATE_CODE, START_DATE, IS_LOCAL, AUTHORITY_ID, MERCHANT_ID
Rate Tiers - TB_RATE_TIERS
RATE_ID, AMOUNT_LOW
Rules - TB_RULES
RULE_ORDER, START_DATE, IS_LOCAL, AUTHORITY_ID, MERCHANT_ID
Tax Code Qualifier Groups - TB_TAX_CODE_QUALIFIER_GROUPS
MERCHANT_ID, NAME
Vendor Groups - TB_VENDOR_GROUPS
MERCHANT_ID, NAME
XML Groups - TB_XML_GROUPS
XML_GROUP_NAME, MERCHANT_ID
Exempt Certificates - TB_EXEMPT_CERTS
CUSTOMER_ID, EXEMPT_REASON_ID, FROM_DATE, CERTIFICATE_NUMBER

Related Content