> ## Documentation Index
> Fetch the complete documentation index at: https://honeydew.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Import Tools

<Tip>
  Import Tools are a standalone product. Please contact [support@honeydew.ai](mailto:support@honeydew.ai) in order to use.
</Tip>

## Looker

Convert a LookML repository to Honeydew semantics.

<Note>
  This section is about converting LookML to Honeydew.

  See [Looker Integration](/integration/bi-tools/looker) on how to use Looker as a BI tool operating
  on a Honeydew schema (whether it was migrated from LookML or not).
</Note>

Automatic conversion steps:

1. Views are converted to [Entities](/modeling/entities)
2. Explores are converted to [Domains](/domains)
3. [Relations](/modeling/relations) are detected from explore join configurations
4. Measures are converted to [Metrics](/calculations/metrics)
5. Dimensions are converted to table attributes (as part of their entity) or to [Calculated Attributes](/calculations/attributes) -
   depending on their expression
6. Dimension Groups are converted to multiple attributes
7. Metadata (such as descriptions and display names) are imported as part of the conversion

<Tip>
  Measures and dimensions expressions that are using Snowflake SQL syntax are converted fully, including lineage and dependencies.
  Measure aggregation types are converted to SQL aggregation functions.
</Tip>

Limitations:

* Liquify templates are not converted
* Looker Parameters and User attributes conversion is not automatic.
  They can be manually converted to [Parameters](/parameters)
* Some Looker advanced functionality is not supported as-is (such as `sql_where` join filters) and
  requires manual conversion.

## Tableau

Convert a Tableau data source to Honeydew semantics.

<Note>
  This section is about converting Tableau Data Source to Honeydew.

  See [From Tableau to Honeydew](/migration/tableau-guide) for a conceptual guide
  on translating Tableau patterns (calculated fields, LOD expressions, table
  calculations) to Honeydew.

  See [Tableau Integration](/integration/bi-tools/tableau) on how to use Tableau
  as a BI tool operating on a Honeydew schema (whether it was migrated from
  Tableau or not).
</Note>

Automatic conversion steps:

1. Tables are converted to [Entities](/modeling/entities)
2. Joins are converted to [Relations](/modeling/relations)
3. Table fields are converted to table attributes (as part of the entity)
4. Calculated fields with aggregations are converted to [Metrics](/calculations/metrics)
5. Calculated dimensions are converted to [Calculated Attributes](/calculations/attributes)
6. Level of detail (LOD) expressions are converted to
   [Metrics with Level Of Details](/calculations/metrics#controlling-grouping)
7. Parameters are converted to [Parameters](/parameters)
8. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

<Tip>
  Measures and dimensions using Tableau VizQL language are translated to Snowflake SQL expressions,
  including lineage and dependencies.
</Tip>

Limitations:

* Most but not all Tableau functions are converted to Snowflake SQL; some require manual adjustment.
* Extracts with a relational schema can't be mapped to their Snowflake source and require manual
  adjustment of Entity Source Tables.
* Some advanced Tableau functionality requires manual conversion.

## Power BI

Convert a Power BI Semantic Model to Honeydew semantics.

<Note>
  This section is about converting a Power BI Semantic Model to Honeydew.

  See [Power BI Integration](/integration/bi-tools/powerbi) on how to use Power BI as a BI tool operating
  on a Honeydew schema (whether it was migrated from Power BI or not).
</Note>

Automatic conversion steps:

1. Tables are converted to [Entities](/modeling/entities)
2. Joins are converted to [Relations](/modeling/relations)
3. Table fields are converted to table attributes (as part of the entity)
4. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

Limitations:

* Calculated DAX columns and measures are copied without conversion to SQL, and require manual conversion.
* Data source that resides in Fabric or is loaded to a Data Import, can't be mapped
  to the Snowflake source automatically and requires manual adjustment of Entity Source Tables.

<Tip>
  Automatic conversion of DAX to calculated attributes and metrics is coming soon.
</Tip>

## SAP Business Objects

Convert an SAP Business Objects Universe to Honeydew semantics.

Automatic conversion steps:

1. Universe data foundation tables are converted to [Entities](/modeling/entities)
2. Joins defined in the data foundation are converted to [Relations](/modeling/relations)
3. Universe classes are converted to folders, preserving the organizational structure
4. Dimension objects are converted to table attributes (as part of their entity)
   or to [Calculated Attributes](/calculations/attributes) - depending on their expression
5. Measure objects are converted to [Metrics](/calculations/metrics)
6. Detail objects are converted to [Calculated Attributes](/calculations/attributes)
7. Metadata (such as descriptions and display names) is imported as part of the conversion

## MicroStrategy

Convert a MicroStrategy project to Honeydew
semantics, including tables, joins, metrics,
derived metrics and metadata.

## dbt

Map a dbt manifest to a Honeydew schema.

<Note>
  dbt can be both a source for Honeydew, and a target for Honeydew.

  To use Honeydew to generate dbt models,see [dbt integration](/integration/etl-tools/dbt) section.

  Also, see [overview of a data pipeline](/integration/etl-tools/pipeline-architecture) for Honeydew and dbt interoperability.
</Note>

Unlike conversion from BI (Tableau, Looker or Power BI), Honeydew does not replace dbt transformations,
but allows to add a semantic model on top of them.

Honeydew dbt import tool processes the compiled dbt manifest (`manifest.json`) to extract metadata.
[dbt tests](https://docs.getdbt.com/docs/build/data-tests) are used to detect relationships and keys.

1. Chosen dbt models are mapped to [Entities](/modeling/entities)
2. Entity keys are detected based on `unique` dbt tests, if these exist
3. [Relations](/modeling/relations) are detected based on `relationship` dbt tests, if these exist
4. Metadata (such as descriptions, folders and display names) is imported as part of the conversion

## Open Semantic Interchange (OSI)

Convert an [Open Semantic Interchange](/integration/osi#converting-to-and-from-osi)
semantic model to Honeydew semantics, including datasets, relationships,
fields, metrics, and AI context metadata.

## Snowflake Semantic Views

Convert
[Snowflake Semantic Views](https://docs.snowflake.com/en/user-guide/views-semantic/overview)
to Honeydew semantics, including tables, joins,
measures, dimensions and metadata.

## Snowflake Schema

When mapping Snowflake tables in Honeydew UI,
Honeydew automatically extracts relevant metadata
if defined, such as comments, primary keys
or foreign keys.