org merge best practices

28
Org Merge Best Practices What you need to know before you merge Ryan Lambert Senior Technical Solution Architect Salesforce Julian Devassy Senior IT Manager, Customer Care Vantiv

Upload: salesforce-developers

Post on 16-Jan-2017

333 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Org Merge Best Practices

Org Merge Best Practices What you need to know before you merge

 Ryan Lambert  Senior Technical Solution Architect  Salesforce

 Julian Devassy  Senior IT Manager, Customer Care  Vantiv

Page 2: Org Merge Best Practices

 Safe harbor statement under the Private Securities Litigation Reform Act of 1995:

 This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.

 The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.

 Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

Safe Harbor

Page 3: Org Merge Best Practices

Ryan Lambert Senior Technical Solution Architect

Salesforce

Page 4: Org Merge Best Practices

Julian Devassy Senior IT Manager, Customer Care

Vantiv

Page 5: Org Merge Best Practices

 Org Merge Overview

 Project Setup

 Migration Tracks

•  Business

•  Metadata

•  Code

•  Data

 Project Management

 Guest Speaker

 Force.com Migration Tool

Agenda

Page 6: Org Merge Best Practices

Org Merge Overview Two is not always better than One!

Page 7: Org Merge Best Practices

 Why Merge? •  Organic Growth, Acquisitions, Doing it Differently

•  Global Reporting, Forecasting

 Lift & Shift vs Optimization

Org Merge Overview

Page 8: Org Merge Best Practices

Project Setup Building a Dream Team

Page 9: Org Merge Best Practices

 The Team

•  Executive Sponsorship, Customer Engagement, Execution Specialists

 Org Access & Users

 Sandboxes

 Tools & Skills

•  AppExchange (example: FieldTrip)

•  Force.com Migration Tool

•  ETL (example: Tableau)

 Deployment Plan

•  Example

Project Setup

Page 10: Org Merge Best Practices

Project Setup Deployment Plan – Example

Script each finite step

Determine dependencies

Dry Runs == Essential

Page 11: Org Merge Best Practices

Business The driver behind it all…

Page 12: Org Merge Best Practices

 Merge Architecture

•  Two Orgs become One

•  Merge Into (retiring org & surviving org)

 “As Is” vs “To Be”

•  Optimization

•  Common Elements

 New Features / Capabilities

 QAT / UAT : early and iterative

 Change Management

Business

Page 13: Org Merge Best Practices

Metadata The XML that you will learn to love…

Page 14: Org Merge Best Practices

 Tool Selection

 Salesforce Limits

•  Custom Fields, Spanning Relationships and Workarounds

 Profiles & Permission Sets

Metadata

Page 15: Org Merge Best Practices

 Destructive Changes

 Unsupported Metadata Types

 Out of Scope

•  Example: Knowledge, Reports and Dashboards

 Deployment Strategy

•  Single Deployment – Metadata + Unit Tests

•  ON/OFF Switch – Triggers, Workflows and Validation Rules

•  Proactive Validation w/ Quick Deploy (if possible)

Metadata

Page 16: Org Merge Best Practices

Code Handle with care

Page 17: Org Merge Best Practices

 Common vs Distinct

 New Code

 Templates

•  Triggers

 Limits

•  Relationships

 Unit Tests & Code Coverage

•  API Versions

Code

Page 18: Org Merge Best Practices

Data The biggest piece of cheese

Page 19: Org Merge Best Practices

 Data Cleansing

•  Prune the fat, make way for inbound data of higher value

 Selective Migration

•  All, Some, None

 Data Transformation

•  Business Optimization

Data

Page 20: Org Merge Best Practices

 Some Good Advice

•  Legacy ID’s

•  Sharing Records

•  The Grand Orchestration

 User Licenses

•  Enough seats for everyone

 Runtime & Delta

Data

Page 21: Org Merge Best Practices

Project Management The glue that holds it all together

Page 22: Org Merge Best Practices

Project Management

Possible Approach

•  Managed Packages

•  Independent Metadata

•  Users (Metadata & Data)

•  ALL METADATA

•  Data

•  Data Dependent / Manual Tasks

Dry Run

•  Practice until its Production-ready

Methodology

•  Agile Waterfall – single release – single goal

Page 23: Org Merge Best Practices

Julian Devassy Senior IT Manager, Customer Care

Vantiv

Page 24: Org Merge Best Practices

Force.com Migration Tool Platform support for your metadata migration

Page 25: Org Merge Best Practices

 What is it?

•  The Force.com Migration Tool is a Java/Ant-based command-line utility, based on the Force.com Metadata API, for moving metadata between a local system directory and a Force.com organization

 Uses

•  New Development projects – Populate a developer org with metadata from production

•  Iterative Deployment – Scripted interface supports an efficient retrieval and deployment process

•  Production Deployment – Code deployment to Production

 Skills Needed

•  Reading, Copy & Paste, a working knowledge of XML

 Getting Started

•  https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_deploying_ant.htm

•  https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/

Force.com Migration Tool

Page 26: Org Merge Best Practices

 Either of these placeholders can hold text, table, charts, smart art, or media.

Quick Tour  Running in Five Minutes

Assumptions: Java & Ant installed & configured

•  Login | Setup | Develop | Tools | Download

•  Unzip

•  Open command prompt terminal (sample)

•  Edit build.properties (user/pass)

•  ant describeMetadata

•  ant test

 Requirements: Java JDK 6.1+ and ANT 1.6+

•  Create Retrieve & Deploy templates

•  Copy & Paste, leverage ${variables}

•  Concept: Retrieve, Tweak, Validate, Deploy

•  checkonly & testlevel ( runalltests )

•  Deployment Status

Page 27: Org Merge Best Practices

Q & A

Page 28: Org Merge Best Practices

Thank you