---
title: "Practices: Anaplan, Databricks, Informatica, Reltio, Salesforce and Snowflake — Datagist"
description: "Datagist practice teams for Anaplan, Databricks, Informatica, Reltio, Salesforce and Snowflake. Each team works on one platform every day."
url: https://datagist.ai/practices
---

Practices 

# Our practices.

Specialist teams for the platforms you already run. Each team works on one platform every day, so they know where it tends to break.

How our practices work 

## Turning data, AI, and technology into business impact.

Our specialist practices help you get more value from the platforms you already use, from implementation and integration to modernization and optimization.

Anaplan practice 

## Anaplan models that load their own actuals.

We build and repair Anaplan models and wire them to your warehouse, so actuals arrive on a schedule and approved plans go back out for reporting.

[Explore the Anaplan practice ](https://datagist.ai/practices/anaplan)

- ### Model design and build  
Finance, sales, workforce, and supply chain models, built to Anaplan's published modeling practices so they calculate quickly and stay easy to change.
- ### Data integration  
Scheduled loads from Snowflake, Databricks, ERP, and CRM through CloudWorks, Anaplan Connect, and the APIs. Each load checks that its totals tie out.
- ### Hierarchies from master data  
Account, product, cost center, and territory lists taken from mastered data. A new cost center in the ERP appears in the plan on the next load.

### More from the team

- Plans back to the warehouse
- Forecasting
- Model review and optimization
- Governance and release management
- Anaplan operations

What changes

> Planners open the model to plan, and the numbers already tie to the books.

Databricks practice 

## A Databricks lakehouse your business can run on.

Our senior engineers set up and run Databricks lakehouses with Unity Catalog in place from the first table, and move your models and agents from notebooks into production.

[Explore the Databricks practice ](https://datagist.ai/practices/databricks)

- ### Lakehouse architecture and setup  
Workspace layout, Unity Catalog, networking and security, and environments defined as infrastructure as code.
- ### Migration to Databricks  
Moves off Hadoop, legacy warehouses, and ETL tools such as Informatica PowerCenter. Automated reconciliation shows the new numbers match the old ones before cutover.
- ### Data engineering with Lakeflow and Delta Lake  
Batch and streaming pipelines, change data capture, and data quality expectations, written as declarative pipelines.

### More from the team

- Unity Catalog governance
- Databricks SQL and BI
- Machine learning and GenAI with Mosaic AI
- Performance and reliability
- Platform operations

What changes

> One governed lakehouse your teams can build on, with every table traced to its source and its owner.

Informatica practice 

## Informatica data you can trace from source to report.

We build and run Informatica's Intelligent Data Management Cloud for integration, data quality, master data, and governance. If older Informatica tools still run on your own servers, we move them to the cloud as well.

[Explore the Informatica practice ](https://datagist.ai/practices/informatica)

- ### Cloud data integration and ingestion  
Batch, streaming, and change data capture pipelines with Cloud Data Integration and Mass Ingestion. Loads land in Snowflake, Databricks, and cloud storage, with pushdown so the work runs inside the platform.
- ### Application and API integration  
APIs, events, and process flows between ERP, CRM, trading partners, and data platforms, built with Cloud Application Integration and managed as APIs.
- ### MDM SaaS and the 360 apps  
Customer, product, supplier, and reference data on MDM SaaS, including Customer 360, Product 360, Supplier 360, and Reference 360\. Match rules are tuned on your own records, and each data owner signs off on survivorship.

### More from the team

- Data quality and observability
- Catalog, governance, and Data Marketplace
- CLAIRE, AI, and Salesforce
- Moves from on-premises Informatica
- Operations and IPU usage

What changes

> Every job has an owner, and you know what reads its output.

Reltio practice 

## Reltio match rules your stewards can read.

We design, tune, and run Reltio for customer, provider, product, and supplier data. Every match rule is tested on your own records before it is allowed to merge anything.

[Explore the Reltio practice ](https://datagist.ai/practices/reltio)

- ### Reltio data model design  
Entity, relationship, and interaction types, attributes, and reference data for customer, provider, product, supplier, and location domains.
- ### Match and merge tuning  
Match rules, comparators, cleansers, and match tokens tuned on a labeled sample. FERN goes live in stages, with false merges checked first.
- ### Survivorship and golden records  
Source ranking, survivorship strategies, and quality rules agreed with data owners, so every attribute has a clear winner.

### More from the team

- Source onboarding and integration
- Hierarchies and affiliations
- Data stewardship
- Reltio data in the warehouse
- Reltio operations

What changes

> One golden record per customer, product, or supplier, and a reason for every merge.

Salesforce practice 

## Salesforce that runs on one clean set of accounts.

We implement and support Salesforce clouds and connect them to your data platform. Data 360, Agentforce, and your reports then work from the same accounts and contacts.

[Explore the Salesforce practice ](https://datagist.ai/practices/salesforce)

- ### Implementation and rollout  
Sales Cloud, Service Cloud, Experience Cloud, and Marketing Cloud, from design through user adoption.
- ### Industry clouds  
Health Cloud, Life Sciences Cloud, Financial Services Cloud for insurance, and Energy & Utilities Cloud, configured for regulated work.
- ### Data 360 (formerly Data Cloud)  
Ingestion, identity resolution, unified profiles, segments, and zero-copy access to Snowflake and Databricks.

### More from the team

- Agentforce and AI
- Integration and MuleSoft
- Customer data quality and MDM
- Analytics with Tableau
- Org health and managed services

What changes

> One record per customer, in an org your teams open every day.

Snowflake practice 

## Snowflake that holds up as more teams join.

We migrate to Snowflake, build on it, and tune it. Roles, warehouses, and resource monitors go in before the data does, so each new team joins a platform that is already governed.

[Explore the Snowflake practice ](https://datagist.ai/practices/snowflake)

- ### Snowflake architecture and setup  
Account and database design, role-based access, network security, and environments managed as code.
- ### Migration to Snowflake  
Moves from Teradata, Netezza, Oracle, SQL Server, and Hadoop, with automated reconciliation of the results.
- ### Data engineering  
Ingestion with Snowpipe and Openflow, transformation with dbt, Dynamic Tables, and Snowpark, and Apache Iceberg tables.

### More from the team

- Master data on Snowflake
- Governance with Snowflake Horizon
- Data sharing and collaboration
- AI with Snowflake Cortex
- Performance and usage

What changes

> Access you can explain to an auditor, and one customer table every team uses.

Practices and services 

## The platform team and the data team work as one.

A practice team knows the platform. Our services teams handle the strategy, data, and AI work around it. Most projects need both, and you get one plan and one point of contact.

[See our services ](https://datagist.ai/services)

## Running a platform we don’t list?

Tell us what you use. The data problems around it are usually the same ones we fix every day.

[Start a conversation ](https://datagist.ai/contact)
